Thanks Dave, sorry to hear you're still in the hotel. I tried the new driver but I'm still seeing the active player being set to -1. I even recreated the device and it still tried to use the -1 playerid. It's not a huge deal if you can't get to it right now, I can work around it by using the shutdown command directly or by using the GUI to play/pause/stop until you get back.
20/06/2024 15:05:45.05 · DEBUG · Server.doCommand - AV|64~Power~Off from dashboard-fx-l367
20/06/2024 15:05:45.05 · DEBUG · Kodi.doCommand - Cmd=[64~Power~Off] Client=[dashboard-fx-l367]
20/06/2024 15:05:45.05 · DEBUG · Kodi.TX:CoreELEC - {"jsonrpc":"2.0","method":"Player.Stop","params":{"playerid":-1},"id":"Player.Stop"}
20/06/2024 15:05:45.05 · DEBUG · Kodi.RX:CoreELEC - {"error":{"code":-32602,"data":{"method":"Player.Stop","stack":{"message":"Value between 0 (inclusive) and 2 (inclusive) expected but -1 received","name":"playerid","type":"integer"}},"message":"Invalid params."},"id":"Player.Stop","jsonrpc":"2.0"}
20/06/2024 15:05:45.05 · DEBUG · Kodi.TX:CoreELEC - {"jsonrpc":"2.0","id":"Application.GetProperties","method":"Application.GetProperties","params":{"properties":["volume","muted"]} ,"id":"Application.GetProperties"}
20/06/2024 15:05:45.05 · DEBUG · Kodi.TX:CoreELEC - {"jsonrpc":"2.0","id":"Player.GetActivePlayers","method":"Player.GetActivePlayers","id":"Player.GetActivePlayers"}
20/06/2024 15:05:45.05 · DEBUG · Kodi.RX:CoreELEC - {"id":"Application.GetProperties","jsonrpc":"2.0","result":{"muted":false,"volume":100}}
20/06/2024 15:05:45.05 · DEBUG · Kodi.RX:CoreELEC - {"id":"Player.GetActivePlayers","jsonrpc":"2.0","result":[]}
Please Log in or Create an account to join the conversation.