Closed gscott16 closed 10 months ago
Please share the logs from the addon
Here is the Log segment
[2024-01-07T16:59:12 INFO govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted. [2024-01-07T17:05:56 INFO govee::service::hass] powerSwitch for E33E9C04A094C4CD: OFF [2024-01-07T17:07:32 INFO govee::service::hass] powerSwitch for E33E9C04A094C4CD: ON [2024-01-07T17:23:48 INFO govee::commands::serve] requesting update via IoT MQTT Office Christmas House (E3:3E:9C:04:A0:94:C4:CD) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "AWS IoT API", updated: 2024-01-07T23:07:50.552622088Z })
The plug is current on… If I slide the switch to the off position in the HA UI, the following message gets posted to the Log. [2024-01-07T17:34:53 INFO govee::service::hass] powerSwitch for E33E9C04A094C4CD: OFF
Nothing happens on the device and a few seconds later the UI moves the switch back to ON.
Those messages are not posted to the LOG at the current logging level
Please set the debug level to govee::commands::serve=trace,info
and restart the addon, then share the logs from when it first starts up
Thanks Wez. Here is the log but I don’t think it’s complete. I noticed that if I refresh the log some of the log data disappears and I am not handy enough with home assistant to know exactly how to change the log size…
One of the 5080 plugs is in the log - Garage Meross Plug.
I can send you some more details if you can share some hints on how to expand the size of the log…
And here is one error sitting in home assistant core that may be of use:
Logger: homeassistant.components.hassio Source: components/hassio/websocket_api.py:138 Integration: Home Assistant Supervisor (documentation, issues) First occurred: 7:36:52 PM (2 occurrences) Last logged: 8:14:15 PM
Failed to to call /addons/b9845f46_govee2mqtt/stats - 404 Client Error for http+docker://localhost/v1.43/containers/addon_b9845f46_govee2mqtt/json: Not Found ("No such container: addon_b9845f46_govee2mqtt")
Wez, here are a couple of additional log messages…
[2024-01-08T19:40:54 INFO govee::commands::serve] requesting update via IoT MQTT Garage Meross Plug (30:33:9C:04:A0:94:CD:91) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "AWS IoT API", updated: 2024-01-09T01:24:54.873469421Z })
[2024-01-08T19:41:54 INFO govee::commands::serve] requesting update via IoT MQTT Glance LED (B1:25:9C:04:A0:A6:36:BB) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "AWS IoT API", updated: 2024-01-09T01:25:54.839044568Z })
[2024-01-08T19:41:54 INFO govee::service::hass] powerSwitch for 30339C04A094CD91: OFF
[2024-01-08T19:43:03 INFO govee::service::hass] powerSwitch for B1259C04A0A636BB: OFF
Failed to to call /addons/b9845f46_govee2mqtt/stats - 404 Client Error for http+docker://localhost/v1.43/containers/addon_b9845f46_govee2mqtt/json: Not Found ("No such container: addon_b9845f46_govee2mqtt")
FWIW, that's not directly something that govee2mqtt can control; that looks like something internal to HASS
Thanks for sharing the logs. Unfortunately the most useful information was truncated away. I've updated the addon to include improved information at the regular logging level, which may help to understand what is going on. Please update the addon, and clear out the debug level. Please share the logs that summarize your device information on startup, and then logs from around where you are trying to control the device.
Wez, thanks for the update and feedback. I have 20+ GOVEE devices so the logs are full of lots of stuff. I have edited this down to one of the 5080 plugs for testing purposes. Incidentally, all of the other GOVEE devices are working as expected.
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started GOVEE_API_KEY=REDACTED GOVEE_MQTT_HOST=core-mosquitto GOVEE_EMAIL=REDACTED GOVEE_PASSWORD=REDACTED GOVEE_MQTT_PASSWORD=REDACTED GOVEE_MQTT_USER=addons GOVEE_MQTT_PORT=1883 ++ cd /app ++ exec /app/govee serve [2024-01-09T10:21:13 INFO govee::commands::serve] Starting service. version 2024.01.09-c452466f [2024-01-09T10:21:13 INFO govee::commands::serve] Querying platform API for device list [2024-01-09T10:21:13 INFO govee::commands::serve] Querying undocumented API for device + room list [2024-01-09T10:21:13 INFO govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted. [2024-01-09T10:21:13 INFO govee::commands::serve] Starting LAN discovery [2024-01-09T10:21:13 INFO govee::commands::serve] Waiting 10 seconds for LAN API discovery [2024-01-09T10:21:13 INFO govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-09T10:21:23 INFO govee::commands::serve] [2024-01-09T10:21:23 INFO govee::commands::serve] Garage Meross Plug (30:33:9C:04:A0:94:CD:91) sku=H5080 [2024-01-09T10:21:23 INFO govee::commands::serve] Platform API: devices.types.socket. supports_rgb=false supports_brightness=false [2024-01-09T10:21:23 INFO govee::commands::serve] color_temp=None segment_rgb=None [2024-01-09T10:21:23 INFO govee::commands::serve] Undoc: room=None supports_iot=true ble_only=false [2024-01-09T10:21:23 INFO govee::commands::serve]
[2024-01-09T10:21:24 INFO govee::service::http] http server addr is 0.0.0.0:8056
[2024-01-09T10:21:43 INFO govee::commands::serve] requesting update via IoT MQTT Garage Meross Plug (30:33:9C:04:A0:94:CD:91) None
[2024-01-09T10:21:54 INFO govee::service::hass] Wait 13.1s for hass to settle on entity configs [2024-01-09T10:22:07 INFO govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-09T10:31:19 INFO govee::service::hass] powerSwitch for 30339C04A094CD91: OFF [2024-01-09T10:31:19 INFO govee::service::state] Using IoT API to set Garage Meross Plug (30:33:9C:04:A0:94:CD:91) power state
Adding an additional log entry…. This looks like a standard polling message which is reporting the correct state.
[2024-01-09T10:46:43 INFO govee::commands::serve] requesting update via IoT MQTT Garage Meross Plug (30:33:9C:04:A0:94:CD:91) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "AWS IoT API", updated: 2024-01-09T16:31:20.894959473Z })
From looking at homebridge-govee, it looks like a different value is needed to control the power state on this device. I've pushed a speculative fix in ab0af6b75892443133f2d704aeb35804da4e8149; please update the addon and let me know if that works!
Thanks Wez. THAT'S IT :) It's working perfectly!!!!
Great!
Wez, great work on this new integration and thank you. I migrated today from your old integration to this new one. I really like what I see. The one question I have is the behavior of the Govee H5080 smart plugs. They show up in the Intergration but they are not controllable through the UI. The PowerSwitch doesn’t seem to change the state (aka sliding it on does not turn it on, sliding it off does not turn it off). This behavior is consistent across the three plugs I tested. Interestingly, the UI does report the correct current state of the device. I can control them through the GOVEE app directly.