jrouvier / esphome-emporia-vue-utility

Alternative ESPHome firmware for the Emporia Vue Utility Connect
GNU General Public License v2.0
75 stars 17 forks source link

Cannot re-connect to meter #16

Open rdeserm opened 5 months ago

rdeserm commented 5 months ago

When I first set this up it worked great the first time, despite a few disconnections that I think were the fault of PG&E.

Eventually, it got disconnected and since then the utility company has not been able to re-pair my device to the meter.

They recently replaced my meter with a new one, no improvement.

Here is the error log that I'm getting:

[13:45:58][D][Vue:445]: Got meter join response
[13:46:03][D][Vue:496]: Sending request for meter reading
[13:46:08][D][Vue:496]: Sending request for meter reading
[13:46:13][D][Vue:496]: Sending request for meter reading
[13:46:18][D][Vue:496]: Sending request for meter reading
[13:46:23][D][Vue:496]: Sending request for meter reading
[13:46:28][D][Vue:496]: Sending request for meter reading
[13:46:33][I][Vue:503]: MGM Firmware Version: 2
[13:46:33][I][Vue:504]: MGM Mac Address:  70:B3:D5:EB:80:00:33:14
[13:46:33][I][Vue:505]: MGM Install Code: 50:A4:B9:98:DA:14:90:53 (secret)
[13:46:33][I][Vue:506]: Trying to re-join the meter.  If you continue to see this message
[13:46:33][I][Vue:507]: you may need to move the device closer to your power meter or
[13:46:33][I][Vue:508]: contact your utililty and ask them to reprovision the device.
[13:46:33][I][Vue:509]: Also confirm that the above mac address & install code match
[13:46:33][I][Vue:510]: what is printed on your device.
[13:46:33][E][Vue:511]: You can also file a bug at
[13:46:33][E][Vue:512]:   https://forms.gle/duMdU2i7wWHdbK5TA

I'm curious if anyone has some insight on what could be going on? It would take considerable effort to get the device closer to the meter and it appears that it is getting a "join response" from the meter. I've reinstalled esphome on the device, done hard resets, etc.

Thanks

baudneo commented 3 months ago

You need to reflash the old stock emporia firmware onto the device to enable the repairing process. This firmware only asks the zigbee chip to request a reading from an already paired meter.

Reflash the old firmware, repair and amke sure it all works and then reflash this firmware so it can continue reading.

dblinick commented 3 months ago

Anybody have a copy of the original firmware? I am having the same issue and not quite sure how to flash back to the stock firmware?

baudneo commented 3 months ago

What version does your MGM chip say it is? I have firmware for mgm v2 and V8. Can also give you the command to flash stock FW.

dblinick commented 3 months ago

The command would be great... I will check on the chip when i get home this evening.

Thank you!

On Fri, May 31, 2024 at 12:58 PM baudneo @.***> wrote:

What version does your MGM chip say it is? I have firmware for mgm v2 and V8. Can also give you the command to flash stock FW.

— Reply to this email directly, view it on GitHub https://github.com/jrouvier/esphome-emporia-vue-utility/issues/16#issuecomment-2142899947, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADSHDF6X4ZHNWX2G7WA75RLZFDJABAVCNFSM6AAAAABE4KXRJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHA4TSOJUG4 . You are receiving this because you commented.Message ID: @.***>

baudneo commented 3 months ago

In the above log output you can see how it reports MGM version: 2

[13:46:33][I][Vue:503]: MGM Firmware Version: 2
[13:46:33][I][Vue:504]: MGM Mac Address:  70:B3:D5:EB:80:00:33:14
[13:46:33][I][Vue:505]: MGM Install Code: 50:A4:B9:98:DA:14:90:53

That's what you'll be looking for in the esphome log output.

dblinick commented 3 months ago

It is version 2

baudneo commented 3 months ago

https://github.com/baudneo/esphome-emporia-vue-utility/blob/firmware-backup/firmware%2F06-27-2023%2Ffw-backup-4M-emporia.v2.bin

One sec for the command. You'll need to install esptool using pip.

baudneo commented 3 months ago

esptool.py --port /dev/ttyUSB0 --chip esp32 -b 115200 write_flash --flash_freq 80m 0x0 {path to file}

you might need to change the --port and obviously change the {path to file}

dblinick commented 3 months ago

awesome - thank you!