Domoticz

Posted: **Friday 04 December 2015 9:49**

did you fill in your SiteID?

please post the code of your script.

Posted: **Tuesday 08 December 2015 16:03**

i get in de log from domoticz:

Error: SolarEdge: Unknown Type: 0061
SolarEdge Something not handled correctly, having extra bytes!

Anyone got a clue what error 0061 might be

Am running Domoticz Stable; 3530

I have the same issue I think that the code doesn't handle odd/uncoded updates from the SE.
Also, like some others have reported I get periods of no updates (in the log) and in the dashboard - when it is not so sunny I get maybe 3 updates a day. Seems to tally at the end of the day OK though.
When I set it up it did take about 15 minutes to report the SE devices and I would say best to set this up on a sunny day

Posted: **Tuesday 08 December 2015 22:21**

This appears to be happening constantly now and I get the following too:

2015-12-08 21:13:13.109 Error: SolarEdge: Unknown Type: 1283
2015-12-08 21:13:13.109 Error: SolarEdge: Something not handled correctly, having extra bytes!
2015-12-08 21:13:13.255 Error: SolarEdge: Unknown Type: 0061
2015-12-08 21:13:13.255 Error: SolarEdge: Something not handled correctly, having extra bytes!

The error 1283 is a new one I noticed and the usage has not updated since 12:05 today. Anyone else get this error and know how to resolve it to get it working?
The actual pass through works fine as I would expect and a reboot of the box has made no difference.

The only thing I did was add a HGI80 USB this morning, the updates were fine on solar for about 2 hours then stopped. The HGI works fine.

Posted: **Wednesday 09 December 2015 15:27**

If I run the python scripts from https://github.com/jbuehl/solaredge manually it seems to work fine. I run seconvert2 with -vvv options and then every update I see corresponds with values I see on the SolarEdge monitoring site. I had similar problems like extra bytes in the beginning,. It turned out that the python scripts were written for an older SolarEdge inverter which uses a slightly different protocol. After the writer of the script(s) made some updates it's working fine now. In this issue https://github.com/jbuehl/solaredge/issues/4 there is a description of the current protocol. Maybe someone can 'translate' the way the python scripts do the decoding into C++ so that it can be incorporated in Domoticz

Posted: **Thursday 17 December 2015 0:37**

I've had HW-failure on my SE-3000 comm-interface, new card was installed few months ago, with that new firmware...since then previous method of Domoticz scraping data (port 2222 & Fwd to solaredge.com ) doesn't work anymore. Probably due to SE update/version on newly installed interface board.
As mentioned by others, FWD still works (I can read correct data from SE portal with App), but Domoticz(2.3530) isn't able to filter out the data anymore...
(Unknown type: 0061 | Something not handled correctly, having extra bytes)
So I want to move to API readout, but as it seems , the offered method in this thread writes to a file every update. I don't like that (R-pi with SD)...
Anybody already changed this to work without writing to file each cycle?

thx for yr suggestions/ideas?

rgds, Robert

Posted: **Thursday 17 December 2015 9:01**

The unknow type 61 is under investigation.
I moved to the api and that is also working without problems.

Posted: **Tuesday 22 December 2015 23:11**

Antwan, I see you have R-pi also, not worried about the frequent write-operations to SD card ????

Posted: **Wednesday 23 December 2015 15:15**

Nope, running for ages.

Posted: **Wednesday 23 December 2015 19:51**

RobertT wrote:I've had HW-failure on my SE-3000 comm-interface, new card was installed few months ago, with that new firmware...since then previous method of Domoticz scraping data (port 2222 & Fwd to solaredge.com ) doesn't work anymore. Probably due to SE update/version on newly installed interface board.
As mentioned by others, FWD still works (I can read correct data from SE portal with App), but Domoticz(2.3530) isn't able to filter out the data anymore...
(Unknown type: 0061 | Something not handled correctly, having extra bytes)
So I want to move to API readout, but as it seems , the offered method in this thread writes to a file every update. I don't like that (R-pi with SD)...
Anybody already changed this to work without writing to file each cycle?

thx for yr suggestions/ideas?

rgds, Robert

I've created a RAM-disk of 1 Mb through fstab, mounted somewhere in the filesystem and I'm writing the temp-file there. Works fine. I use Ubuntu Linux and a guide was here: http://www.jamescoyle.net/how-to/943-cr ... k-in-linux
I expect this to work on a Pi as well

Posted: **Wednesday 23 December 2015 20:17**

I'm trying to get my solaredge inverter on Domoticz. Use the API method, I see a 'worker started' in the log files and checked the api key if it is delivering an xml. Everything seems to be ok.
the only thing I'm not sure about, I have a 3 phase 5000 inverter, I thought I read something that only single phase inverters are working at the moment?

Can somebody confirm? I Don't see devices added when I have configured the hardware.

Posted: **Wednesday 23 December 2015 23:12**

When using the API, the solaredge should report directly to prod.solaredge.com or could it be passed through through the raspberry.
(Otherwise i need to change it back to prod.solaredge.com)

When passed through the RPI2, the data gets to the Solaredge monitoring site.

But in the RPi2 Log, the API reports, Invalid data recieved?

What could that be?

and for the settings, on serial number, it should be the SN from converter i presume? and should it be with (7F123456-CC) or 7F123456-CC
Site ID and API are set

Posted: **Thursday 24 December 2015 22:57**

SCS007 wrote:I'm trying to get my solaredge inverter on Domoticz. Use the API method, I see a 'worker started' in the log files and checked the api key if it is delivering an xml. Everything seems to be ok.
the only thing I'm not sure about, I have a 3 phase 5000 inverter, I thought I read something that only single phase inverters are working at the moment?

Can somebody confirm? I Don't see devices added when I have configured the hardware.

With the curl command in the script and the correct parameters in it you can receive the data on the bash command line. If it matches the values that the SolarEdge gives (especially the total amount), than it works.
Did you create a virtual device after creating the dummy hardware? You need the idx from tha virtual device in the scripts, in order to let data be assigned and visible.

Posted: **Wednesday 06 January 2016 21:11**

Hi all,

Recently we got a solaredge installation and i wanted to log the day and total kW production in domoticz which is running on a raspberry pi.
I did everything as Antwan described and in the domoticz log i see this every 15 min.:
2016-01-06 21:00:00.613 LUA: 2016-01-06 20:51:22 solar input E: 60291.0 P: 0.0
(during daylight is see some value at the end e.g. P: 35.5)

But the virtual device is not being updated and stays on 0 kWh for total and day production.
I tried both ID and IDX within the LUA script , but no effect.
Can anyone help me out?

Posted: **Friday 08 January 2016 8:56**

If you have a recent beta of Domoticz, it may be easier to use use SolarEdge via Web API in Hardware. That way there's no need for scripts nor uservariables. Only the SiteID, API Key and Serial number of your inverter, which you can find on the Solaredge monitoring website.

Posted: **Friday 08 January 2016 16:36**

Thanks for the tip!
Working now in just 40 seconds..

Posted: **Monday 11 January 2016 16:36**

Does the solaredge reports directly to the prod.solaredge.com
Or does it work also when passed through through the Raspberry? (This is how my setup is working now, or used to work.)

EDIT: Addition

The API, should that be a users API, or an Site API?
http://www.solaredge.com/files/pdfs/se_ ... ng_api.pdf (Page 5)

I Got a (new?) api key, but i still get invalid data. so i might got the wrong API?

Posted: **Monday 11 January 2016 17:46**

Zwollenaar wrote:Does the solaredge reports directly to the prod.solaredge.com
Or does it work also when passed through through the Raspberry? (This is how my setup is working now, or used to work.)

It does report directly to prod.solaredge.com.
I didn't try to pass it throught the pi.

Posted: **Thursday 21 January 2016 12:34**

After using the lua api script (working fine) I wanted to use SolarEdge via Web API in Hardware.
I did configured on two domoticz devices but no luck.
I mailed a long email with my supplier and he even had contact with SolarEdge helpdesk and they stated I have the site API. But still I get those errors:

2016-01-20 17:17:28.334 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:34:15.739 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:39:15.987 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:44:16.214 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:49:16.450 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:54:16.673 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 17:59:16.883 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey
2016-01-20 18:04:17.294 Error: SolarEdgeAPI: Invalid data received, or invalid SiteID/Serial/APIKey

What is wrong the api key is working on my mobile phone and on /lua/script_time_SolarEdge.lua?

Twimpy

Posted: **Friday 22 January 2016 11:47**

Anyone can help?
Domoticz on Intel V2.4273
Domoticz on Raspberry V2.4222
When something is wrong on my API key SolarEdge NL like to know to helping other customers.

Posted: **Friday 22 January 2016 13:37**

Some possible reasons:

Did you use quotes when you shouldn't
or spaces/tabs before/after

As the inverter Serial isn't used in the lua-script, are you sure it's the correct one?

Does this work in your browser? (substitute {siteId}, {serial} and {apiKey} with your own values)

Code: Select all

https://monitoringapi.solaredge.com/equipment/{siteId}/{serial}/data?startTime=2016-01-21%2011:00:00&endTime=2016-01-21%2013:00:00&api_key={apiKey}

[fixed]

Domoticz

SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number

Re: SolarEdge in Latest Beta / Port Number