Domoticz

Hi,

I also have the same issue. I can make successful REST request manually. But Domoticz just starts and nothing more is shown.

/Xter

xter wrote:Hi,

I also have the same issue. I can make successful REST request manually. But Domoticz just starts and nothing more is shown.

/Xter

Dear All,

I get it work for me! Firstly I was also able to HTTP request with a browser and there was response.. But no success to get devices in Domoticz.
I ask to my installer support to verify the API KEY, if there was a SITE-API-KEY or a ACCOUNT-API_KEY.. Then I received a second API-KEY (I guess the site one), and with that Site-api-key it works in Domoticz, devices are there....

But with that key that allows me to get the devices, it doesn't work to HTTP request.. and also in Domoticz no values to my devices.. errors in the log.
I put back then the first key (I guess the account-api-key).... AND everythings works now !!!!

I hope it can help some of you

xter wrote:Hi,

I also have the same issue. I can make successful REST request manually. But Domoticz just starts and nothing more is shown.

/Xter

Same for me. Requesting data by giving in Site-id, Ser-nr and API-key works in browser. In Domoticz no new devices during 5 minutes. The log states that the worker has started though. I am using v3.6179 of Domoticz on Ubuntu.

EDIT: a reboot was required

ubfssF wrote:

xter wrote:Hi,

I also have the same issue. I can make successful REST request manually. But Domoticz just starts and nothing more is shown.

/Xter

Same for me. Requesting data by giving in Site-id, Ser-nr and API-key works in browser. In Domoticz no new devices during 5 minutes. The log states that the worker has started though. I am using v3.6179 of Domoticz on Ubuntu.

EDIT: a reboot was required

I solved this by using the right key... Actualy there is 2 different key for SolarEdgeAPI usage.. 1st is SITE KEY, 2nd is ACCOUNT KEY. I think you're using the account one which allow to request values. The site one you should use once in domoticz to get your devices...

Honestly, it is not very useful to get those devices... I also started with that but then, there is only PV actual watt available. I created my devices myself and it is much better..
os.execute('curl "https://monitoringapi.solaredge.com/sit ... key=APIKEY" > ' ..tmp_filename
with PowerFlow request you get all you need (PV-GRID-LOAD) values...

Hi,

to litfiba

Could you explain me how you exactly added your solaredge with catching your data directly from the homepage?
How do you forwardet to a device and how did you added such a device?
Because I have the same problem as many others with adding the solaredge into domoticz.
I tried following steps.
1. Edited the Server name on my inverter from prod2.solaredge.com to >IP of Domoticz<
2. Added the device Solaredge over API and tried both versions, with both API-Keys from my installer.
3. Never got any device after many restarts and Tries.

I always can only see Solaredge worker started - and nothing else...

Please

I had similar problems as mentioned in this thread. I asked my solar panel supplier the site API key. Didn't work. Asked them again for the Site API key, got another one. Did not work either. Huh, why? Site ID was correct. Checked the serial number, was spot on. Dubble checked the Wiki page and noticed they mentioned that the serial should look like: 1Z234567-8Z. Mine looked like ZZ1234-01Z234567-8Z. Just removed the ZZ1234-0 (zero) and it worked. Maybe this can help users in the future.

For me it helped to add the location into the configuration of Domoticz...

SolarEdge: monitoring installed OPTIMIZERS suggestion/request.

Is it possible to monitor the installed optimizers too ? The current Domotics SolarEdge system shows some nice things already, but it would be great if we can monitor the optimzers too: we had a dead optimizer last month...

If possible: the software could be expanded with some logic:

1) if an optimizer doesn't give power after 24 hours: it's not working -> error on Domoticz panel and sending an error message. This for detection of dead optimzers or/and solarpanels.

2) if the power of an optimizer is lower then (for example) 30% in compairing with the other installed optimizers -> error on Domoticz panel and sending an error message also. This for detection of
bad working or dirty solarpanels.

This all should be possible, because the installed SolarEdge system sends the data to the SolarEdge panel. But I am not sure if the SolarEdge API can return the optimizer details...

Arthur

Hi Forum,

I'm using the SolarEdge web API and it works as intended with the API key I received form my supplier.

I have a question though: according the the SolarEdge API description, there are data updates available in 15 minute increments. Yet, when looking in Domoticz, I note that data is updated every 5 minutes.

Is Domoticz actually obtaining new data every 5 or 15 minutes from the SolarEdge web api?

Domoberry wrote: ↑Friday 25 August 2017 10:41 Hi Forum,

I'm using the SolarEdge web API and it works as intended with the API key I received form my supplier.

I have a question though: according the the SolarEdge API description, there are data updates available in 15 minute increments. Yet, when looking in Domoticz, I note that data is updated every 5 minutes.

Is Domoticz actually obtaining new data every 5 or 15 minutes from the SolarEdge web api?

Looks like it tries to update every 5 minutes, which is actually exceeding this API usage limits. Are we able to have this configurable, i.e. update the frequency to collect new data?

Hello,

This week i installed an Ubiquiti Unifi Security Gateway (USG) after the installation the SolarEdge via Web API doesn't work anymore.
Probably this has something to do with the settings off the USG, but i have don't have any clue where to start

When i putt the api key in my browser i'am getting some data

You must also fill your site id into SITEID.
I also have probelems with reading data from the SolarEdge site.
It worked for a few hours and then it went dead. Even a new API kley did not solve the problem.