Look at this. https://www.reichelt.nl/nl/nl/regensensor-12-v-dc-m-152-p118916.html?search=regensensor&&r=1 In combination with a RF switch as Zigbee, Z-Wave or 433MHz you have a good rain sensor with heating. And a 12 volt supply. I have just started to use one of these, wired to a Raspberry Pi ...

Intel NUC as master with RFXcom and Open z-wave dongle and Raspberry pi 2 as slave with zigate and also acting as the ha-bridge and no-IP duc.
Both using node-red to monitor each other and power cycle in the event of a crash.

My mistake guys. Counter icons cannot be changed. I used custom sensor and not a counter in my setup I think you made a mistake with this one too because a custom sensor cannot be updated with the info form your script resulting in the following error. Error (2.4.19): Method updateCounter is not ...

If you set the debug node to show the "Complete msg object and attatch it to the parse node then in the debug window you will see the elements of the data object, if you then expand this by clicking on it you will see at the bottom a section called "parts", expand that and you will see the "index ...

Just a small point. Whilst the 'Throttle' node limits the data to the first set the query comes across, which in the case of countries is today's data. It might be better to explicitly limit the data table selected by specifying a 'Switch' node between the 'Select country' and 'Parse' nodes to ...

ok, I understand now, but after the changes the function parse returns: "function : (error) "TypeError: Cannot read property 'replace' of undefined"" Check the array index numbers used in the 'replace' function. It sounds like one (or more) might be out of range. ie: not in the array. As the arrays ...

You need to look through the msg.payload.array by sending it to the debugging panel and then match the elements with the figures shown in https://www.worldometers.info/coronavirus/ for a given country. the array elements appear to be different to those that the OP has used. Below is the code from ...

I moved from a Raspberry Pi to a NUC a couple of years ago. From memory I think that with the 433mHz devices it was as simple as backing up the Domoticz database & plugging the Rfxtrx into the NUC, installing Domoticz then restoring the backup. I run Domoticz in Ubuntu. Out of interest, what are the ...

The device IDs for 'ARC' & 'X10' switches appear to be the ASCII decimal codes for the letters selected in the dialog to create the virtual switch, instead of the letters themselves. I thought that this just applied to Virtual switches when I mentioned it in the bug section last year.

@waarren Again sorry for the delay in replying. I had the 'Intruders' script set for every 5 minutes and another script to download "Dark Sky" weather every 10 minutes. Both were working up until 10:00 on Feb 17. At 10:09 on Feb 17 I updated Domoticz to beta 4.11896. After that I was getting the ...

@Warren, Thanks for your quick and helpful replies. The simple problem with the "Every minute" script was that I had not put curly brackets around 'every minute' The "every 5 minutes script" however still does not run at the specified intervals, it did before the last update. 'myHttpResponse' is ...

Sorry for the delay. After adding your code line to 'EventHelpers.lua' . The log now shows: 020-02-18 13:20:00.139 Error: dzVents: Error: (3.0.0) {"every 5 minutes"} 2020-02-18 13:20:00.139 Error: dzVents: Error: (3.0.0) every minute 2020-02-18 13:20:00.139 Error:EventSystem:i n/home/user/domoticz ...

There is the following error appearing in the log every minute after updating to Domoticz beta v4.11696 - dzVents 3.0.0 Error: EventSystem: in /home/user/domoticz/dzVents/runtime/dzVents.lua: /home/user/domoticz/dzVents/runtime/EventHelpers.lua:462: bad argument #1 to 'for iterator' (table expected ...

It's when you are creating a new switch 'manually' and you select the slave radio button. Then from the drop down that appears titled 'Device:' there is nothing to select. The screen you have shown is to select a slave device for a master (not too sure of the difference between the two approaches ...

This bash script will start a Fire TV box. 'keyevent' 26 is the command to wake it up. and the next line starts the BBC iPlayer (so can be ignored or changed to an app of your choice. #!/bin/bash adb start-server && \ adb connect <IP address of Fire TV> && \ sleep 0.5 && \ adb shell input keyevent ...

@waarren
I've just realised that in the 'Sendnotification' method the 'extradata' can be used to specify the device.

So in future I shall use that rather than curl.

Thanks for pointing me in the right direction.

@Kasvand
I've added reference to this to the Wiki page. Well done for creating it.

The risk of using curl directly in an event script is that you block the entire event system for the duration of the call. You are quite correct, I should have mentioned that. Although in my experience the Pushover API calls are handled in a negligible amount of time. It also allows for sending a ...

I know that this doesn't actually use the included 'Sendnotification' function but as a method it works well for me Call the function with: pushovernotify("0","Domoticz","message","1","my_phone")( Execute function with: --Send Pushover notification to a particular device function pushovernotify ...

This snippet should help: #!/usr/bin/python ### import requests ### #rest of code ### # Parse URL url = 'http://<DOMOTICZ_IP>:<PORT>/json.htm?type=command&param=udevice&idx=<YOURTEXTDEVICEIDX>&nvalue=0&svalue='+str(<YOURVALUE>)' # Send data to Domoticz device r = requests.get(url) Obviously change ...

Enabling the serial port fixed it for me. All working very well. Devices pair first time. Only problem is I have the PiZiGate on a slave Domoticz as my master Domoticz is on a Ubuntu machine and therefore even though the devices are shared they don't appear on the master, I believe this is due to ...