I had the same issue since October 2024 with my Qubino flash rgbw dimmer. As you said 9.18.1 is working well. Not sure if somebody from Domoticz is taking care on this issue. So we need to stay with 9.18.1 until it's solved in Domoticz

@Ewout Have you found a solution which works?

I have the same issue with the newest ZWAVE js ui and I am gone back to 9.18.1 which worked for me again. It seems to be a zwave is ui problem. I have reported thtat month ago to Zwave Js ui as a bug.

okay. I am operating the Hiki Tasmota device in combination with the openDTU for my Hoymiles device. To get the data from Hiki is one thing to have the data in the energy dashboard another. But this is a seperate issue. In the Hiki device I have only enabled the MQTT parameters nothing else. Then ...

The Tasmota device is sending the Data and i can read them with the Mqtt Explorer. With MqttMapper i can transfer the data to Domoticz.

Would be nice to have the choice between UK / EU decimal seperator.

Great! I was wondering more than a year now how to get readings of my (belgian) Gas meter that stands outside the house. I currently rushed off today to get this working. Broke the glass of the reed contact when trying to get it to read the gas meter. Bummer. I will also attach a 2xAA battery unit ...

@FlyingDomoticz I need another time your help. After you helped me to get the "curr_w" added to devices, I added two new devices for "total_kwh" and "export_total_kwh". I found no chance to add this both and the python file checker told me Checking MqttMapper.json Duplicate tele/Hichi_F42ED0/SENSOR ...

@FlyingDomoticz I need another time your help. After you helped me to get the "curr_w" added to devices, I added two new devices for "total_kwh" and "export_total_kwh". I found no chance to add this both and the python file checker told me Checking MqttMapper.json Duplicate tele/Hichi_F42ED0/SENSOR ...

Who the hell is so experianced to understand this details. This did the trick. Thanks a lot.

this is the error log 2024-08-25 12:33:46.063 Error: Mqtt Mapper: Can't find >curr_w< in >{'Time': '2024-08-25T11:33:45', 'SML': {'server_id': '0a01484c590200155d58', 'export_total_kwh': 0.0, 'total_kwh': 1771.478, 'curr_w': 953, 'volt_p1': 236.1, 'volt_p2': 236.5, 'volt_p3': 234.7, 'amp_p1': 1.9 ...

Domoticz 2024.7 RPi3 bullseye I have no idea what's going on in this particular case. I was guessing the Error is coming from Open Weather Map. Any help is welcome. Domoticz is runing well and I have no idea where to start searching. 2024-08-24 17:40:05.558 Error: SQL Query("DELETE FROM Temperature ...

To help, i need (part of) configuration file showing the incriminated device, and content of MQTT topic used in configuration file. this can be seen in the console of the Tasmota unit 19:38:45.955 MQT: tele/Hichi_F42ED0/SENSOR = {"Time":"2024-08-23T19:38:45","SML":{"server_id":"0a01484c590200155d58 ...

They're 2 classical things that may cause issues: 1) published data is not marked as "retain". In this case, MqttMapper won't be updated until value changes. It's generally a good idea to flag topics "retain", as readers staring after last update could see last value. 2) you made changes into ...

that's exactly what I ment. With restart Domoticz it works but selecting it on "Hardware" tab and clicking on "Update" nothing happend at all. I am on RPI3 with the latest stable release. By the way if you read this email. I am fighting to read P1meter values from a tasmota device. P1meter topic.JPG ...

How can the MqttMapper be updated after changing the MqttMapper.json e.g. after adding a new device. Updating the Idx under hardware is not possible. Until now I deleted the Idx and re-entered it again. But in this case I get every time new devices in the database. Also activating/deactivating is ...

Anyhow, great support from your side and a very helpfull tool. Without it it's difficult to get Shelly Mqtt data to Domoticz.

I updated Domoticz to version 2024.7 and updated MQttMapper to the latest version like in your system. It's running well now. No idea what the reason was. Thanks for your help

your test script will generate the follwing error. : EventSystem: in Test.lua: [string "commandArray = {} ..."]:4: bad argument #1 to 'pairs' (table expected, got nil)

Many thanks for your continues work to find the problem. Sorry I was not clear on the topic content. Maybe the picture gives you the correct response.