You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually when the remote wakes up, it restarts all the services :
Wifi driver (wether the driver is in standby mode or completely off)
Bluetooth driver
Internal integrations
External & custom integrations
Meanwhile, if the user tries to process a command : entity command, activity start..., an error is raised as soon as the related integrations are unavailable.
From the logs we can see this kind of messages : [uc_denon_driver] Error connecting to driver ws://127.0.0.1:8092: ServiceUnavailable("Failed to connect to host: Connection refused (os error 111)")
And especially when a command on a given integration occurs : [Salon TV Orange] error executing activity command sonyavr_driver.main.media_player.5501824:media_player.on (ignore error: false): sonyavr_driver session not available
A red error message appears on the screen then.
A proposed solution :
Add a new option on the remote "Bufferize commands and process them during startup or wakeup"
Eventually add another option to skip errors in startup/stop sequences of activities (at activity level) : this option could helpful when an entity is failing but it is not a big deal for later usage
When processing commands (start activity sequence, execute a standalone command for a given entity) : if the entity is exposed by an integration which is not started yet and not connected (the core should be able to know which integrations are starting, started or not started yet) => wait for the integration to be loaded and running the commands when available
Add a "X" cross icon on the screen to abort the command / or sequence if it takes too much time
This new behaviour is close to the harmony's behaviour : startup/stop sequences wait for devices to be available (bluetooth connections in that case) and after a while, a cross is displayed to abort if it takes a too long time
How to Reproduce
Start an activity after lifting the remote which is asleep
The start sequence will fail eventually if it concerns an integration which is not loaded yet
Expected behavior
Start an activity
For each commands in the start sequence, wait for the integration to be fully loaded if the command is related to this integration not started yet
Display a cross to abort sequence in case the user finds it too long
System version
No response
What part of the system affected by the problem?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
albaintor
changed the title
[bug] Bufferize commands (activity start for ex) while the remote is waking up
[Feature] Bufferize commands (activity start for ex) while the remote is waking up
Nov 28, 2024
albaintor
changed the title
[Feature] Bufferize commands (activity start for ex) while the remote is waking up
[feature request] Bufferize commands (activity start for ex) while the remote is waking up
Nov 28, 2024
Is there an existing issue for this?
Description
Actually when the remote wakes up, it restarts all the services :
Meanwhile, if the user tries to process a command : entity command, activity start..., an error is raised as soon as the related integrations are unavailable.
From the logs we can see this kind of messages :
[uc_denon_driver] Error connecting to driver ws://127.0.0.1:8092: ServiceUnavailable("Failed to connect to host: Connection refused (os error 111)")
And especially when a command on a given integration occurs :
[Salon TV Orange] error executing activity command sonyavr_driver.main.media_player.5501824:media_player.on (ignore error: false): sonyavr_driver session not available
A red error message appears on the screen then.
A proposed solution :
This new behaviour is close to the harmony's behaviour : startup/stop sequences wait for devices to be available (bluetooth connections in that case) and after a while, a cross is displayed to abort if it takes a too long time
How to Reproduce
Expected behavior
System version
No response
What part of the system affected by the problem?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: