emporia-vue-local / emporia-vue2-reversing Goto Github PK

Lot of modern routers allow setting up dedicated guest WiFi with MAC filtering and mark it hidden (Unifi network or TPLink Extenders), in which case something like NodeRed flow can process MQTT data and forward via MQTT or REST to HomeAssistant?

Would this work without needing any additional reverse engineering?

#NotReallyAnIssue

You wrote an article Reverse-engineering the Emporia Vue 2 dated Jul 28, 2021

Here you showed you can communicate with it without all the soldering connections to the vue.

I was wondering if you had considered any of the following.

1. Using Pihole or another local DNS solution you can change the IP address the devices gets and point it at home assistant or etc directly.
2. iptables has DNAT for which you can forward traffic from the local IP of the emporia device and the destination port of 8883 which you discovered.
3. Local DHCP server and then use the DHCP server to assign the emporia vue to a static IP which then makes IP and/or port forwarding even easier.
4. Raspberry Pi has built-in bluetooth, to connect to the emporia vue.

IP 192.168.1.20 (or whatever) to homeassistant.local (or etc via IP and/or DNS) and port 8883

If I don't want to change to a custom firmware, and I implement the above, which for me is easy, could we then have a local mqtt server and forward that to home assistant?

Can I use your wifi changer script to change the native wifi credentials without changing my firmware?

Hi and first of all thanks for all the work on this.

Love the results I am seeing so far... although it has revealed that I will need a more roomy breaker box to fit all these clamps.

I have an odd ball circuit in my kitchen that uses a dual pole breaker with phase A driving the top plug and phase B driving the bottom one.

So far I have not been able to figure out a way to get one clamp to read this outlet correctly. My latest attempt was to remove the multiplier and clamp around both wires but only one plug reports any draw. If I use the other plug I see my phase B total jump but the plug reports 0W.

Any tricks I can pull here or am I going to be forced to use 2 clamps?

Thanks again!!

Hello!
Could you please explain how did you setup the local network and bridge MQTT server with 192.168.1.101 address for getting the prod/minions/emporia/ct/v1/AAAABBBBCCCCDDDDEEEEFF/debug/v2 topic ?
Thank you!

Copied from #1 (comment)

Hello

I'm writing a driver for Berry's Emporia32. I read everything about the topic. I dumped the i2c bus. I reviewed cpp
and h files for ESPHome. Things are working out for me. But I have a few questions:

1. What are the indications for "Power data" used for in the accounts?
2. When I take the bytes of the data for "Current data" in the file "emporia_vue.cpp" it is commented that they are not multiplied by a factor, but the data I receive are: 69, 77, 82 ..... The reports are constantly floating up and down . The load I measure is 44W. In order to get the above statements true, I have to multiply by a coefficient: 0.0022. How do you consider the consumption if you do not apply a coefficient for the indication? If all goes well, I'll draw a Tasmota "C" driver.

Greetings Blagovest.

While not the vue2, I suspect the ev charger is probably pretty similar and am planning on tinkering about with it. Was looking at the internals and was curious if anyone had seen on their vue2 labeling like as follows for tx/rx/vcc/gnd before I go and start trying to figure out what pin is what. I am hoping left to right is what it looks like in the vue2 (3.3,5,tx,rx,gnd,en,io0). Feel free to close immediately if this is too off topic.

.

QUESTION: Does anyone know of any sources for similar reverse engineering efforts for the Emporia smart plugs?

Background

So, I've ordered a Vue 2 main unit, and managed to get through pulling the flash contents and working through the NVS. Thanks for the great work!

I've also ordered (they arrive later this week) the smart plugs though, as I've got a few hot spots that are on otherwise pretty broad circuits (e.g., my home office setup is on the same circuit as every light and plug on our second floor... 🤦‍♂️), and I'd like to use them for both monitoring and control.

My gut is suggesting to me that internally they are probably very, very similar since their features compared to a full unit seem very similar (so I'm expecting a similar ES32 with almost identical firmware, and a single current loop, with a relay).

My end goal, I think, is to replace the certificates in the flash (that are almost certainly the AWS IOT Core CA certs) with custom certs, and MITM the traffic to get the best of both worlds (on-prem data retention, with cloud connectivity for control), but I'm not there yet (the certs are in some mutant format I haven't put much time into deciphering).

Repurposing this issue for the discussion that it started. Was originally a question about connecting, and turned into a discussion about deciding the sensor data.

In the blog post, you mentioned that one of your USB-Serial adaptors wasn't working when you tried to connect to the ESP32. I'm wondering if I'm hitting the same issue; I only have one serial adaptor to test with at the moment though.

I'm using the FT232RL FTDI Mini USB to TTL Serial Converter, and getting nothing while trying to connect:

> esptool.py --port /dev/cu.usbserial-A50285BI read_flash 0 0x400000 flash_contents.bin
esptool.py v2.8
Serial port /dev/cu.usbserial-A50285BI
Connecting........_____....._____....._____....._____....._____....._____....._____

A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header

Process I'm taking to enter flashing mode:

1. Power with 3.3v
2. Pull IO0 pin to GND
3. Pull EN pin to GND, and release
4. Release IO0 pin

But that's not working; my only thought is that maybe there is something else connected with TX/RX that is interfering? And a different serial converter could sort through the noise?

Any guidance would be appreciated!

Edit by @flaviut for visibility:

There is now a ESPHome component. You can follow development at

• https://github.com/krconv/esphome/tree/add-emporia-vue-maelstrom96
• https://github.com/Maelstrom96/esphome/tree/add-emporia-vue2-staging
• esphome/esphome#2871
• esphome/esphome-docs#1702