Is it possible to post those entries as text rather than an image and I’ll paste them in here and try it on my system.
It’s 6am here I won’t get to try it for about 8 hours.
I call it tetchy rather than buggy - but yes I know and you have to double check it’s updated the right data. There are 2 annoying bugs in beta 3d - the editor as you found and the child device install bug. I haven’t fixed the editor one - it’s a convoluted bit of code.
Ok Good I thought it was just messing with me... Enter a value and go back it's in the wrong attribute!
Is there an easy way to export out of mqtt explorer or another tool?
Sorry not at computer - on iPad but you can get it in history on the RHS I think.
Just to check this is created from HA and the device works correctly in HA. No virtual device is ever created automatically in HE from discovery ?
That is correct the couch_micro is created in HA and working correctly. I tried including my living_fan from HA just as a test and it also did not create the device. I have not been able to get any devices to be created from HE discovery.
Strange.. OK I’ll check tomorrow with your data.. any log message at all ?
PM me with anything else useful
Does the devices created from the hass statestream only go one way? ex i have a switch the states are reported in hubitat correctly i can turn it on and off in hass but not in hubitat
HA statestream as a protocol does not support control however I have included (in GitHub repository) some automations for HA that do provide such control... did you install those ? They cover the base devices but are very simple so you can add more unusual devices very easily. Then you’ll have 2 way control.
Awesome, so i added those three automations to my automations.yaml and read through your readme on github (Sorry i should have read that before asking) it appears that should be all i need to do correct?
discover the HA device into HE via the MQTT app in HE?
Yes .. let me know how you get on. Use a simple switch or light device first to become familiar. If you are using more complex devices eg a climate device PM me as next beta includes more devices.
A user posted above he was having an issue with discovery not creating devices but I know many users it’s working well for, including myself. Maybe it’s just his unusual esp devices.... looking into that.
Do i need to customize the automation?
It created the device correctly and the device in HE reflects the state correctly
MQTT Explorer
HE
I will PM you
I could get some stuff running on a Zigbee2mqtt instance. I have some buttons, which I understand are hard to support through MQTT, and some lights. The primary reason was that I'm beginning to replace my Netatmo TRV's with some Zigbee. And they are best supported by zigbee2mqtt.
If you need a tester, I'm ready.
I am not yet supporting discovery of climate devices into HE via HA MQTT Discovery yet but.....
Assuming they are appearing in HA I will likely discover them via statestream and I have a new remote thermostat device driver included in beta 3e which will hopefully just work. Good candidate to test with,
I’ll have now sent you a PM re beta3e. Can you let me know the brand/model of the TRV by PM
Buttons are a no no - mainly a HA issue.
Has anyone had issues getting a standard zigbee button to show up in Home Assistant via MQTT?
I have MQTT beta 3d set up in Hubitat with a variety of sensors and lights which all are working fine in HA. But when I try to add my Samsung zigbee button to the MQTT app in hubitat (published devices) it breaks everything in HA (all the MQTT devices get a red exclaimation mark). If I remove the button everything comes back again.
When the button is published, I can see the button in the /home/hubitat path fine using MQTT explorer.
Also, if I only publish the battery feature of the button it does work fine so it appears to be something with the actual button press feature.
Oh I just found the discussion further up in the thread that said buttons don't work, is that still accurate?
Or is it only the auto-discovery that doesn't work? (and if so, how would I manually add the button?).
What are others doing to workaround this and allow buttons in HE to be used in HA?
I think I have MQTT app installed correctly and I see it's connecting to the broker successfully. I only have one device selected, a dimmer in my bedrooom. It looks like everything goes ok and then hits the nullpointerexception.
app:502021-06-28 09:42:43.145 pm errorjava.lang.NullPointerException: Cannot get property 'displayName' on null object on line 2210 (updated)
app:502021-06-28 09:42:43.037 pm infoMQTT: Resynch MQTT device states and HA discovery topics
app:502021-06-28 09:42:42.968 pm debugMQTT: Events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.965 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.962 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from Switch switch using auto
app:502021-06-28 09:42:42.948 pm debugMQTT: Events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.945 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.942 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from Light switch using auto
app:502021-06-28 09:42:42.931 pm debugMQTT: Events subscribe to Bedroom Overhead Light level dimmed
app:502021-06-28 09:42:42.928 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light level dimmed
app:502021-06-28 09:42:42.925 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from SwitchLevel level using auto
app:502021-06-28 09:42:42.912 pm debugMQTT: Events subscribe to Bedroom Overhead Light power sensorDevices
app:502021-06-28 09:42:42.908 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light power sensorDevices
app:502021-06-28 09:42:42.905 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from PowerMeter power using auto
app:502021-06-28 09:42:42.891 pm infoMQTT: Starting HE device publishing to MQTT for 1 HE devices with 0 attributes
app:502021-06-28 09:42:42.857 pm debugMQTT: Events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.854 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.851 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from Switch switch using auto
app:502021-06-28 09:42:42.832 pm debugMQTT: Events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.829 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light switch switched
app:502021-06-28 09:42:42.826 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from Light switch using auto
app:502021-06-28 09:42:42.783 pm debugMQTT: Events subscribe to Bedroom Overhead Light level dimmed
app:502021-06-28 09:42:42.780 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light level dimmed
app:502021-06-28 09:42:42.777 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from SwitchLevel level using auto
app:502021-06-28 09:42:42.726 pm debugMQTT: Events subscribe to Bedroom Overhead Light power sensorDevices
app:502021-06-28 09:42:42.720 pm debugMQTT: Everything events subscribe to Bedroom Overhead Light power sensorDevices
app:502021-06-28 09:42:42.715 pm debugMQTT: Bedroom Overhead Light: Need to subscribe to events from PowerMeter power using auto
app:502021-06-28 09:42:42.672 pm debugMQTT: deviceSubscribesRather than use the ‘Everything’ drop down, disable the device there and use the ‘Dimmers’ and/or ‘Switches’ drop down to select your bedroom light.
What driver is your light using ?
I'm sorry if I missed that in 455 messages. Lol. I did that and it works now. The dimmer in question is using the GE Zigbee Dimmer driver.
Trying to figure out if I am in the right place. Looking for an option where I can send messages to MQTT Broker FROM HE. I have HA running but hopefully only for the MQTT Broker. I'd like to send message from HE to MQTT Broker for devices subscribing to take action on. Everytime I think I am in the right place I end up on another topic/post.
sorry
If you are wanting to send arbitrary messages to MQTT then this isn't the ideal integration but it can be done. Instead you can just the API built into HE and send them that way including (I believe) from Rule Machine.
If the message instead originates from an HE device but is destined to HA you can do that from this app.
Download the Hubitat app
