homeassistant

12072 readers

19 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

GreatAlbatross@feddit.uk

Problems with Zigbee2mqtt (lemmy.world)

submitted 10 months ago by nogooduser@lemmy.world to c/homeassistant@lemmy.world

10 comments fedilink hide all child comments

I run HA in Docker and I have set up Mosquito MQTT and Zigbee2mqtt in other containers.

I can add Zigbee devices into Zigbee2mqtt and they automatically turn up in the MQTT integration. The problem is that they usually don’t have the control entities in HA. This means that I can’t activate switches by clicking on them in HA.

Everything else seems to work. I can turn the devices on and off in Zigbee2mqtt and I can do the same from Node Red (running in another container) with the Zigbee2mqtt plugin.

Has anyone else seen this problem?

I found something in GitHub about it but the comments said that it was fixed in the next version but I have a later version than that but it’s still not working.

top 10 comments

sorted by: hot top controversial new old

[–] AlternateRoute@lemmy.ca 4 points 10 months ago (1 children)

https://www.zigbee2mqtt.io/guide/configuration/homeassistant.html

Did you enable home assistant discovery since you were doing a manual installation?

# Optional: Home Assistant integration (MQTT discovery) (default: false)
homeassistant: true

[–] nogooduser@lemmy.world 1 points 10 months ago (1 children)

I have thanks. I have tried just doing the basic setting of ‘true’ and the more advanced options with no joy.

[–] AlternateRoute@lemmy.ca 2 points 10 months ago

Odd I have done the full setup several times As I run pure dockers / separate HA, Mosquito MQTT and Zigbee2mqtt and the devices all just auto discover and appear in HA has devices with entities with full control.

[–] lossanarch@lemmy.world 3 points 10 months ago (2 children)

Fairly sure this is a regression in the current release, i just ran into the same thing after upgrading to 1.34 and went back to 1.31.1

[–] nogooduser@lemmy.world 2 points 10 months ago

Downgrading to 1.31.1 fixed it. Thanks a lot.

[–] nogooduser@lemmy.world 1 points 10 months ago

Ok, thanks. I’ll have a look at switching to an older version.

[–] sabreW4K3@lemmy.tf 3 points 10 months ago

I haven't had the problem and am really new to HA, but it sounds like the switches weren't added properly. Perhaps try a reset?

[–] beeng@discuss.tchncs.de 2 points 10 months ago

How is your zigbee2mqtt running? Via HA or standalone?

You can click elements from NodeRed, so it means the HA connection to node-red is broken it sounds.

Try updating HA nodes inside nodeRed.
Make sure that your mqtt server has no errors

[–] gazoinksboe@lemmy.world 2 points 10 months ago (1 children)

I haven’t had this issue specifically but I’ve noticed when adding color changing bulbs, the color changing ability doesn’t show up in Home Assistant until I change the color in the dashboard of zigbee2mqtt. After that, home assistant recognizes the bulb’s capabilities. What hub do you have?

[–] nogooduser@lemmy.world 2 points 10 months ago

I have the older SONOFF stick.

I’m pretty sure that I have tried that. The kind of sure that means I’m going to have to try it again. 😀