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
During 8 days the plugin worked flawlessly with my EPSON LS12000B.
Now, every two times when I turn the projector OFF using a send command, the projector goes OFF but the HA state goes to ON instead of OFF (1s after the actual "turn off" message, see log). Then HA stays ON until I restart and stop the projector.
Debug log
8:15:17 PM - changed to cooldown triggered by service epson_projector_link.send_command
8:15:18 PM - turned on triggered by service epson_projector_link.send_command
Command sent using the send_command :
"PWR OFF"
I looked at the code, there seems to be some code to manage "future state" and status updates, so things don't seem to be simple IRL.
The text was updated successfully, but these errors were encountered:
I spent hours trying to get logs of the problem but the problem only occurred when I wasn't recording the logs.
I finally understood yesterday that the problem occurs when the projector is seeking signal.
So to reproduce the problem one need to turn the source AND the projector off at the same time. Same time means "less that 4s delay between the two events".
I will try to get logs now I can reproduce.
Version of the custom_component
Current version, installed 15 days ago.
Describe the bug
During 8 days the plugin worked flawlessly with my EPSON LS12000B.
Now, every two times when I turn the projector OFF using a send command, the projector goes OFF but the HA state goes to ON instead of OFF (1s after the actual "turn off" message, see log). Then HA stays ON until I restart and stop the projector.
Debug log
8:15:17 PM - changed to cooldown triggered by service epson_projector_link.send_command
8:15:18 PM - turned on triggered by service epson_projector_link.send_command
Command sent using the send_command :
"PWR OFF"
I looked at the code, there seems to be some code to manage "future state" and status updates, so things don't seem to be simple IRL.
The text was updated successfully, but these errors were encountered: