I am using the SolarEdge API for a few months, works perfectly. But I still want to use the SolarEdge via LAN feature. updating every 5 mins sounds great! I changed the forwarding adress from my inverter and added the hardware, but it doesn't work. Is there anything I can do to debug? Nothing ...

Can someone provide me the V2 version of the Solaredge Configuration tool? (Please PM)

Thanks!

I am using the lua script posted above to check the hue status directly from the bridge. This is done every minute.

This is still a workaround. Can I be of some help somewhere?

I have got this kind of integration as well. The problem is that when I switch lights using non-Domoticz Apps, like Philips Hue app or Hue-TAP, I would like the status in Domoticz to be changed. The status changes, but it seems only visual, not in the database. This makes it unable to use the state ...

thanks! using latest stable version: v2.3530

I tried: if(devicechanged[]) --> never executes (of course in device script) commandArray = {} base_url = 'http://192.168.1.57/api/&&APIUSERKEY&&/' domoticz_url = '192.168.1.58:8080' if(devicechanged['Betty']) then -- Only store the pattern if the light is already on -- Only load libaries now io ...

Note that I have commented out the if statement that checks for the device update. Meaning it now runs every minute. Code is very rough, full of dirty comments and unneccesary print commands... sorry for that :) replace: $$APIUSERKEY$$ with your philips hue user ID note that the hue bulb I am ...

When I am changing my philips light bulbs using other software than domoticz (for instance via Hue app or via Hue Tap) I can see that the status of the light bulbs change in domoticz. That is good! However, I can't use it in scripts. It seems that only the GUI of Domoticz is updated, but not the ...

did you fill in your SiteID?

please post the code of your script.

Working LUA script Above LUA script works perfect, except for one thing: it checks every 15 minutes for an update, at .00, .15, .30 and .45. new information on the website is available shortly after, so let's say at .01, .16, .31 and .46. Information from the Solaredge is thus delayed by minimal 15 ...