I already solved it. I don't need LUA. It works perfectly within Node-Red. I only oversaw my mistake. This solves the problem in the function-node: var moist = msg.payload msg.payload = {}; msg.payload.idx = 1036; msg.payload.nvalue = 0; msg.payload.svalue = moist; return msg; I had to save the data ...

You're not getting the point. I almost got it working. When I use my own data domoticz gets updated. But until now I'm not able to get in the data from HA. Only because I don't know how to filter the value from the message from HA. I fill it know with idx, nvalue, and svalue. I can even update ...

Maybe this helps someone to give me clues. I've downloaded the source from Node-Red. Please notice that there is still an ERROR in this code. I want the actual message (namely the correct humility) to be in the message sent to Domoticz to adjust the value. I already discovered that Node-Red is very ...

At this time, only the value of the sensor indicating the percentage of humidity. For this purpose I created a device (from hardware dummy) of type general, percentage (humidity). Once this works, I want to use more, because I've discovered that with the addition 'Nora' to Node-red, I can also use ...

I use both Home Assistant and Domoticz. Not all Xiaomi plant sensors can be reached from Domoticz. So I want to use the HA, which is in a different place to make the last 2 sensors also available in Domoticz. For this I use Node Red and MQTT. I get the data in the Pi on which Domoticz is running. I ...

I'm running Domoticz on a Raspberry 3 plus. That works fine, but I found out that after about a week the Domoticz application starts to run slow. I then do a reboot. Apparently the log is full or something like that. Now I actually want to automate this, but it probably takes me too much research to ...

Abortion! That was the problem. It runs for days now. It's my mainframe mind that made me use abortion I think.

I would like to reopen another subject, namely that relating to the MCZ pellet stove. The RFXCOM offers the possibility to control an MCZ pellet stove. I managed to find out the code and that part works. I get a message back. It is only not possible to create a virtual sensor in Domoticz so far. An ...

The Ring 2 service works in principle but I never know in advance for how long. Sometimes it's only half a day, sometimes it's 3 days, but in the end, despite a built-in restart, the service stops at an abort. This way I can't rely on the actions that have to be carried out when pressing the Ring ...

It works! I get an email with an image of the person who is pushing the Ring doorbell. The only thing that is left to do is making the script run as a service or as a part of PM2. Which I haven't been able to install yet. When I managed to do so I will describe how or sent the link. The link in the ...

I think I solved the last problem. I changed my password due to a character that was not recognized but I forgot to push the 'Done'-button. Now the script seems to be running endlessly but when I push the button on the Ring 2 nothing seems to happen. But no more errors!

This is what I've done: I downloaded the plugin from https://github.com/tchellomello/python-ring-doorbell. No errors. Left it where it was installed. As user pi and just to be on the safe side as root. The latter was not necessary because the plugin was already there. Then I changed the script of ...

That’s the same one I used. But how did you make it work after downloading the plug-ins from github and changing the script for personal use (User and password).

I own a Ring 2. However, I am not willing to pay for a subscription every month to see the call history. Now there is a plugin available for Domoticz to add the Ring 2. With a link to github to load the plugin on the Raspberry. I did that. I also changed the scripts and placed them in the scripts ...