Daniel Lashua

@robertsLando This is fantastic. I'd always wondered why something like this (mqtt AND web interface) didn't already exist for ZWave and have taken a stab at it myself a couple...

looking forward to this enhancement. It'll make using these entities in Home Assistant much easier.

When you register a "device_automation" via MQTT, the end result is that Home Assistant will fire an event when that trigger occurs. Because you are using AppDaemon, you don't have...

When Zigbee2MQTT uses the "device_automation" in Home Assistant, doesn't that trigger an event in Home Assistant? If so, you can listen_event() for that in AppDaemon.

My cursory examination of this shows that "device automations" are part of the new "device triggers" that Home Assistant has implemented, presumably to make creating Automations from the UI easier....

As a workaround, you could use the Home Assistant UI to create an automation with a device trigger that simply fires an event, and then listen for this event in...

If you are able to do so, would you submit a PR with this improvement?

Chiming in to say this happens to me quite often as well. I have two instances of wyze2mqtt running, both with different client_ids, both running in docker. The next time...

As far as best practices for Paho MQTT goes, there are a few things to be aware of. 1) Using LWT will allow an external observer to at least know...

> I have a suspicion that it is Paho not respecting the client ID specified when it tries to reconnect. Haven't had the chance to troubleshoot this issue though as...