I’m not sure why, but I’m getting two calls to the API one minute apart? I’ve set the live polling interval to 10 minutes, and each of these live calls is happening every 10 minutes. I’d completely wiped my setup and any links, I can see in the logs the Thing being initialised only once, so not sure why the second call is being triggered?
2018-06-28 10:09:03.433 [DEBUG] [dge.handler.SolarEdgeLiveDataPolling] - polling SolarEdge live data org.openhab.binding.solaredge.config.SolarEdgeConfiguration@147bcc7[tokenOrApiKey=GeneratedAPIKey,solarId=123456,meterInstalled=false,usePrivateApi=false,live data pollingInterval=10,aggregate data pollingInterval=120,asyncTimeout=120,syncTimeout=120]
2018-06-28 10:09:05.190 [DEBUG] [nal.callback.AbstractCommandCallback] - received content, length: 271
2018-06-28 10:09:05.195 [DEBUG] [nal.callback.AbstractCommandCallback] - HTTP response 200
2018-06-28 10:09:05.198 [DEBUG] [nal.callback.AbstractCommandCallback] - onComplete()
2018-06-28 10:09:05.202 [DEBUG] [nal.callback.AbstractCommandCallback] - JSON String: {"overview":{"lastUpdateTime":"2018-06-28 09:56:50","lifeTimeData":{"energy":4143099.0,"revenue":384.4251},"lastYearData":{"energy":3842267.0},"lastMonthData":{"energy":457852.0},"lastDayData":{"energy":2372.0},"currentPower":{"power":1855.4329},"measuredBy":"INVERTER"}}
2018-06-28 10:09:05.212 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Handling channel update.
2018-06-28 10:09:05.217 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_year#production: 3842.27
2018-06-28 10:09:05.222 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: live#production: 1.86
2018-06-28 10:09:05.230 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_day#production: 2.37
2018-06-28 10:09:05.241 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_month#production: 457.85
2018-06-28 10:09:05.249 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_week#production: 0.0
==> /var/log/openhab2/events.log <==
2018-06-28 10:09:05.249 [vent.ItemStateChangedEvent] - SE5000H_Live_Production changed from 2.2 to 1.86
2018-06-28 10:09:05.271 [vent.ItemStateChangedEvent] - SE5000H_Today_Energy changed from 2.03 to 2.37
==> /var/log/openhab2/openhab.log <==
2018-06-28 10:10:00.163 [DEBUG] [dge.handler.SolarEdgeLiveDataPolling] - polling SolarEdge live data org.openhab.binding.solaredge.config.SolarEdgeConfiguration@1bfd7b7[tokenOrApiKey=GeneratedAPIKey,solarId=123456,meterInstalled=false,usePrivateApi=false,live data pollingInterval=10,aggregate data pollingInterval=120,asyncTimeout=120,syncTimeout=120]
2018-06-28 10:10:00.961 [DEBUG] [nal.callback.AbstractCommandCallback] - received content, length: 271
2018-06-28 10:10:00.970 [DEBUG] [nal.callback.AbstractCommandCallback] - HTTP response 200
2018-06-28 10:10:00.972 [DEBUG] [nal.callback.AbstractCommandCallback] - onComplete()
2018-06-28 10:10:00.974 [DEBUG] [nal.callback.AbstractCommandCallback] - JSON String: {"overview":{"lastUpdateTime":"2018-06-28 09:56:50","lifeTimeData":{"energy":4143099.0,"revenue":384.4251},"lastYearData":{"energy":3842267.0},"lastMonthData":{"energy":457852.0},"lastDayData":{"energy":2372.0},"currentPower":{"power":1855.4329},"measuredBy":"INVERTER"}}
2018-06-28 10:10:00.985 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Handling channel update.
2018-06-28 10:10:00.993 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_year#production: 3842.27
2018-06-28 10:10:00.997 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: live#production: 1.86
2018-06-28 10:10:01.003 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_day#production: 2.37
2018-06-28 10:10:01.014 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_month#production: 457.85
2018-06-28 10:10:01.025 [DEBUG] [laredge.handler.SolarEdgeBaseHandler] - Channel is to be updated: aggregate_week#production: 0.0
The error “(COMMUNICATION_ERROR): Too Many Requests” which only affects setups with meter installed will be fixed in the next version. There will be a delay between subsequent requests to avoid that parallel query limit.
after some time i also had to upgrade to the latest 2.4 DEV version of the binding.
i have an older inverter so i use legacy mode.
i also have an API key so i used it in the configuration.
the binding is working fine, i got logged in and the data is showing BUT the values are coming as Wh and not as KWh
i have OH2.3 version now, the monitoring site language is English and this is also the API call return
2018-07-21 23:33:31.002 [vent.ItemStateChangedEvent] - Solaredge_Day_Production changed from NULL to 51669.73
2018-07-21 23:33:36.011 [vent.ItemStateChangedEvent] - Solaredge_Week_Production changed from NULL to 295468.276
2018-07-21 23:33:41.018 [vent.ItemStateChangedEvent] - Solaredge_Month_Production changed from NULL to 985069.8
Why am i now getting values in Wh ?
Is this having to do with UoM ?
hey guys,
i tried both 2.3.0 and 2.4.0 snapshot but i get problems with my openhabian when the binding is installed.
after a reboot my channels start to disappear and do not come back. when uninstalled binding every thing returns.
Hi @nick_woodforth: I need more details to analyze it. Logs, more details about your setup, bindings, versions, etc. I do not think this is a general problem as you are the first one reporting it.
@ngalfas: The easiest way to enable debug logging is to use the karaf console:
I have tried to use it, but I stuck at the connection part: I use OH on synology. This does not have a browser so I cannot use SPRING_SECURITY_REMEMBER_ME_COOKIE. I tried to add the value of my laptop’s browser’s cookie, but cannot connect with this.
Does somebody have any idea how to get this cookie without browser, or is there a possibility to use this bindings without this adding username/password?
The binding supports two modes. Depening on the mode you need either the Cookie or an API key. It does not matter if you retrieve the Cookie on your laptop and use it on your raspberry pi, synology NAS or whatever.
However, as I mentioned in the previous, I tried with the cookie of the laptop, but without success: I checked the value of SPRING_SECURITY_REMEMBER_ME_COOKIE for monitoring.solaredge.com (in chrome), and copied the value to the appropriate field on the binding’s formular.
After saving it says: “UNKNOWN, configuration error, invalid api key or solarId is not valid for this api key”. Session id is good.
Do you have any hints what could be wrong?
Well, it seems that your binding is configured to use the public API which requires an API key but you provided the token. So either use the API key or switch to the private API.
Great, thanks!
Now, I am a step further: “OFFLINE - COMMUNICATION_ERROR HTTP protocol violation: Authentication challenge without WWW-Authenticate header”
Could you please post your binding configuration (thing config is sufficient). Please mask your token/api-key.
Also I would like to see your logs. Please also mask your token/api-key there
I have a SolarEdge SE7K 3-phase converter (and optimizers on all panels) installed as of last week and I just wanted to report that it works fine in my setup. I’ve created an API key on the SolarEdge website and inserted it, along with the Site ID in the binding configuration.
That’s all (besides a sitemap entry to show values and graphs in Basic UI) it took for me. Since the API doesn’t support the optimizer I have no data on that at the moment.
