H6199 Not responding to on/off requests

[JohnnyCarcinogen]

I've got a TV backlight strip that was working, but has now stopped responding. I just installed this add-on a couple days ago and it was working, but now it's stopped. There's no error in the logs, and it's getting the information about the device from the API call. There is a long warning in the log which I'm including. H6199troubleshooting.txt

[wez]

Thanks for reporting this! The issue from the troubleshooting text file should be resolved in the latest version of the addon.

Other changes include some more diagnostics about the devices and what was tried; if you're still unable to control your devices, please restart the addon so that those diagnostics show up in the logs section and share them here.

[JohnnyCarcinogen]

Thank you for the quick response and all the work on this. I updated the add-on to 2024.01.09-509d1790 and restarted everything, but no luck. I also completely uninstalled, removed the devices, and then installed again. I still have the same bizarre behavior. I'm including the logs during the initial start up of the add-on. There are some warnings about a device not communicating, but it's possible that's referencing a Bluetooth BBQ temperature sensor which is indeed not turned on. I'm also including some error logs. When I turn the device on/off using he Govee app, these errors start popping up. InitialGoveeStartupLogs.txt ErrorH6199.txt

[wez]

Those particular error messages are harmless, but I'll make them go away in the next update.

There's not really any information about the devices that aren't being controlled/working. The startup logs were truncated; the information about the device with the warning was missing from the top.

Are there messages that result from you trying to control the device through home assistant?

[calvinbui]

I'm on 2024.01.09-d3d97110 and my H6199 (DreamView T1) is working.

[JohnnyCarcinogen]

Thanks all. At this point, I'm starting to think the issue lies either with the device or my network configuration. I do have it set to only use 2.4Ghz as that can be an issue with these devices. I also have a static reserved for it. Here's the complete startup log, but if it's working for others, I suspect I've got another issue. h6199latest.txt

[wez]

@calvinbui do you see your H6199 as having LAN API support in your startup diagnostics? I'm not sure if it should show up there.

@JohnnyCarcinogen I don't see the log lines that I would expect to see from you attempting to control the device in what you shared most recently. Can you share those?

[JohnnyCarcinogen]

Those errors aren't showing any longer when I control the device from the Govee application. I do have these messages in the Logbook of the actual device: TV Backlight became unavailable 10:16:52 AM - 18 minutes ago TV Backlight Power Switch became unavailable 10:16:52 AM - 18 minutes ago

[wez]

I'd still like to see what does get logged when you try to control the device, as I don't have enough context to understand what is happening on your system.

[calvinbui]

@calvinbui do you see your H6199 as having LAN API support in your startup diagnostics? I'm not sure if it should show up there.

No, it doesn't have LAN support. It uses the IoT API.

[2024-01-11T00:54:26 INFO  govee::commands::serve] Starting service. version 2024.01.09-d3d97110
[2024-01-11T00:54:26 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-11T00:54:26 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-11T00:54:29 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-11T00:54:29 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-11T00:54:29 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-11T00:54:29 INFO  govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-01-11T00:54:39 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-11T00:54:39 INFO  govee::commands::serve] DreamView T1 () sku=H6199
[2024-01-11T00:54:39 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-11T00:54:39 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..15)
[2024-01-11T00:54:39 INFO  govee::commands::serve]   Undoc: room=Some("Living Room") supports_iot=true ble_only=false
[2024-01-11T00:54:39 INFO  govee::commands::serve] 
[2024-01-11T00:54:39 INFO  govee::service::http] http server addr is 0.0.0.0:8056
[2024-01-11T00:54:54 INFO  govee::service::hass] Wait 1.05s for hass to settle on entity configs
[2024-01-11T00:54:55 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-11T00:54:59 INFO  govee::service::state] requesting update via IoT MQTT DreamView T1 () None
[2024-01-11T00:55:27 INFO  govee::service::hass] Command for DreamView T1 (): {"state":"ON"}
[2024-01-11T00:55:27 INFO  govee::service::state] Using IoT API to set DreamView T1 () power state
[2024-01-11T00:55:32 INFO  govee::service::hass] Command for DreamView T1 (): {"state":"OFF"}

[JohnnyCarcinogen]

Yes, mine shows the supports_iot=true during startup. FWIW, my device is the Envisual version as opposed to the Dreamview if that makes any difference. (https://www.amazon.com/gp/product/B08LVPWQQP/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1) h6199latest.txt

[wez]

@JohnnyCarcinogen what I'm asking for is the logs from you controlling the device. For example, @calvinbui's logs show:

[2024-01-11T00:55:27 INFO  govee::service::state] Using IoT API to set DreamView T1 () power state
[2024-01-11T00:55:32 INFO  govee::service::hass] Command for DreamView T1 (): {"state":"OFF"}

I'd like to see the equivalent lines from your logs.

[JohnnyCarcinogen]

Sure thing. Here you go. Looks the same, but nothing happens, and the button just switches back to the "on" state.

[2024-01-10T13:28:21 INFO govee::service::hass] Command for TV Backlight (redacted): {"state":"OFF"} [2024-01-10T13:28:21 INFO govee::service::state] Using IoT API to set TV Backlight (redacted) power state [2024-01-10T13:28:25 INFO govee::service::hass] Command for TV Backlight (redacted): {"state":"OFF"} [2024-01-10T13:28:25 INFO govee::service::state] Using IoT API to set TV Backlight (redacted) power state

[wez]

Thanks; so yeah, I think there is a networking issue with that device. Is it on a different vlan or something? It seems like your other LAN API capable device doesn't show up on the LAN and since this device doesn't seem to respond, it makes me suspect that the devices are on an isolated part of the network where they neither have LAN nor public internet access.

[JohnnyCarcinogen]

Same VLAN. but I agree at this point, I think it's local network for some reason. Oddly, I reinstalled the old Govee integration yesterday while it was still working and it restored functionality. I'm going to try unplugging it for a bit. I appreciate all your assistance, and apologize for the waste of time. Thanks for all the work on this project. It is much nicer to be able to control effects.

[JohnnyCarcinogen]

Ok, this is bizarre. This was added to my scenes, and it actually works. Maybe some weird automation it picked up from the Govee app? Who knows. At least I have a work around.

[JohnnyCarcinogen]

FWIW, I believe I see the issue now. On my other set of lights, I have a toggle for enabling LAN control. On the H6199 that's not present, and I'm unable to update the FW from 1.00.01 even though it shows there's an update available. I've emailed Govee support, but I'm not holding my breath. If anything actually comes from it, I'll drop it here. Thanks.

[JohnnyCarcinogen]

Response from Govee: Thanks for contacting Govee here. Sorry to share that devices with cameras do not support Lan Control.

[wez]

I don't think there's anything here for me to address, so let's close this!

[JohnnyCarcinogen]

I know this is closed, but this is working now. haha. I don't know if it was the Home Assistant Core update or one of your updates, but it's responding now. Go figure.