App broken with Mosquitto broker 7.0.0
### Govee Device SKU All ### Govee2MQTT Version 2026.03.25-ab9deb66 ### Describe the issue The latest version of Mosquitto broker for Home Assistant does not allow client ids containing the "/" character. The Mosquitto log fills up with lines stating: 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" While govee2mqtt believe it's working, nothing can be controlled, and nothing updates. Reverting to the Mosquitto broker 6.5.2 restores service. ### Startup Diagnostics [2026-04-14T16:58:55 INFO govee::service::hass] Attempting connection to mqtt broker 192.168.1.220:1883... [2026-04-14T16:58:55 INFO govee::service::hass] Connected to mqtt broker 192.168.1.220:1883, status=CONNACK code 0: Connection Accepted. ### Additional Logs 2026-04-14 16:58:55: New connection from 192.168.1.220:36122 on port 1883. 2026-04-14 16:58:55: New client connected from 192.168.1.220:36122 as govee2mqtt/ae210f7bf2664b21a870812623d133a8 (p4, c1, k120, u'addons'). 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b2
Posted by markjhealey on Apr 14, 2026, 4:18 PM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
App broken with Mosquitto broker 7.0.0
### Govee Device SKU All ### Govee2MQTT Version 2026.03.25-ab9deb66 ### Describe the issue The latest version of Mosquitto broker for Home Assistant does not allow client ids containing the "/" character. The Mosquitto log fills up with lines stating: 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" While govee2mqtt believe it's working, nothing can be controlled, and nothing updates. Reverting to the Mosquitto broker 6.5.2 restores service. ### Startup Diagnostics [2026-04-14T16:58:55 INFO govee::service::hass] Attempting connection to mqtt broker 192.168.1.220:1883... [2026-04-14T16:58:55 INFO govee::service::hass] Connected to mqtt broker 192.168.1.220:1883, status=CONNACK code 0: Connection Accepted. ### Additional Logs 2026-04-14 16:58:55: New connection from 192.168.1.220:36122 on port 1883. 2026-04-14 16:58:55: New client connected from 192.168.1.220:36122 as govee2mqtt/ae210f7bf2664b21a870812623d133a8 (p4, c1, k120, u'addons'). 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b21a870812623d133a8" 2026-04-14 16:58:59: ACL denying access to client with dangerous client id "govee2mqtt/ae210f7bf2664b2
Comments (0)
No comments yet. Start the discussion.