The zigbee chip firmware is up-to-date. PG&E rep also read back the MAC and Install Code correctly, so it is unlikely that’s the cause. I will call PG&E on Monday and reprovision again. If that still does not work, I’d call Emporia and see what they would say about it.
Another thing to mention here: I am replacing my Rainforest device with Emploria. Rainforest is right now powered off. I mentioned this to PG&E rep as well, but it does not like this is a concern since it is powered off…
I would say bad device if you’re certain PG&E is doing their part. Emporia support is usually very helpful and will mail you out a replacement.
Called PG&E today. The official firmware is working now. But after flashing esphome. somehow it still reports the same error loop? I reflashed back the official firmware and it is back to normal again without the need to call PG&E to revision. Of course, I may be impatient since I did not wait for too long (maybe 2 to 3 loops of the join message after boot loop count is cleared, so total may be 5 loops of join message) before reflashing back the official firmware. Should I wait longer?
Setup debug level for logging and in the levels set Vue to debug as well
Interesting. Now I reflashed esphome, and it is working now. Weird. But glad everything worked out!
1 Like
An observation. It seems that the closest position may not be the best position for the device. For example, when I plug in to the outlet closest to the meter, it won’t be able to get any reading from the meter. However, if I plug in to the outlet that I used to place my rainforest HAN device, which is probably 30 ft away, it immediately starts to get the readings. I tried a few other outlets. One outlet that is merely 5 ft away from the closest outlet would work fine.
So, in short, if you see problems like error loop, you may want to try to move to another outlet and see, even if the other outlet it farther away from the meter.
I have SDGE and vue with official firmware stopped connecting to the meter recently. SDGE discontinued HAN connectivity and likely won’t be any help. I decided to flash esphome to see what was happening. It’s not connecting to meter, but i’ve seen value 0 and value 3 depending on location - assuming that’s not helpful?
[15:42:46][D][emporia_vue_utility:719]: Sending request for meter reading
[15:42:46][I][emporia_vue_utility:110]: Got error message (with value '3'). Move me closer to the meter for better reception.
If the emporia is disconnected from the meter, there is nothing that can be done.
The smart meter acts as the coordinator in this version of zigbee, so the utility provider has to initiate the provisioning process. Can you post more debug level logs? I cant tell if the meter is paired to the emporia and just not sending data or if theres no connection at all between the 2.
FWIW, I’ve never seen error 3.
[09:14:56][I][emporia_vue_utility:726]: MGM Firmware Version: 8
[09:14:56][I][emporia_vue_utility:727]: MGM Mac Address: xxx
[09:14:56][I][emporia_vue_utility:728]: MGM Install Code: xxx (secret)
[09:14:56][I][emporia_vue_utility:731]: Trying to re-join the meter. If you continue to see this message
[09:14:56][I][emporia_vue_utility:733]: you may need to move the device closer to your power meter or
[09:14:56][I][emporia_vue_utility:735]: contact your utililty and ask them to reprovision the device.
[09:14:56][I][emporia_vue_utility:737]: Also confirm that the above mac address & install code match
[09:14:56][I][emporia_vue_utility:738]: what is printed on your device.
[09:14:56][E][emporia_vue_utility:739]: You can also try asking for help at
[09:14:56][E][emporia_vue_utility:743]: https://community.home-assistant.io/t/emporia-vue-utility-connect/378347
[09:14:56][I][emporia_vue_utility:678]: Join response value: 1
[09:15:22][D][emporia_vue_utility:719]: Sending request for meter reading
[09:15:22][I][emporia_vue_utility:110]: Got error message (with value '3'). Move me closer to the meter for better reception.
I also got some MQTT broker errors which i filtered out. Is there another other debug level that shows more info?
Edit: i was getting error 0 initially, then moved it closer to the meter and got 3. Now moving it back to the previous location yields error 3.
Edit2: getting all the numbers in the further location
[09:22:11][I][emporia_vue_utility:726]: MGM Firmware Version: 8
[09:22:11][I][emporia_vue_utility:727]: MGM Mac Address: xxx
[09:22:11][I][emporia_vue_utility:728]: MGM Install Code: xxx (secret)
[09:22:11][I][emporia_vue_utility:731]: Trying to re-join the meter. If you continue to see this message
[09:22:11][I][emporia_vue_utility:733]: you may need to move the device closer to your power meter or
[09:22:11][I][emporia_vue_utility:735]: contact your utililty and ask them to reprovision the device.
[09:22:11][I][emporia_vue_utility:737]: Also confirm that the above mac address & install code match
[09:22:11][I][emporia_vue_utility:738]: what is printed on your device.
[09:22:11][E][emporia_vue_utility:739]: You can also try asking for help at
[09:22:11][E][emporia_vue_utility:743]: https://community.home-assistant.io/t/emporia-vue-utility-connect/378347
[09:22:11][I][emporia_vue_utility:678]: Join response value: 1
[09:22:15][D][emporia_vue_utility:719]: Sending request for meter reading
[09:22:18][I][emporia_vue_utility:110]: Got error message (with value '3'). Move me closer to the meter for better reception.
[09:22:20][I][emporia_vue_utility:110]: Got error message (with value '4'). Move me closer to the meter for better reception.
[09:22:20][I][emporia_vue_utility:110]: Got error message (with value '3'). Move me closer to the meter for better reception.
[09:22:24][I][emporia_vue_utility:110]: Got error message (with value '4'). Move me closer to the meter for better reception.
[09:22:33][I][emporia_vue_utility:110]: Got error message (with value '4'). Move me closer to the meter for better reception.
[09:22:42][I][emporia_vue_utility:726]: MGM Firmware Version: 8
[09:22:42][I][emporia_vue_utility:727]: MGM Mac Address: xxx
[09:22:42][I][emporia_vue_utility:728]: MGM Install Code: xxx (secret)
[09:22:42][I][emporia_vue_utility:731]: Trying to re-join the meter. If you continue to see this message
[09:22:42][I][emporia_vue_utility:733]: you may need to move the device closer to your power meter or
[09:22:42][I][emporia_vue_utility:735]: contact your utililty and ask them to reprovision the device.
[09:22:42][I][emporia_vue_utility:737]: Also confirm that the above mac address & install code match
[09:22:42][I][emporia_vue_utility:738]: what is printed on your device.
[09:22:42][E][emporia_vue_utility:739]: You can also try asking for help at
[09:22:42][E][emporia_vue_utility:743]: https://community.home-assistant.io/t/emporia-vue-utility-connect/378347
[09:22:42][I][emporia_vue_utility:678]: Join response value: 1
[09:22:45][D][emporia_vue_utility:719]: Sending request for meter reading
[09:22:48][I][emporia_vue_utility:110]: Got error message (with value '2'). Move me closer to the meter for better reception.
[09:22:50][I][emporia_vue_utility:110]: Got error message (with value '0'). Move me closer to the meter for better reception.Emporia seems provisioned, so it’s an error we know nothing about. There’s nothing that we can do on client side, when emporia asks the meter for a reading, it’s returning an unknown error.
i figured. thank you for checking.
I know it’s been a long time, but I was able to fix the issue of missing solar production data. I updated my original post with details.
tl;dr I suspect that MGM Firmware v2 didn’t support solar production. I upgraded by flashing back to stock which triggered an mgm firmware update, then flashed back to esphome.
2 Likes
Good that it works now for you! I’m confused why you had to call to reprovision each time you changed the firmware as the firmware change doesn’t impact the pairing status, but whatever I suppose.
Regarding MGM Firmware v2, I bet it did have the necessary data but the field was never identified in the payload. To quote myself from an old post:
That said, this payload has separate fields for the consumption and production totals. So those of you who say that kWh Returned is always staying at 0, I believe somewhere in your 152 byte payload there is a field that is counting up the produced total and we just need to find it and use it. Happy to discuss the approach if anyone is interested in trying to figure it out.
But updating the stock firmware is certainly easier.
Curious if anyone else has seen the logging data I’ve seen with mgm V8. I wonder if I got a board that has the mgm UART logging setup.
You’ll know because the emporia won’t return any meter readings, just errors in the log about incorrect data. I have a workaround, but I am interested to see if anyone else has the mgm UART logging happening.
The log messages are from the zigbee se stack, as I see “EMBERNET” quite frequently in the ASCII converted data.
@monkeyst - what would it take to have your repo compatible with esp-idf? This would allow the vue connect to also be a Bluetooth proxy for Bermuda presence detection.
I can possibly spend some time this weekend looking into it, just thought I would mention it.
I have zero familiarity with what the distinction is between esp-idf and arduino so would have to research, but my 2 cents:
- A ~$4 ESP32 devkit seems like the most cost-effective option when compared to the time cost of porting the code to a different framework just to support a non-power-meter-related feature.
EDIT: Is it also worth breaking compatibility (requiring everyone to pay attention and update their YAML to use the esp-idf framework)? - Curiosity is piqued. Optimistically it couldn’t be too hard to switch over since IIRC we just need to be able to talk over UART and have basic GPIO functionality for LED control. I’ll maybe give it an hour tonight and see where I get.
Gave it a shot, wasn’t too bad.
Leaving it as a branch for now since there isn’t much reason to break existing users.
The example YAMLs show how to use the branch, which is mainly:
external_components:
source:
type: git
url: https://github.com/nekorevend/esphome-emporia-vue-utility
ref: esp-idf
EDIT: Ah, so the esp-idf code works with either framework. Neat, I can merge the branch later but it’d be cool if you could confirm the change enables you to do what you want @baudneo.
1 Like
Awesome, thanks. The reason I would prefer on the same device is to limit extra wifi devices. Between esphome, openbeken and some other random IoT devices, I’m around 90 ish devices connected to wifi.
I’ve been slowly combining esps and removing devices that had a single task to clear up the airwaves a bit. Not sure if it will solve my problem of congestion (in a city, neighbours are close), but it’s a start.
I’ll upload the code tonight and check. Just a fyi for anyone else reading this, you need to flash the esp with a cable when switching between Arduino and esp-idf (different partition layouts). Idk if it will fail or actually flash OTA when switching and just act weird, I’m just going off the esphome docs for that info.
This is news to me! In my brief testing, I did OTAs back and forth and it seemed to work fine… I had even renamed the sensor entities, so I know it didn’t just fail the OTA and boot the old version.
I think your right, I just checked docs and no mention. IIRC, someone was helping me troubleshoot an issue and told me that’s what esphome called for, it worked, so I stuck with it.
I think the only thing needed, if a person is having issues, is to clean build files. Which is great news because I’ve been taking devices down or out of places that were a PITA, when I could of just used OTA.