Flaviu Tamas

WOW! This is incredible! I'm curious about how you went about doing this, I did spend a while looking at things in a hex editor, but didn't really get anywhere.

It took me a bit to understand the spreadsheet, but now that I do, I've written up a C declaration for that data: ``` // all data is little-endian struct...

@Maelstrom96 I believe it's 100kHz. I uploaded a dump from sigrok pulseview to https://github.com/flaviut/emporia-vue2-reversing/blob/master/i2c%20dump.bin, and unless the time base is off in that, it shows 100kHz.  That hopefully the...

`cal_data` is a false lead--the [calibration data is internal to the ESP32 for their wifi hardware](https://github.com/espressif/esp-idf/blob/58283e385a7cbd04b8f628af15b5acf633aac2f3/components/esp_phy/src/phy_init.c#L452-L455). The real calibration constants are `cReal` and `cApparent`. However, the values here are surprising....

@Maelstrom96 You're right--increasing the number there won't work unless we adjust the function signatures too. We already have https://github.com/espressif/arduino-esp32/blob/master/libraries/Wire/src/Wire.h#L98, and it's a real shame that that function is written in...

So I did some digging, and here's how things work: The NVS calibration on the Emporia Vue 2 that I got isn't used. I'm not sure why the `cReal` and...

TLDR because my message above was basically a dump of my thoughts: > I wonder if the calibration is really changing that much per CT Calibration is not different per...

> The thing is that I doubt that the "current" number is actually instantaneous current For some reason, I thought it was spot-on. It isn't quite, looking at a recent...

I completely ignore the current. I used this code to ingest the data into InfluxDB: https://github.com/flaviut/emporia-vue2-reversing/blob/master/parse_mqtt_dbg.py#L196-L242 And this query to process it: ``` import "math" from(bucket: "home_automation") |> range(start: v.timeRangeStart,...

> Something else that is intriguing is that the debug messages always seems to start by 0x03, and @krconv documented it as the message "version", but I'm seeing it with...