Integration simply stopped working. Reloading times out.
asinla opened this issue · 4 comments
On Feb 5th the device became unavailable. I updated to the latest HA version in case that was the problem but the Custom Envoy integration will not load. The Envoy combiner is connected to wifi and reports correctly in the Enlighten app and Enlighten online web portal.
I am including a few lines of the Debug Log below with IP addresses crossed out.
Thanks.
024-02-06 20:20:23.496 DEBUG (MainThread) [custom_components.enphase_envoy] Finished fetching envoy Envoy 202316216865 data in 55.003 seconds (success: False)
2024-02-06 20:21:43.635 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Checking Token value: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:21:43.635 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token is populated: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:21:43.635 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token expires at: 2024-02-17 20:55:46
2024-02-06 20:21:43.635 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Detect Model running
2024-02-06 20:21:43.635 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] HTTP GET Attempt #1 of 2: https://192.168.xx.xxx/production.json?details=1: use token: True: Header: Timeout: 60 Holdoff: 0
2024-02-06 20:22:38.638 DEBUG (MainThread) [custom_components.enphase_envoy] Finished fetching envoy Envoy 202316216865 data in 55.003 seconds (success: False)
2024-02-06 20:23:59.107 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Checking Token value: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:23:59.107 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token is populated: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:23:59.108 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token expires at: 2024-02-17 20:55:46
2024-02-06 20:23:59.108 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Detect Model running
2024-02-06 20:23:59.108 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] HTTP GET Attempt #1 of 2: https://192.168.xx.xxx/production.json?details=1: use token: True: Header: Timeout: 60 Holdoff: 0
2024-02-06 20:24:54.109 DEBUG (MainThread) [custom_components.enphase_envoy] Finished fetching envoy Envoy 202316216865 data in 55.002 seconds (success: False)
2024-02-06 20:26:14.488 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Checking Token value: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:26:14.488 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token is populated: yJraWQiOi (Only first 10 characters shown)
2024-02-06 20:26:14.488 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Token expires at: 2024-02-17 20:55:46
2024-02-06 20:26:14.488 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Detect Model running
2024-02-06 20:26:14.488 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] HTTP GET Attempt #1 of 2: https://192.168.xx.xx/production.json?
The log that you shared shows indeed no replies are received from the Envoy and that HA ends the collection.
So it's not communication at all since Feb 5? Anything that happened then that may provide clue? Is the envoy firmware updated?Have you tried restarting the Envoy itself?
Although I doubt it will help if it ain't working since the 5th, try reducing the timeout or increasing the overall timeout. The log shows a timeout of 60 seconds but the overall loop is ended at 55 sec. So if it really needs more time then 55 seconds to reply make sure to increase the overall timeout, it should be longer then the timeout and account for the retries. Try setting it to 130 sec so 2 attempts can timeout completely. Alternative strategy is to set timeout to 20 seconds and leave overall at 55. But as said, if 55 sec is not enough one can wonder if more time will help.
Is opening http://envoy.local/info in your browser working?
Thanks, I'll try those settings and report back.
Nothing I know of has changed since then which is why I found it very weird. I am not home right now so cannot check the envoy.local.
Firmware is D7.3.467. I have no idea if it has been updated recently but I'll poke around some more and find out.
Cheers.
Ok...it seems to be working now after adjusting the timeout to 130 seconds.
Tomorrow when the sun is shining I will check the Custom Energy Card I use and make sure it's all good again.
Also, envoy.local/info works fine.
I'll make a final report back here tomorrow.
Have a good one!
Working again this morning. Thanks for the help.