Could Tasmota support the Emporia Vue Gen 2? #12749

crlogic · 2021-07-25T14:43:07Z

crlogic
Jul 25, 2021

I have never used Tasmota before but know of it. Have played with ESP32's & micropython so flashing things isn't too scary.

I just got an Emporia Vue Gen 2 with two CT's for mains just to explore it.

Opening it up it has a WROVER-B, a single SAMD09D and two HC4051's. There are headers and labels so I don't think flashing it would be a challenge.

Sadly Emporia does not offer local MQTT and rate-limits their non-public API that HA taps into.

I would be willing to flash it if someone has a bin that might support energy monitoring. I realize I have no software development skills and that SAMD likely does magic..

[edit] WROVER not WROOM

sfromis · 2021-07-25T15:31:44Z

sfromis
Jul 25, 2021

With another MCU, the SAMD09D, it sounds like some work may be needed to explore how the device works, and possibly get it supported. A common setup with another MCU is that the ESP8266 is merely used as a "wifi modem" with the other processor running the show, and having serial communication. While this may mean that the rest of the hardware is "taken care of", it is likely an open question how that communication works.

1 reply

crlogic Jul 25, 2021
Author

That makes sense.

What would be the best way to go about exploring this?

digiblur · 2021-07-25T23:17:17Z

digiblur
Jul 25, 2021

SAMD09D

Time to do some serial sniffing if that is the interface it is using. Can you pin things out to see what is connected to what on each chip between the ESP and secondary MCU?

11 replies

crlogic Jul 26, 2021
Author

Did you just flashed tasmota.bin (esp8266) on a ESP32 ?

Oh you bet I did!

Never even realized there were different binaries.. ..trying tasmota32.bin now :))

digiblur Jul 26, 2021

Nice! Did you take a full backup of all of the chip?

crlogic Jul 26, 2021
Author

Nice! Did you take a full backup of all of the chip?

Full? errr, maybe..

I have a 4MB backup that I have flashed back and forth about a half dozen times before realizing this device has 4BM SPI RAM and 8MB SPI Flash..

..so it works to restore; crossing fingers that the last 4-8MB weren't needed!

crlogic Jul 27, 2021
Author

SAMD09D

Time to do some serial sniffing if that is the interface it is using. Can you pin things out to see what is connected to what on each chip between the ESP and secondary MCU?

After inspecting both top and bottom layers of the PCB aligned in pixel-layers, the SAMD appears to be directly underneath the ESP32 which makes throughholes a tough thing to track :/

crlogic Jul 27, 2021
Author

Found two plain text certificates and one plain text RSA private key in the backup :o

A few server addresses, ports and mqtt topics. Although watching the serial output of the stock firmware offers up more topics.

barbudor · 2021-07-26T18:59:27Z

barbudor
Jul 26, 2021

Beware that for ESP32, the flashing procedure is slightly more complex and requires more than just 1 binary. Read the doc please

1 reply

crlogic Jul 26, 2021
Author

I RTFM'd and its alive!!!!

[edit] seriously, thank you. I bumble my way through things the hard way some times..

crlogic · 2021-07-26T19:36:38Z

crlogic
Jul 26, 2021
Author

Now that Tasmota32 v9.5.0 is up and running on the WROVER and everything is installed back in the panel we can start poking!

Using the Berry console I see nothing on the I2C busses

wire2.scan()
[]
wire1.scan()
[]

Does that mean we want to assume the ESP32 and the SAMD are connected via SPI or UART? Honest question, I know so very little about these things. Need to learn more how to use it..

Direction welcome as I can't make heads or tails of https://tasmota.github.io/docs/Commands/#serial-bridge to poke for data..

0 replies

crlogic · 2021-07-26T23:20:04Z

crlogic
Jul 26, 2021
Author

If anyone can point me to an example/guide that explains better than the docs how to actually uart.reading() that would be great. As far as I can see, the official docs say what gpio does what and not how to pull a string from a serial/uart.

First day in Tasmota is very confusing..

4 replies

sfromis Jul 26, 2021

At least until now, you do not have direct serial features in Berry. To make basic use of serial bridge, after you configure pins, baud rate and SerialConfig, you can do a send to turn on reception, including selecting (via the format in the SerialSend) if you get data in hex or chars. Received data will appear in SerialReceived MQTT messages. Until you make the first send, Tasmota will not be receiving data.

crlogic Jul 27, 2021
Author

At least until now, you do not have direct serial features in Berry. To make basic use of serial bridge, after you configure pins, baud rate and SerialConfig, you can do a send to turn on reception, including selecting (via the format in the SerialSend) if you get data in hex or chars. Received data will appear in SerialReceived MQTT messages. Until you make the first send, Tasmota will not be receiving data.

Few questions about this;

configuring pins is using the GUI options? Eg. Configuration --> Configure Modules --> GPIO1 Serial TX
I am able to query/confirm Baudrate/SerialConfig via MQTT correctly. Not quite clear if the SerialSend value should be raw or some json format. Have successfully sent raw value and MQTT returned a {"SerialSend":"Done"} so I am assuming that works? Without any other data in return am I safe to assume it is not those pins and I have to try others?

crlogic Jul 27, 2021
Author

What might I expect to see returned when serial RX is achieved?

03:27:50.853 MQT: stat/tasmota_A#####/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"1824":"SerBr Rx"},"GPIO5":{"1792":"SerBr Tx"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"},"GPIO18":{"0":"None"},"GPIO19":{"0":"None"},"GPIO21":{"0":"None"},"GPIO22":{"0":"None"},"GPIO23":{"0":"None"},"GPIO25":{"0":"None"},"GPIO26":{"0":"None"},"GPIO27":{"0":"None"},"GPIO32":{"0":"None"},"GPIO33":{"0":"None"},"GPIO34":{"0":"None"},"GPIO35":{"0":"None"},"GPIO36":{"0":"None"},"GPIO39":{"0":"None"}}
03:32:03.351 MQT: stat/tasmota_A#####/RESULT = {"SSerialSend":"Done"}
03:32:03.543 MQT: tele/tasmota_A#####/RESULT = {"SSerialReceived":"1\n"}

So SSerialReceived seen but where is the data!?

barbudor Jul 27, 2021

Here in the message payload : a "1" and a "\n"

crlogic · 2021-07-27T12:06:20Z

crlogic
Jul 27, 2021
Author

It seemed odd since it was just repeating the SSerialSend integer.

…

On Tue, Jul 27, 2021, 6:28 AM Barbudor ***@***.***> wrote: Here in the message payload : a "1" and a "\n" — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12749 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASNI4Z54VUOA2BCZMLUEFLTZ2C43ANCNFSM5A6TKQZQ> .

1 reply

sfromis Jul 27, 2021

Getting same payload back may simply be the other MCU echoing anything it gets (very common with full duplex operation), and if it does not recognize what you sent, it has nothing further to say. It might also be your tx/rx pins being connected, with you thus effectively running a loopback test. Do note that baud rate and serial config will normally be important to get right.

What format you send depends entirely on the expectations of the other MCU.

crlogic · 2021-07-27T13:52:05Z

crlogic
Jul 27, 2021
Author

I suppose I did get myself into a guessing game.. ..thx!

…

On Tue, Jul 27, 2021 at 9:37 AM sfromis ***@***.***> wrote: Getting same payload back may simply be the other MCU echoing anything it gets (very common with full duplex operation), and if it does not recognize what you sent, it has nothing further to say. It might also be your tx/rx pins being connected, with you thus effectively running a loopback test. Do note that baud rate and serial config will normally be important to get right. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12749 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASNI4ZAHN3TPEKA5QOC5S3TZ2Y73ANCNFSM5A6TKQZQ> .

0 replies

chris153002 · 2022-01-06T15:50:24Z

chris153002
Jan 6, 2022

FYI If you are still working on this.

https://flaviutamas.com/2021/reversing-emporia-vue-2

He has figured out the I2C pins (Connenction to the SAMD MCU).

0 replies

crlogic · 2022-01-06T15:55:46Z

crlogic
Jan 6, 2022
Author

Wow there has been great progress. Will definitely go the ESPHome route.

…

On Thu, Jan 6, 2022 at 10:50 AM chris153002 ***@***.***> wrote: FYI If you are still working on this. https://flaviutamas.com/2021/reversing-emporia-vue-2 He has figured out the I2C pins (Connenction to the SAMD MCU). — Reply to this email directly, view it on GitHub <#12749 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASNI45LLXMMIDVB64HCSXDUUW24XANCNFSM5A6TKQZQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

1 reply

TommySharpNZ Dec 5, 2022

Did you get ESPHome running on your Emporia okay? I'm having quite a few issues with mine in that I find it quite unreliable and reboots often and loses daily counters...

TommySharpNZ · 2022-11-23T20:10:30Z

TommySharpNZ
Nov 23, 2022

I have ESPHome running on mine for a week now :-)
But to be honest I'd really love to have Tasmota on it instead.... Maybe this work can somehow help get Tasmota onto it?

0 replies

TommySharpNZ · 2023-01-29T08:51:18Z

TommySharpNZ Jan 29, 2023

I kindly ask that you don't spam our discussion. Your post is off-topic and is disrupting the flow of conversation. We value constructive dialogue and welcome diverse perspectives, but spamming is not productive or respectful of others' time. Please refrain from posting irrelevant content in the future.

hemangjoshi37a · 2023-01-29T09:34:40Z

hemangjoshi37a Jan 29, 2023

First of all I have provided solution to this topic which discusses the author that MQTT is not available in vue devices, which can be very much helpful to the people who are in this discussion.
And second of all who are you to decide what is spam and what is not, may be you are a spam who does not want me to spread awareness that about a great app that is available in the PlayStore.

Bro instead bashing anyone please do something productive in your life for God sake.

MichaelWoodc · 2024-09-11T21:08:20Z

MichaelWoodc
Sep 11, 2024

Guys I am on the emporia vue v3 but trying to do the same thing. I am curious how much headway you guya may have made on this. I am trying esphome and not having a seamless experience. I prefer tasmota

0 replies

Could Tasmota support the Emporia Vue Gen 2? #12749

Replies: 12 comments · 21 replies

crlogic Jul 25, 2021 Author

crlogic Jul 26, 2021 Author

crlogic Jul 26, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jul 26, 2021 Author

crlogic Jul 26, 2021 Author

crlogic Jul 26, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jul 27, 2021 Author

crlogic Jan 6, 2022 Author

This comment was marked as spam.

Replies: 12 comments 21 replies

crlogic Jul 25, 2021
Author

crlogic Jul 26, 2021
Author

crlogic Jul 26, 2021
Author

crlogic Jul 27, 2021
Author

crlogic Jul 27, 2021
Author

crlogic Jul 26, 2021
Author

crlogic
Jul 26, 2021
Author

crlogic
Jul 26, 2021
Author

crlogic Jul 27, 2021
Author

crlogic Jul 27, 2021
Author

crlogic
Jul 27, 2021
Author

crlogic
Jul 27, 2021
Author

crlogic
Jan 6, 2022
Author