Closed rbressers closed 6 years ago
@rbressers What model of Envoy is it? If you have a minute can you pop over to https://github.com/jesserizzo/envoy_reader/blob/master/envoy_reader/envoy_reader.py and run that python script on the command line and see if it works for you. I believe I've got it supporting the original Envoy, the Envoy S and the Envoy IQ.
@jesserizzo I am using the Envoy-S model. The output of the script is not that hopeful
Enter the Envoy IP address, or press enter to search for it.192.168.1.105 Enter the model of the Envoy ('Original' or 'S'), or press enter.S Traceback (most recent call last): File "env.py", line 167, in <module> print("production {}".format(EnvoyReader(host, envoy_model) File "env.py", line 30, in production production = raw_json["production"][1]["wNow"] IndexError: list index out of range
@rbressers Ok, that's annoying. Seems like they changed the order of the json in a firmware update. Can you just in your browser go to http://envoy/production.json and paste the whole output in a comment here. Thanks for your help.
@jesserizzo The output is as follows :
{"production":[{"type":"inverters","activeCount":10,"readingTime":1535308263,"wNow":24,"whLifetime":1046748}],"storage":[{"type":"acb","activeCount":0,"readingTime":0,"wNow":0,"whNow":0,"state":"idle"}]}
@rbressers Ok, I don't think it's because of the firmware update. I think it's because you don't have the hardware in your main electrical panel that monitors your whole house usage. So you will have less information available.
Can you check one more thing for me. Does http://envoy/api/v1/production give you anything?
The URL gives me the following information:
{ "wattHoursToday": 12395, "wattHoursSevenDays": 78702, "wattHoursLifetime": 1046748, "wattsNow": 26 }
And it is indeed not the Envoy-S metered but the standard Envoy-S
@rbressers Ok, please try https://github.com/jesserizzo/envoy_reader/blob/master/envoy_reader/envoy_reader.py again.
That's more like it 😉
Enter the Envoy IP address, or press enter to search for it.
production 0
consumption Unavailable
daily_production 12395
daily_consumption Unavailable
seven_days_production 78702
seven_days_consumption Unavailable
lifetime_production 1046748
lifetime_consumption Unavailable```
Same result I got from the script and the S. looks like youre on the right track
Excellent, I'll submit a pull request today.
@jesserizzo I have a first generation Envoy that does not work correctly together with your envoy_reader.py. I have noticed your mention that it was only been tested with Envoy-S. Please review the information that I have posted here: https://community.home-assistant.io/t/trouble-with-enphase-envoy/67359/4 TIA
@nmichail I had added support for the Envoy-C a while back, but that got broken apparently after refactoring on the original branch. Just created a new PR to fix this at https://github.com/jesserizzo/envoy_reader/pull/3
Home Assistant release with the issue: 0.76.2
Operating environment (Hass.io/Docker/Windows/etc.): Raspbian Stretch in a Python virtual environment
Component/platform: enphase_envoy
Description of problem: Configuring the Enphase Envoy component results in traceback and error on startup.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: Envoy information : Software Version : R4.10.24 (21d507) Software Build Date : 21 Jul, 2018 2:55 AM