(0x1) .MEDIA_SHOW_EPISODE - int : The episode number of the media if present.
(0x1) .MEDIA_ARTIST - string : The artist name of the media if present.(0x1) .MEDIA_ALBUM - string : The album name of the media if present.
(0x1) .MEDIA_FILENAME - string : The full filename of the media.(0x2) .MEDIA_ISSEEKING - boolean : True if the media is currently seeking or fast forwarding(rewinding).(0x2) .MEDIA_ISPLAYING - boolean : True if the media is currently playing (not paused).(0x2) .MEDIA_ISACTIVE - boolean : True if a player is currently active.(0x8) .HOST_NAME - string : Contain the name of current Media Center (Yatse 4.3.0+).(0x8) .HOST_ID - long : Contain the id of current Media Center (Yatse 4.3.0+).(0x8) .HOST_STATUS - boolean : Contain the connection status to current Media Center.0x8 : Connection changed : This flag is set when the connection status to Media Center changeĭepending on the flags a number of extra fields will be filled with more details (The corresponding needed flag is show between () as the type).0x2 : Status changed : This flag is set when the status of Media Center change (Play / Pause / Stop / Seeking).0x1 : Media changed : This flag is set when the currently playing media change.This int is a bit flag that can have one or more of the following bits set : You must then check the int extra : .STATUS_FLAG to know the type of event. The Broadcast Intent will have it's action set to : .INFO_STATUS_CHANGED With the unlocker you can activate the option Send Broadcasts that allow Yatse to send public broadcast to inform other application on the phone on events. To search a media of type mediatype with the name value (Sample : yatse://command/search/Movie/alien) yatse://command/search/mediatype/value (Unlocker only).To start playing a media of type mediatype with the name value (Sample : yatse/command/play/Movie/avatar) yatse://command/play/mediatype/value (Unlocker only).To change the current Media Center (where xx is the ID of the media center, visible in all media center list bottom right) yatse://command/select/media_center?ID=xx.On Beta 4.10445 although this isn't new just looking to fix it now.Yatse register some specific URI when installed: 16:22:45.996 Kodi: Restarting I/O service thread. 16:20:43.972 Kodi: Restarting I/O service thread. This still works fine! (based on this 'idle switch' I turn off my receiver)Ĭode: Select all 16:20:33.248 Kodi: (Kodi) Missed 1 pings, assumed off. This one sends it's preset (by me) virtual switch command to Domoticz 5 minutes after Kodi is idle. I have a Kodi plugin that can do actions, based on Kodi status. This screensaver status behaviour didn't happen with previous Kodi versions. When somewhere during play of the album, the pause button is used, and 'play' button afterwards, the 5:00 minutes thing with the screensaver starts over, repeating the list as described above. But will not turn to 'screensaver', even after > 30 minutes. When the album is finished, Kodi status will be displayed as 'On' (normal behaviour). All remaining tracks will be played afterwards without 'screensaver' status update, no matter how long the tracks are Kodi status 'Screensaver' stays active until the next audio track starts, than the status is updated to Audio again
After 5:00 minutes, Kodi (shown in Domoticz log) gives a status update "GUI.OnScreensaverActivated received" However, I came across one issue so far (and I wonder whether it should be looked at from the plugin side or Kodi side): Except for having to reset the screen resolution back from 640x480 to my 1920x1200 everything ran as before. Kodi 18 is recently released for stable in Xbian for RPI, I therefore accidentically updated to it. I assume that disable /enable a device on the hardware page is not sufficient, since I reviewed the python code, seeing that it indeed was 2.6.5 is mentioned there. Is it correct that you didn't update the version number? I saw 2.6.4 in the log after update of the plugin and switching it off/on again in Domoticz For the quick modification of the plugin to support the latest change in Kodi18.