esphome 2024.4.0 breaks things AGAIN

[baudneo]

The devs over at esphome seem to have a nack for breaking installations constantly and then blaming everything and everyone else. They close issues in their issue tracker and say to go to the discord to discuss. When you go to the discord to discuss, they tell you to go on a wild goose chase and prove to them that its an esphome issue rather than the code in the custom class.

I dont know how much more prrof someone needs that esphome is the issue. This cusotm sensor class code and its YAML config have been working fine for over a year. Every once in awhile upgrading esphome versions causes issues.

Everything was working fine, I upgrade to 2024.4.0 and now I have no sensors for watts, kwh_net or kwh_consumed. When I open up a wireless logging session with logs: Vue: DEBUG set, I get no logs whatsoever from the Vue TAG:

[14:41:24][C][logger:166]: Logger:
[14:41:24][C][logger:167]:   Level: DEBUG
[14:41:24][C][logger:169]:   Log Baud Rate: 115200
[14:41:24][C][logger:170]:   Hardware UART: UART0
[14:41:24][C][logger:174]:   Level for 'Vue': DEBUG
etc, etc.
[14:41:26][D][sensor:094]: 'Wifi signal': Sending state -53.00000 dBm with 0 decimals of accuracy
[14:41:33][D][internal_temperature:067]: Ignoring invalid temperature (success=0, value=53.3)
[14:41:36][D][sensor:094]: 'Wifi signal': Sending state -53.00000 dBm with 0 decimals of accuracy
[14:41:38][D][sensor:094]: 'Uptime': Sending state 4120.39795 s with 0 decimals of accuracy
[14:41:46][D][sensor:094]: 'Wifi signal': Sending state -52.00000 dBm with 0 decimals of accuracy
[14:41:56][D][sensor:094]: 'Wifi signal': Sending state -53.00000 dBm with 0 decimals of accuracy
[14:42:06][D][sensor:094]: 'Wifi signal': Sending state -53.00000 dBm with 0 decimals of accuracy
[14:42:16][D][sensor:094]: 'Wifi signal': Sending state -52.00000 dBm with 0 decimals of accuracy

The only logs I am seeing are for wifi signal, uptime and temperature.

How can I check if the Vue custom class is being initialized? Or get it to throw an error or something so I can prove to them that they have once again nuked my setup?

Sorry for the tone of this post, I am getting extremely fed up with the experiences I am having with esphomes 'support'. Who the hell releases deprecations and or breaking changes and doesnt thrown an error on deprecated or broken code?

[baudneo]

I have confirmed downgrading esphome to 2024.3.2 fixes things, so yes, it is their fault.

To downgrade, I went to the HASS settings > backups and found the esphome addon backup (I always make sure the backup before upgrade option is enabled for cases like this). After restoring the esphome addon to 2024.3.2, you need to recompile the broken devices YAML config and upload it to the device: go to esphome addon > click on Edit for the broken device > click Install.

[baudneo]

esphome team says to rewrite this custom component into one of their add-on modules. I may try and take the time to do that when i have some spare time. If I do I will put in a PR.

At least that way esphome will 'support' us when there are errors. ATM, they just blame it on being an old unsupported add-on and refuse to help at all.

[baudneo]

Fixed using the new maintainers external component code: https://github.com/nekorevend/esphome-emporia-vue-utility