[RELEASE] MQTT UA Client driver(switch, ir blaster) | tasmota

rdstov · July 27, 2019, 5:06pm

Ryan,
So The code above for the driver allows for a Tasmota device to work with HE with no Broker? (I presume the custom Tasmota FW referred to is also needed). I’m not a code guy and just barely managed to flash my Tuya Smartlife device.

podarok · July 27, 2019, 9:26pm

If device toggled outside of HE - dashboard won't know. In my case - all works

Ryan780 · July 27, 2019, 9:38pm

Yes it will. It is broadcast to HE with Eric's custom firmware. I am on my phone so I can't link to it at the moment.

podarok · July 28, 2019, 5:29am

I'm not a big fan of relying on custom firmware of Tasmota. Usually forks are not good in providing support. Community consolidated around main repo. I guess it's a slippery slope.
Also - there is no support for retaining messages, like mqtt has. I added this in my driver.
When client disconnected - broker will retain the message while reconnected client. Very helpful in crowded wifi networks

Ryan780 · July 28, 2019, 5:30am

Okay. But you have to have a broker. Which is another thing to fail. I've never not had the other work.

podarok · July 28, 2019, 5:31am

That's why I'm looking for [API] Listen a TCP/UDP port from Driver?
For getting ability to build mqtt broker within hubitat

podarok · July 28, 2019, 5:32am

Mqtt broker can be installed as a cluster to multiple devices in the network for not fail

Ryan780 · July 28, 2019, 5:37am

Then I have to have multiple devices to install it on.

And as far as firmware updates, as long as the device works, I'm not updating to the latest firmware for Tasmota. Why would i if the device works anyway?

podarok · July 28, 2019, 5:42am

Sure
It's easy to use all family mobile phones to do that, all android devices around(even TV boxes). (Just termux + termux api + termux boot + nodejs +...)
Or 2 HE hubs which makes sense anyway for not fighting with struggle of building mesh networks and supporting big number of ZigBee/zWave devices

Ryan780 · July 28, 2019, 5:46am

Nope, nope and more nope. LOL. Sorry, but you're not selling me on MQTT for Tasmota. Not when there's a direct integration. Now, there are other reasons why i'd like MQTT support. But i don't see how you get a broker working natively on the hub without access to the OS. You can program one in Groovy?

podarok · July 28, 2019, 5:50am

Yes, there is a way to program one in groovy

Ryan780 · July 28, 2019, 5:51am

Okay. I can't wait to see what you come up with.

podarok · July 28, 2019, 5:52am

Without API for building TCP services in HE I can come up with nothing

Ryan780 · July 28, 2019, 5:55am

So, like i said, without access to the OS, you can't build a broker in the hub.

podarok · July 28, 2019, 5:56am

Sure

podarok · July 28, 2019, 6:02am

I would pay for the developer access for the Built-in APP building opportunity

Ryan780 · July 28, 2019, 6:03am

And they have said many times they will not ever do that. From a support perspective that would be a nightmare.

podarok · July 28, 2019, 6:06am

If keeping those drivers opensource - not necessarily

Ryan780 · July 28, 2019, 6:09am

Native Hubitat drivers are not open source. You don't have access to the drivers released by Hubitat.

podarok · July 30, 2019, 2:43pm

Added support for IR Blaster

github.com

podarok/mqtt-ua-client/blob/master/MQTT_UA_IR_Blaster/MQTT_UA_IR_Blaster_Client.groovy

metadata {
 definition(name: "MQTT UA IR blaster Client", namespace: "mqtt_ua_ir", author: "Andrii Podanenko") {
  capability "Initialize"
  capability "Switch"
 }
 preferences {
  input name: "MQTTBroker", type: "text", title: "MQTT Broker Address", description: "Enter address of the broker, for example, tcp://192.168.1.71:1883", required: true, displayDuringSetup: true
  input name: "username", type: "text", title: "MQTT Username", description: "Keep blank if none", required: false, displayDuringSetup: true
  input name: "password", type: "password", title: "MQTT Password", description: "Keep blank if none", required: false, displayDuringSetup: true
  input name: "publishto", type: "text", title: "Channel to Publish", description: "MQTT Channel used for publishing a message to", required: true, displayDuringSetup: false
  input name: "publishon", type: "text", title: "Text to Publish for switch ON", description: "Text used for publishing a message to a channel", required: true, displayDuringSetup: false
  input name: "publishoff", type: "text", title: "Text to Publish for switch OFF", description: "Text used for publishing a message to a channel", required: true, displayDuringSetup: false
 }

}


def installed() {
 log.info "installed..."
}

This file has been truncated. show original

Tested and working on Tuya IR Bridge