atombaf / homebridge-mqtt-tasmota Goto Github PK

Hi there,

I'm just wondering if this plugin will help me setup some RF Smoke alarms using my Tasmota flashed Sonoff RF Bridge.

If so is there anything special in the config that I will need to do as each smoke alarm will have it's own RF code.

Thanks for your time.

I am using a different prefix (because i dislike the default topic setup from tasmota)

This does not seem to work with this plugin.
I enabled the "debug" option, where am I supposed to the see the output ? In the default homebridge log ? Don't see anything there.

Log. Error
7.2.2024, 11:05:04Mqtt Tasmota BridgeFEHLER[Mqtt Tasmota Bridge xxx@Temp. Warmwasser@Temp. Warmwasser@Current Relative Humidity] characteristic value expected valid finite number and received "NaN" (number)
7.2.2024, 11:07:18Mqtt Tasmota BridgeFEHLER[Mqtt Tasmota Bridge xxx@Temp. Warmwasser@Temp. Warmwasser@Current Relative Humidity] characteristic value expected valid finite number and received "NaN" (number)
7.2.2024, 11:10:04Mqtt Tasmota BridgeFEHLER[Mqtt Tasmota Bridge xxx@Temp. Warmwasser@Temp. Warmwasser@Current Relative Humidity] characteristic value expected valid finite number and received "NaN" (number)

Is it regarding the missing Humidity, because it's only Temperature Sensor?

I would like to integrate a Sonoff relay with a temperature/humidity sensor. Tosmata is already on the device. Is there a way to make the device compatible with homebridge-mqtt-tasmota? I am already running an IFAN03 with the plugin and would like to use the same plugin.

First of all, thank you for a great plugin. Very easy to add all of my devices, naming, index etc.

But something I haven’t figured out is how to sync the device statuses. Lets say I use the wall switch or have a timer set up in the tasmota web interface then it wont change the status in HomeKit. I can see in the logs that MQTT is sending from the tasmota device but nothing is received in homebridge.

Is this a known bug/limitation or am I just missing something obvious?

Thank you!

are dimmer switch supported?

I was initially getting errors.

Error event on MQTT

I added logging of the error (e.message) which was Connection refused: Not authorized.

After some debugging, I saw that needed to add the URL (and username/password) not just to the accessory section but also to the platform.

The onConnect's config from the constructor is called both from the accessory and at the platform level during boot up.

I just installed MQTT Tasmota 0.4.6 on HB 1.4.0 (running on a Debian VM).

I created a test device called "test", set topic to "tasmota_%06X" as indicated on my switch (Treatlife SS02 running Tasmota 11.0). I lest the rest as default.

on my switch:

MQTT Host : 10.1.10.2 (HB server IP)
Port : 1883
User: DVES_USER
Client: DVES_DCC183
Topic: tasmota_%06X
Group topic 1: cmnd/tasmotas/
Full Topic: cmnd/tasmota_DCC183/
Fallback Topics: cmnd/DVES_DCC183_fb/
No Retain: Disabled

But it dosnet look like it's able to connect, in my HB logs I see:
Error event on MQTT connect ECONNREFUSED 127.0.0.1:1883"

What am I doing wrong?

Hello tested it, and it is on screen - switching the icons OFF/ON and so on, but it is not checking if that is really possible and if it is changed after clicking a button.
so, how can you be sure, that the device is answering ?
in my example, a tasmota device is loosing the WIFI, and is not reachable, but in homebridge it is showing the ICON as OFF or click on it, then goes to "ON", but you can't see if it works or not.

Is there no status check ?
eg: if device offline, then icon with "!" or whatever ?

cu

10:11:09 MQT: stat/lightAndrey/RESULT = {"POWER1":"OFF"}
10:11:09 MQT: stat/lightAndrey/POWER1 = OFF
10:11:10 MQT: stat/lightAndrey/RESULT = {"POWER2":"OFF"}
10:11:10 MQT: stat/lightAndrey/POWER2 = OFF

Sonoff T1 2CH Модуль

how to organize 2 switches?