-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AndroidTV] PhilipsTV power channel change values after thing thing got offline #18159
Comments
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/androidtv-binding-3-2-0-4-2-0/142203/562 |
EDIT: I found the offending code. Line 537 in 4dfaef9
When the thing state is set to online (and not in standby) it auto sets the power to ON. We probably should be calling for it to refresh instead. |
Hi @morph166955 it looks so. If you can create a fix and publish a bundle, I can test it. |
Working on that right now. Just moved to a new dev box and I'm having issues with Maven. Once I get that resolved I should be able to build a test jar. Might be a few days, not sure why it's breaking currently. |
Hi @morph166955 could you please update me about the fix? |
Expected Behavior
Keep value as OFF, instead setting it ON and immediately set it to OFF after thing got online
Current Behavior
Item value is OFF
Thing got OFFINE
Thing get ONLINE
Item value set to ON
Almost the same time it gets OFF.
PSA screenshot
Possible Solution
keep OFF value instead of ON
Steps to Reproduce (for Bugs)
Item value is OFF
Thing got OFFINE
Thing get ONLINE
Item value set to ON
Almost the same time it gets OFF.
Context
I have a PhilipsTV and use this configuration
As I persist state of TV there are lots of ON OFF entries generated during a day while TV was off full day.
Could it be related to this logic?
openhab-addons/bundles/org.openhab.binding.androidtv/src/main/java/org/openhab/binding/androidtv/internal/protocol/philipstv/service/PowerService.java
Line 69 in 4dfaef9
Debug log around the issue:
Your Environment
The text was updated successfully, but these errors were encountered: