esphome::sensor::Sensor::raw_state is deprecated

Bobbinz

Hello,

When using github://LocalBytes/esphome-localbytes-plug/localbytes-plug-pm.yaml@main for the localbytes plugs you now get a warning when compiling.

esphome::sensor::Sensor::raw_state' is deprecated: Use get_raw_state() instead of .raw_state. Will be removed in 2026.10.0

Full details are at https://github.com/LocalBytes/esphome-localbytes-plug/issues/20

There are also a few PRs on that project that could do with merging if somebody has the time to review them?

MichaelMKKelly

Bobbinz When using github://LocalBytes/esphome-localbytes-plug/localbytes-plug-pm.yaml@main for the localbytes plugs you now get a warning when compiling.

esphome::sensor::Sensor::raw_state’ is deprecated: Use get_raw_state() instead of .raw_state. Will be removed in 2026.10.0

Full details are at https://github.com/LocalBytes/esphome-localbytes-plug/issues/20

I have investigated the change and it is just a small change required as there is no underlying functional change.

PR Submitted - https://github.com/LocalBytes/esphome-localbytes-plug/pull/21

Bobbinz Perhaps most notably

https://github.com/LocalBytes/esphome-localbytes-plug/pull/16

Needs merging before 2026.6 comes out.

I would agree that this is currently the most time sensitive (although still plenty of time) of the PR’s for the Plug..

Bobbinz

Perhaps most notably

https://github.com/LocalBytes/esphome-localbytes-plug/pull/16

Needs merging before 2026.6 comes out.

Bobbinz

There is a similar issue with the Localdeck only this time with std::string esphome::EntityBase::get_object_id()

https://github.com/LocalBytes/localdeck-config/issues/61

Bobbinz

@AAllport

AAllport

Morning All, thanks for bearing with me…

I’ve taken a quick look at those PR’s and the only immediate hesitation is IPv6, given that the previous issue was caused.
Especially as I feel the majority of internal domestic networks are either v4 or dual-stack (although yes, I appreciate vendors not supporting v6 can be frustrating at times).

I’ll put some time in to review them properly towards the end of this week/begining of next!

I’ll also take a look at our settings in our PM tool, as we didn’t seem to get notifications of the PRs when they came through.
Massive thanks to @MichaelMKKelly for the contributions, and for bearing with us!

MichaelMKKelly

@AAllport

AAllport Massive thanks to @MichaelMKKelly for the contributions

No Worries, Happy to help. I have been working on my own rewrite so makes sense to contribute some of the fixes and improvements where it makes sense.

AAllport I’ve taken a quick look at those PR’s and the only immediate hesitation is IPv6, given that the previous issue was caused.

I do not believe this is an issue any longer due to the massive optimizations in ESPHome since the original issue.
Using your notes to compare to from here: https://forum.mylocalbytes.com/d/186-reset-esp-smartplug/13
When the problem first occurred the the totals of .bin + bin.gz were:
without: 968340
with: 1025584

I have run a test build on ESPHome 2026.4.1 with all 6 of the current PR’s included. and compared without and without ipv6 and see totals of:
without: 698850
with: 755511

With the limit being 1023984

Even with some variation from version sizes and compression ratios you can see that we are very much comfortably within the size limit now.

Whilst this includes the extra optimizations in pr #18, It Is pretty amazing how much optimization has come from ESPHome. The team over there is pretty magic.

Hopefully can get these merged soon. 🙂

Bobbinz

Just updated to the new release of localbytes plug and installed with no issues 😃

AAllport

Thanks for letting us know @Bobbinz! (And thanks for bearing with me)

Bobbinz

No worries at all! I had not found the time to start digging myself yet through the code. Thanks for sorting it all out 🙂

There is a minor error that the preferences take too long to save when you boot the localbytes-plug but that is a nothing thing really. I see that kind of error on all sorts of other projects too!

To the best of my knowledge, based on the products I own, it’s just the localdeck with deprecation issues now.

AAllport

I believe you’re correct… Bulb is a community managed config at the moment.

Deck I need to do a few wider updates on the configurator (hence some of the changes you may have seen on the blog/docs site) looking to schedule that in for May!