Hello, I can't find a way to place a new topic and how I have managed to put this, I can't reproduce. But there is a new problem in my energy dashboard after the new version of Domoticz (Version: 2025.1) My house does not get any energy as long as the solarpanels produce energy. Looking at the ...

And now i saw what was wrong, the device type "custom"I changed it in watermeter and it shows:
Thank you for showing me the way.

And here the widget

Now I was to quick to answer. The watermeter device in Domoticz has 2 values:
So, why not showing.

My watermeter does not combine 2 values, and therefore my device has only 1. The dashboard does not see's such a device and hence the disable.
How can I create that device, given the presence of more then one counter the actual watermeter send it to Domoticz?

Ah, I see. Forgot to tell that I have it in use, but the icon is not that of drop of water but just 4 squares. Wat I ment was that choosing the item "water" (the third option), shows only disabled. And choosing waterflow as a dummy does not appear eather, what seams to be logic. Please let me know ...

Thank you, it works fine.

The watermeter is another issue , and yes I have a watermeter in Domoticz for more then a year.
It is present in the energy dashboard, so why it's not to be handled here?
It is not that important to me, it's just a nice picture.

Hi, I have a few questions: 1, How to get a second convertor (there are 2 separated convertors) to feed from solar into my house? There is only one source available. 2, how to connect my watermeter from smartgateways, I can not choose it because I get at that line only “not connected” Thanks in adv ...

I used your @yahoo.com address but it bounced. "mailbox not found"
Here is a new zip with all the files that where changed today, including the last domoticz log

Oké, I will send all the files offline and in dos-format to

Looking at your instructions again, I realized I took the wrong m_file to use. Instead of m_mijnafvalwijzer.lua I selected m_mijnafvalwijzer_API.lua. (In But even after correcting this it's not working right. The Domoticz log changed in an interesting way, it shows (among others) Error: 1234AA not ...

I have followed your instructions but no succes.
The Domoticz logfile and the 2 files that where changed are here:
So tou can check if I did it right.

I installed the garbagecalendar on my raspberry pi and followed the instructions supplied. It does not work. JvanderZande offered suggestions for testing and debugging, which I all followed, including changing TLS-version. No result. The only solution left was sending the logfiles and the lua file ...

Final. I removed all devices, one by one at a time, and included them in another controller on another Raspberry Pi. A second mqqt-broker is neccesary to be able to use them. I have several Pi's working for me so that could be arranged By removing from the first controller I checked the presence of ...

The logging by mqtt-explorer shows this:
Socket error on client Domoticz-MQTT-AutoDiscover55c3b685-0702-4837-9171-d3afeafc95b612, disconnecting
Can this help?

The debug log from ZwaveJS shows this: 2023-10-28 10:19:30.193 ERROR MQTT: Mqtt client error connect ECONNREFUSED 192.168.1.217:1883 Error: connect ECONNREFUSED 192.168.1.217:1883 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) I have no idea what it means, but it must have ...

One would think so, but I have allready seen that post. It's not the solution in my case. I followed her steps and did the same. But Domoticz does not see the messages, only when I change the topic in section MQTT in "homeassistant" the discovery takes place, and no disconnections follows. this is ...

a Correction on switch behaviour, the commands (topic homeassistant in the setting) take place. The switches react to the command, but in Domoticz the bulb stays On.

I do not have any messages in mqtt topic Zwave, only when I use homeassistant as topic. Then I get the "discovered" messages of all my devices. But no reaction to any switch command. And after a while the disconnection and it starts all over again.

The previous post does not show my problem in the topic field and will be overlooked easyely. Hence this new post. I have Zwave JS UI in a Docker comtainer and it was fully satisfactory for more then a year. Then I did a upgrade to “Z-wave JS 11.9.2”. in the summer this year. That version also did a ...