Firmware Upgrade: ESPHome 2024.6.0

mprowe

What do I need to do with this? How do I upgrade? Is it necessary? Can I replace the code with a local copy so I don’t have this problem next time around?
Regards, Martin

jane_t

Looking at the default github load for the plug
esphome-localbytes-plug/localbytes-plug-pm.yaml
It looks like the minimal code it uses has not been updated yet. So it is probably simplest to wait for a while and check when the “powers that be” have added the extra code to the script. If you are in a hurry for some reason you can make a local copy. Personally the plugs are working so I will leave them until it is fixed on Github.

MichaelMKKelly

Its a very small change that’s needed. I have just opened a pull request with a fix. but if you want to use my fork in the meantime then feel free although I strongly recommend switching back to the main repo as soon as a fix is deployed.

I have myself just commented out the main one and will probably be returning to it in the future but this is what my file looks like currently:

packages: #localbytes.plug-pm: github://LocalBytes/esphome-localbytes-plug/localbytes-plug-pm.yaml@main remote_package: url: https://github.com/MichaelMKKelly/localbytes-plug-pm ref: main file: localbytes-plug-pm.yaml

mprowe

Thank you both for your advice and suggestions. Very helpful.
For others following this thread, may I add that the code Michael has provides needs a bit of jiggling!
This is my version (with added indents) - gosh… I hate this yaml coding! But I guess it comes with the benifits of ESPHome?

packages: #no space
#localbytes.plug-pm: github://LocalBytes/esphome-localbytes-plug/localbytes-plug-pm.yaml@main
  remote_package: #2 spaces
    url: https://github.com/MichaelMKKelly/localbytes-plug-pm #4 spaces
    ref: main
    file: localbytes-plug-pm.yaml

Just as a postscript: I am surprised that the Localbytes techies are not watching their products and and updating their code as soon as the need arises?

Regards, Martin

jane_t

I suspect the Majority of users are not using the bleeding edge of ESPHome. For plugs and lights there is little need to keep them right up to date. Personally I don’t bother keeping plugs or lights up to date unless there is something important which I need. With 20 plus ESPHome devices updating them all every month is too much hassle.

MichaelMKKelly

yeah when I pasted it the formatting disappeared but figured anyone that is doing this can probably fix the indentation and if they cant then they shouldn’t be doing it.

please do remember to switch back the original repo as soon as updates are pushed, I don’t want to be responsible for people using an outdated version further down the line.

I am building more and more esphome devices and at some point ill not bother with updating them all but not quite there yet 🙂. I am also in the learning process a bit so am happy to mess with things a bit

SaaX

“building more and more esphome devices” made me curious 😃 I’ve just started building my first device, parts are still in shipping. I want to build a battery plus solar powered temperature & humidity sensor for our greenhouse and I’m pretty sure that I don’t know what I’m doing 🤣

MichaelMKKelly

“building up” is what I meant to type to be fair but I am indeed building some custom stuff.
I wrote up my first totally custom build recently here - https://github.com/MichaelMKKelly/MK-SmartBed
some more stuff in the pipeline.

SaaX

Just had a look - jaysus, you’re lightyears ahead of me! My little sensor project is like total beginner stuff - just hoping it’ll work as planned…

AAllport

Plug 2024.06 is on my todo list after LocalDeck is shipped, and we’ve restocked a few other things (we’re low on a few sensors, etc.)
IIRC, the only breaking change is the ota section.

In theory, we could update it now, but I don’t have any spare plugs to hand (I am spending time with family during the LocalDeck build) to test!

MichaelMKKelly

AAllport yes its just a small change and my fork (mentioned above) of the jamesswift repo has been working fine with the 1 line change. If you wanted to create a canary branch on the main repo with the change in then I am happy to give it a test for you. I am setting up another plug and testing things this afternoon anyway.

AAllport

I can see a PR has been filed.
I’m swinging by the office (my flat) tomorrow, so I should be able to give it a test.

I would rather have a final go/no-go from someone internal before we hit merge.
In the meantime, I believe you can do something like this:

packages:
  localbytes.plug-pm: github://LocalBytes/esphome-localbytes-plug/localbytes-plug-pm.yaml@pr/2

But don’t quote me on that.

Worse case, we’ll merge it on Friday even if we haven’t done an internal final check, as I’m fairly sure it’s correct!

AAllport

I forgot we had GHA setup 🤦
It looks like the only error was due to poor scripting on my end It was approved and merged.

We now support 2024.06 everyone!