DNS name used by later firmware

[glyndon]

FWIW, I am observing traffic from a relatively new VeSync unit, and it is looking for 'server22.vesync.com' (as distinct from 'server2' as described in the readme file).
Perhaps they've added servers, or changed server name(s) since that text was written.

[iceman73]

Seems like something might have changed than just the server, as the unit I have pointing at server22 never gets registered with Voltlet

[glyndon]

My suspicion is that older/original firmware contacted server2, where newer firmware contacts server 22.
The firmware version in this unit is 1.95.

I'm seeing the version by tapping the serial lines on the ESP8266 (don't do this using mains power, or with the device in any way connected to the mains power, supply your own 3.3.v to the board if the case is open).

But the server22 observation is from a network packet trace. server22 is the name it asks DNS to resolve for it.

[trumpetrhapsody]

Can confirm that 2018+ units use server22.vesync.com. I'm getting the following error returned:

read error: json: cannot unmarshal number into Go value of type map[string]interface {}

I'm running this in a HomeAssistant add-on docker container, so I would have to try and spin up a dedicated instance to troubleshoot the json response. Any chance someone else has this sorted already?

[glyndon]

My solution to the Vesync device firmware issue was to pry open the case, solder on a header, flash ESPHome by RS232, remove the header, snap the case closed, and enjoy them as wonderfully-compact ESPHome devices from then on.
YMMV, but if you go this route, pry the case open very carefully. It takes longer, but you'll be glad you did.