Installs, identified devices and entities but not polling information, checked again after 24 hours #39
Comments
|
Weird. No errors in the HA logging? Did you try a restart? |
|
Yep, weird. I have restarted, deleted and reinstalled the integration. HA log examples;
Stupid question: Is there a common SolarEdge cloud or are Australians perhaps operating a different format? |
|
Not sure, i think there is only one cloud. Im working one some issues and will add while i'm fixing those add some more logging. There is an error but its not logged. |
|
With the latest version it should return some more error logging. Could you check if that is true? |
|
I updated to version 1.2.3, enabled debug logging and restarted Homeassistant.
My setup on a Raspberry Pi 4B |
|
Oh damm.. ik hoped the error would be visible with the latest version. Could you perhaps send me the response of: |
|
Yep, before I do, perhaps you know the answer; how much of my site info can I share publicly before risking external interference by a bad actor? I had a visitor the other day taking a photo of one of my inverters' ID tag. I do not know this person at all and wonder what the risk is? Can I DM you the response? |
|
Uhm, thats weird.. I thought you can acces the internal accespoint of the inverter if you scan the ID-tag with set settapp from solaredge. At least, with the latest inverters. But you have to manualy switch that red switch. But im not sure... Yes, you can DM me the response! |
|
I too have this same issue -- i can help with any troubleshooting if needed. |
|
I will try to push a release today where there is more logging so hopefully you will see the real error/reason why the integration is failing. |
|
Ping, if there are any other tests I can do to help? |
|
I was way too busy with work and private matters unfortunately. From this weekend it will be quieter and I will pick up some stuff again! Sorry for the inconvenience and yes if I need your help I will let you know. |
|
@ProudElm any update? still no recording of data: |
|
No, i could not find any poblems. I'm on holliday so i could have more time. I Will take an other look. |
|
adding Debug log -- not sure how helpful it it. Removed the site id. is this failing in the Sensor.py in lines 176-179 ? except Exception as err:
_LOGGER.error("Error in updating updater")
_LOGGER.error(err)
raise UpdateFailed(err) |
|
I think I found something. Changing the 60 to 300 on line 148 in the sensor.py allowed me to get results. try:
# Note: asyncio.TimeoutError and aiohttp.ClientError are already
# handled by the data update coordinator.
# changing form 60 to 300 to increase time out.
async with async_timeout.timeout(300):
_LOGGER.debug("Update vanuit de coordinator")
data = await self.hass.async_add_executor_job(
self.my_api.requestAllData
)
|
|
Here is my log from re-installation this morning.
|
|
See indeed issue #47. I think this could indeed fix it. I will try to publish something from my holiday address. I cannot test it, my dev environment is broken. |
|
...and now it works for me. Thank you. Where do you discuss automations related to the optimizers, eg. sending a message if one panel suddenly drops in production indicating a hardware fault? |
|
Not sure. i really dont have a place for that. Perhaps make an issue and then we can do it there ;) |
Current is Unavailable
and the other metrics are Unknown
thank you for this initiative!
The text was updated successfully, but these errors were encountered: