MQTT import works really well for zigbee2mqtt devices. I have tested it with binary sensors for now (contact, motion). But I'll try additional devices later o.
Thanks for sticking with me!
Going to test a few z-wave devices I'm bringing in by MQTT also.
I presume you are bringing those other (non-zigbee2mqtt) devices via Home Asst?
If so, is there a "how to" resource you can point to for sharing those such HA devices via MQTT?
MQTT StateStream is pretty easy and seems to work well, but it only shares states to HE. I'm hoping for more 2-way capability with some of those devices (ala HADB). I'm guessing I need to dive deeper into HA's "MQTT Discovery" feature, but I haven't gotten very far with it yet.
I'm just wondering if that's the right road to be going down, or if I'm missing some other solution to try... Many thanks for any thoughts!
No, I'm not. I use Node-RED to bring in zigbee2mqtt devices into Hubitat. Now I can eliminate Node-RED for this use.
Two-way control works well with the MQTT Import integration.
OK, cool, thanks - I'll keep playing around with it then!
It kinda works with bringing in devices using ZwaveJS. I can see status changes, but am unable to control devices. This is what one of my ZWaveJS devices looks like:
Any chance of getting a ZWaveJS importer like the zigbee2mqtt importer?
Many thanks either way!
For zigbee2mqtt, some devices work perfectly. Binary switches and dimmers work great. All sensors I've tested work great (contact, motion, leak, occupancy, temperature).
Here's what doesn't work well currently:
Let me know what I can provide to help!
Can you send me the screenshots of what it looks like in your setup? Relevant MQTTExplorer topic names and full text of the retained messages would be perfect.
Yup. Starting with this message.
Multi-endpoint switch with four endpoints and temperature sensor:
{"countdown_l1":0,"countdown_l2":0,"countdown_l3":0,"countdown_l4":0,"linkquality":53,"power_on_behavior_l1":"off","power_on_behavior_l2":"off","power_on_behavior_l3":"off","power_on_behavior_l4":"off","state_l1":"ON","state_l2":"OFF","state_l3":"OFF","state_l4":"OFF","temperature":25.8}
Multi-endpoint switch with three endpoints:
{"linkquality":191,"state_center":"ON","state_left":"ON","state_right":"ON"}
Multi-endpoint switch with two endpoints
{"linkquality":76,"state_l1":"ON","state_l2":"ON"}
Zigbee Fan Module (Hampton Bay):
{"brightness":254,"fan_mode":"low","fan_state":"ON","linkquality":108,"state":"OFF"}
Supported fan modes are:
Tuya RGB/CT light
{"brightness":254,"color":{"hue":349,"saturation":31,"x":0.3627,"y":0.3175},"color_mode":"hs","color_temp":244,"color_temp_startup":25,"linkquality":0,"power_on_behavior":"previous","state":"OFF"}
Color temp goes from 25-1000, withj 25 being coolest and 1000 being warmest.
CT issue should be fixed in 2.5.0.123, which was released to the public ~ an hour ago.
I did the "best effort" fix on the fan, but I don't have a real device to test it on. So, maybe fixed.
I can send you an unused controller (that you can keep). PM me. Thanks!
Just FYI @gopher.ny that any time I try to import multiple zigbee2mqtt devices it gives an error, and only imports one of them.
Importing the same devices one at a time works fine.
EDIT: I have found if I just keep the same selection list and do the Import Selected over and over they eventually all add. Sometimes one device each round, sometimes more.
Checking that.
I have 2 instances of Z2M. Only one show up in the devices list.
@gopher.ny Also, you may need to think through what should be a state change and what shouldn't.
For instance, zigbee2mqtt that integrates with home assistant has this option enabled in zigbee2mqtt:
MQTT message payload will contain all attributes, not only changed ones. Has to be true when integrating via Home Assistant (Default: true)
Because of that, on every update all attributes are included. Which is generating a â– â– â– â– ton of extra events on the hubitat side for attributes that did not change.
For example on this Inovelli Blue dimmer connected to zigbee2mqtt I get 5 events every update, even though only 1 attribute changed:
P.S. - And nice work. The MQTT import seems to be working pretty well and is a VERY nice new feature. Congrats!!!
One more just for giggles @gopher.ny ...
It would also be nice if temperature attributes were converted to preferred units. Most devices I have report in DegC, but being an old fashioned American I want DegF.
It would be spiffy if specifically for the temperature attribute it would auto-convert it like Home Assistant does... Not the end of the world or anything though.
Here's a Third Reality ZigBee Temp + Humidity sensor - note temp is in DegC:
Also seeing an error in the logs if I update the default current state on a zigbee2mqtt mqtt device:
When trying to import some Tasmota devices, I get this error:
But Tasmota's MQTT structure separate command topics from states ones:
Yes on node-red I have to filter to only show new values. The way my alarm works is probably an edge case:
Without a means to 'filter if unchanged' that may play havoc with re-triggering rules I'd guess.
Download the Hubitat app
