After some time, TV appears to be on even if it's in standby #702
Comments
|
@tavicu where should we capture context around this issue? I'm finding the plugin becoming more unstable with latest node (22.12.0) version. Hosting HB on 15.2 MacOS
What context would be helpful to share? Here are recent debug logs from my end. As this user notices, the TV falls out of sync frequently resulting in the TV turning on/off inadvertently. I'm noticing a high volume of errors in my debug log data: |
|
Wanted to pass along some log data and screenshots to record these events in hope we can resolve this glitch. Right now I have the Samsung TV off. The Home App shows it as on. Controller for Home shows it as off: 
But it does show it's "Sleep Discovery Mode" is "On" This is what my debugging log shows during this time: I'm enabling NodeJS:DataStream*,HAP-NodeJS:* to grab more detail over the next few days. LMK if I can provide any additional context. Currently on Node 22.12.0 |
|
@lordgiotto Yeah, if it comes empty then the current version will treat it like it's ON. However, it is strange that the answer is empty. The new version will not look at the PowerState at all :). It should be much more reliable than the current "hacks". @JasonGoldenDDT You said there is a high volume of errors but I don't see any, only debugs that don't help with this problem. Right now the plugin checks the state by pinging the TV and if it responds, then it sends a http request to check the power state. In case the request fails, then the plugin will mark the TV as OFF. There were some reports previously from people that had problems on their network and the request timed out, resulting in a fail response. The timeout is set to 500ms. If your TV takes longer to respond, then there's the problem. But it's strange than in Home app appears ON while Controller appears OFF. Again, something is telling me there is a problem on your network somewhere because in Homebridge the status of tv is OFF but it's not updating in the home app. Try to restart your devices, your apple tv (that is set as home hub) if you have one, hard restart your TV (keep the power button pressed on your remote until you see the Samsung logo). Other than that ... don't know how to help you right now. As I mentioned to @lordgiotto, the newer version of the plugin will have a new method that checks the state of TV, A more reliable method and without hacks trying to determine the correct state. You can check how fast your TV responds with a curl command, more here: #535 |
|
@tavicu Thank you for taking a moment to respond. I'm trying to collect as much data round the experience as I can, given I don't have background creating Homebridge Plugins. I'm not sure, but at suspect there is an interaction with Node.js and this plugin that affects it's reliability. I noticed after changing my node install form 18 to 22 the plugin became less reliable. After enabling HAP Node debugging messages, it looks like on refresh the device's status is getting updated erroneously. Telling Home the TV is "active" when it's off. IDK of this got cross wired with "Auto Discovery Enabled" or something else entirely. These log files are difficult to mask for sharing purposes. Let me know what context I can provide to be helpful here. What would be helpful from the log? I have adjusted my debugging to include HAP messages now, and the log can collect multiple days of activity. From ControllerForHomeKit Log Homebridge Debug w/-NodeJS:DataStream,HAP-NodeJS:** I can provide more log data, just time consuming to mask to share here. From "ControllerforHomeKit" Device Log - can export to JSON file
|
|
Continuing to investigate the cause of this issue with my Samsung NQ90C TV falling out of sync with the Home App. As mentioned I've enabled debugging with HAP-Node and I'm seeing a pattern emerge since going from Node 18 to Node 22 and this plugin. A very high sampling rate of the device's data. I continue to see the TV appear as ON in the Home App hours after turning it off. It seems like there is a queue of outdated messages getting picked up by the Home App. I see this with an LG TV as well. Let know what additional context I can provide, or messages I should look out for. |
|
Same here, From what I read in other threads developers use Smart Things API to determine channels and TV status (On Off) If I can help with any other information let me know, I would like to add tv to routines and automation, running away from home assistant and migrating everything to apple Home |
Why would you want to do that? :) Home Assistant is miles ahead Homebridge Also, using Smart Things API it's not the scope of the project, which is keeping basic functionality locally without requiring internet access. Regarding the node version and everything you are reporting, there is not much I can do even if you find something (and until now I see no error in your logs or something, just basic things which reports changes or state). This is just a plugin that mostly uses Homebridge and HAP-NodeJS APK. So everything is provided by them, like setting the state, input, and so on. The plugin logic is to determine the state of TV for example, and then report it to Homebridge. What homebridge is doing with this information ... it's their kitchen and nothing I can do. |
|
I just dropped a spreadsheet (numbers) on this thread about a similar issue I'm having with LG TV and AC. nVuln/homebridge-lg-thinq#325 (comment) The file includes all devices and their HAP-Node Activities and Values. Gives some insight as to the volume of messages over a span of the last few days. @tavicu the logs are massive, I'm working on capturing and masking data around my use case with these devices. But I am seeking some odd behavior with HAP, take a look at the messages that are getting sent, Firmware is repeated significantly more than any other message. I'll keep working on example debug data, but if you see a message you'd like me to drill down on I can. I have automation that fires daily at specific times related to these devices, so it just takes time to capture and filter through the data. I suspect it's an interaction between Node and the plugin as I did notice changes in performance between 18 and 22 in my recent changes to troubleshoot version error messages in the log. |
Having Home assistant for 3 years time now, need to re do the entire thing, maintaining it is killing a lot of time, doing so with 2 homes, (my parents and mine) I am at the point of completely rebuilding HA server, but for my parents at least I am considering migrating them to Apple home, Just trying. It all started becase I wanted to have the garage door remote on apple car play... But I am already starting to find limitations on it. Anyway, I totally get the purpose of the project and staying away from cloud, makes sense! |
Home App is not reliable in my experience. I have migrated to Home Assistant 4 years ago and never looked back. In 4 years I didn't had to fix anything. From Home Assistant you can expose your entities to Home app and have the garage door on car play. That's what I did, especially that my wife still prefers Home App (in her defence, even after 4 years I didn't had time to clean up the Home Assistant main dashboard :P). @JasonGoldenDDT I understand and I appreciate it. But as I said in the previous message, you should probably post in Homebridge repo, not much we can do from the plugin. |
|
@tavicu I'm sharing my experience in the HAP-Node GitHub, as with these types of things no one really has the bandwidth to unpack what is actually happening for the user. Im just taking shots in the dark here hoping something draws attention to the technical issue causing this to happen. I'll come back around to this after the holidays. |
Hi, first of all, thanks for this plugin: I tried many both in HB and in HA, and yours is the most reliable :)
I'm opening this issue because, within a few hours after I turn off my Samsung S90CA OLED TV, the accessory appears to be on in Homebridge, while the TV is still off. And it stays that way until I turn it on and off again.
Not sure if it's related, but by checking the
/api/v2/GET endpoint when that happens, I noticed that thePowerStatevalue is set to an empty string (see attachment below).Have you ever experienced this kind of bug? Do you know if there is a solution to this, or if maybe the upcoming version you're working on will handle this edge case?
Thanks :)
The text was updated successfully, but these errors were encountered: