Same thing happened for me 9:30am today.
I have somewhat recovered by not using the integration and using restful sensors instead.
I’ll do a write up soon of how I solved it.
3 Likes
I managed to integrate the Envoy by using the custom integration “Enphase Envoy (DEV)”. However, now the updates from the Envoy are every 60 seconds or so. If anyone knows how to get back to updates every second I’d appreciate it 
I never managed to get updates every second with fw 7. About every 15-30 seconds is as good as it gets for me. Would love to hear a solution but I’m afraid it’s limited by the controller.
With version 5 I managed to get them in real time. How do you get them every 15-30 secs with v7?
O man, real-time what a joy! I use GitHub - posixx/home_assistant_custom_envoy and REST sensor.
1 Like
Thanks, it works like a charm
My envoy-s updated as well some days ago whilst I was away on holiday to version D7.6.175
I’ve added possix repo to hacs and when setting up i’m getting “Device already configured”
Do I have to delete the device from home assistant and add it again?
Thanks for any help
Delete the old integration first.
1 Like
Hi all, I had to reconfigure my Envoy integration some days ago after the upgrade of the firmware to v7. I’m using GitHub - posixx/home_assistant_custom_envoy. The integration works fine but every day I get a disconnection at the same time (23:02) and then some parameters become unavailable unless I restart HA. Does anyone else face anything similar?
I just saw this wonderful post Enphase Envoy with Energy Dashboard - #662 by del13r from @del13r and I expect everything is solved
1 Like
Hello guys. Mine stopped working a few days ago. I presume its due firmware upgrade. I now see I have live view of usage in the app or maybe I missed it previously. Can someone post a detailed what to do to get it working again please? I dont want to break fancy dashboard I have for envoy.
thanks
I highly recommend you to take a look at the link I shared in the post previous to yours.
1 Like
Yes, i upgraded to the mentioned integration without problems; all data and entity names were preserved. Remove the current integration, add new source in HACS, install (i chose MAIN version so i was up to date with latest patches not yet released).
I did change the update interval from 60 to 30 seconds like i was used to with posixx.
Like @vbh (thanks for the summary of steps to take), I also migrated from the deprecated posixx to the “briancmpbll” version. All good and up and running.
Note that v.0.13 has configurable “Update intrval”, no need to manually change it anymore in the “init.py” file.
Good to see that our hardworking coding community has gathered forces and we are on one flow now.
tnx
John
@bokepasa79 Same behaviour noticed here. I am using Evoy-S-metered-EU, on V7,x since it was installed, - these things seem to restart itself every day around 23:00 local time. As such not a big issue, I learnt to live with it, as during that time I have zero Solar production ongoing. Unavailability of the sensors is mostly 1-2 minutes.
HOWEVER - I am using the “Current production xxxx” sensors as input to my energy dashboard. First to a Rieman Sum helper, who then feeds into the final helper which is configured as utility meter which feeds my Energy Dashboard.When the “Current production xxx” becomes unavailable, the Rieman helper becomes unavailble. Understandable, and correct behaviour.
When the Envoy “Current production xxx” becomes available again at about 23:02, it comes available with a value of 0 (zero). The Rieman Sum helper will not trigger on this to also become available, it does so in the early morning when it sees production > 0 value coming in. You might want to leave your system untouched overnight to see if it has exactly this behaviour.
My solution for this:
I run an automation (limited to be triggered onyl during 22:50 - 23:10), which triggers when my Rieman Sum helper becomes unavailable. Then it waits a couple of minutes, checks if Envoy Production xxx is available, and calls a service as per below to force the Rieman Sum helper to update itself. It does that with the new value of 0 (zero) of “Current production xxx”.
I hope I explained it in an understandable fashion, and it helps you.
grtz
John
1 Like
Alrighty guys,
Here is the fully manual solution I came up with using just the rest sensor for Enphase Envoy on D7 firmware.
It’s a lengthy guide with lots of explanation.
Hopefully it helps someone else out.
1 Like
I see that home assistant 2023.9 has updated the official enphase integration to support newer firmware. It seems logical to try to move towards the official integration, however I am afraid of losing the historical statistics for energy usage. Does a migration path exist which minimises loss of data ?
1 Like