OK - thanks and you're right: it works.
It only took some time... After adding the SolarEdge hardware, it took more than half a day for the devices to appear.
But they're there now!

hi all, Have an issue trying to get the SolarEdge API up and running. Following the Wiki and two previous comunity-posts haven't helped me yet. The wiki tells me that I should fill two fields: API key and SiteID. The former I did, the latter... isn't there? 2019-08-16 23_16_47-Domoticz.png Obviously ...

Seems to be solved in Domoticz 4.10798.
Had the same errors from my sensitive strip, not anymore since this version.
Thanks!

micksel wrote:Zedd, Can you share your modified script?

I actually altered the script in the Wiki page...

Nice alteration, Siewert, I'll implement that one as well.
It will save me from looking up all IP's and making them static!

This is the script I use: #!/usr/bin/python # Title: check_device_online.py # Author: Chopper_Rob # Date: 25-02-2015 # Info: Checks the presence of the given device on the network and reports back to domoticz # URL : https://www.chopperrob.nl/domoticz/5-report-devices-online-status-to-domoticz ...

To be honest: I haven't got a clue if that's the case or not.
Experience (meaning, the past few days) arping has worked flawlessly for me. Which doesn't mean that other versions than our Android 7 phones may provide different results.

The solution to this is to use something that does request a reply from your phone (or another device) and will get a response whether the device active or not. Arp-requests are generally answered by all phones, so why not use this? Indeed, checking with 'arp', only performs a lookup in an existing ...

Hi Guantolento, I think you need to do some reading-up on crontab and check the headers of check_device_online.py! The script works fine. You don't really use 'sleep' within crontab, you can just use crontab to start your scripts at the desired time. Second, the check_device_online.py-script ...