Hi @rda2w,
I made some minor changes today (v3.4.2) at my beta branch, and it now works as expected on my end.
Regarding your specific issue with the hex name, it looks like you’re having specific connectivity issue… Do you have good wi-fi connectivity at home?
On my side, I’ve noticed the following facts:
(1) Cloud Connectivity between ST and ecobee is an issue.
This morning from 9h30 to 10h40 (EST) the ST connection was lost with ecobee.
Then, at around 10h40 (EST) the connection was re-established and MyEcobee device was able to recover and it proceeded then normally after.
(2) The stock ST device is even more vulnerable to cloud connectivity issue.
I was running the ST stock device in parallel to see if it is also affected by the ST-ecobee connectivity issue. And, I can confirm that it is also greatly affected.
However, contrary to My Ecobee device, the ST stock ecobee device is now stuck since 10h30 (EST) and does not respond at all. I cannot increase/decrease the setpoints or even refresh it.
The device is now longer responsive and I will have to kill it.
(3) It seems that having ecobee3’s remote sensors generates more exceptions
I’ve noticed that most of the ecobee3 users who expose their remote sensors to ST have more issues than other ecobee users.
The more ecobee3’s remote sensors, the more exceptions they get.
Recommendations
- If you have many ecobee thermostats or many ecobee3 remote sensors, create many instances of MyEcobeeInit and ecobee3RemoteSensorsInit and split your devices between them.
You can assign a new name to the smartapp at the last page.
- If ST support says that you should switch from my custom Ecobee device to the ST stock device, this is clearly wrong as the ST stock device is not able to recover from any ST-ecobee connectivity lost.
P.S. I’ve updated the known issues section of the ST community wiki with my recommendations
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Known_issues
Regards.