Compiliation fails after esphome 2023.10.0 update

Question

Compiliation fails after esphome 2023.10.0 update

Opened this issue 10 months ago · 7 comments

Compiling .pioenvs/kauf-rgbsw-648e5f/src/esphome/components/captive_portal/captive_portal.cpp.o
src/esphome/components/captive_portal/captive_portal.cpp: In member function 'void esphome::captive_portal::CaptivePortal::start()':
src/esphome/components/captive_portal/captive_portal.cpp:76:37: error: invalid cast from type 'esphome::network::IPAddress' to type 'uint32_t' {aka 'unsigned int'}
76 | this->dns_server_->start(53, "*", (uint32_t) ip);
| ^~~~~~~~~~~~~
*** [.pioenvs/kauf-rgbsw-648e5f/src/esphome/components/captive_portal/captive_portal.cpp.o] Error 1

Answer 1 · 2023-10-18T15:21:42.000Z

When I tried to do update to 2023.10 from HA, I receive a message at bottom " failed to call service update/install....."
Currently on 2023.9.3.

Answer 2 · 2023-10-18T20:09:05.000Z

Should be fixed now. Had to update the custom components for the latest ESPHome release. In order for you to see the fix you'll need to delete your .esphome/packages folder or wait 24 hours for ESPHome to check for an updated package again.

Answer 3 · 2023-10-18T20:54:00.000Z

I only have a *config/esphome/* with all my esphome-devices' yaml files in it. There is no *.esphome/packages* directory. Thanks

…

On Wed, Oct 18, 2023 at 2:09 PM Brian Kaufman ***@***.***> wrote: Should be fixed now. Had to update the custom components for the latest ESPHome release. In order for you to see the fix you'll need to delete your .esphome/packages folder or wait 24 hours for ESPHome to check for an updated package again. — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEN5KAAMFT7Q4XXUTNK5CSDYAAZOZAVCNFSM6AAAAAA6FWPPOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGI2DIMRVGA> . You are receiving this because you commented.Message ID: ***@***.***>

Answer 4 · 2023-10-18T21:00:47.000Z

.esphome is a hidden folder within config/esphome/. You probably need to show hidden files or something.

Answer 5 · 2023-10-18T21:10:42.000Z

Ignore that - I found the folder - I will rename it Thanks

…

On Wed, Oct 18, 2023 at 2:53 PM Albertus de Wet ***@***.***> wrote: I only have a *config/esphome/* with all my esphome-devices' yaml files in it. There is no *.esphome/packages* directory. Thanks On Wed, Oct 18, 2023 at 2:09 PM Brian Kaufman ***@***.***> wrote: > Should be fixed now. Had to update the custom components for the latest > ESPHome release. In order for you to see the fix you'll need to delete > your .esphome/packages folder or wait 24 hours for ESPHome to check for an > updated package again. > > — > Reply to this email directly, view it on GitHub > <#8 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEN5KAAMFT7Q4XXUTNK5CSDYAAZOZAVCNFSM6AAAAAA6FWPPOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGI2DIMRVGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

Answer 6 · 2023-10-19T12:19:23.000Z

One of the two devices got updated and one still gives the same error message.I noticed today that there is another update to Esphome 10.1. It has not seem to have hit the individual devices yet.

…

On Wed, Oct 18, 2023 at 3:10 PM Albertus de Wet ***@***.***> wrote: Ignore that - I found the folder - I will rename it Thanks On Wed, Oct 18, 2023 at 2:53 PM Albertus de Wet ***@***.***> wrote: > I only have a *config/esphome/* with all my esphome-devices' yaml files > in it. There is no *.esphome/packages* directory. > > Thanks > > On Wed, Oct 18, 2023 at 2:09 PM Brian Kaufman ***@***.***> > wrote: > >> Should be fixed now. Had to update the custom components for the latest >> ESPHome release. In order for you to see the fix you'll need to delete >> your .esphome/packages folder or wait 24 hours for ESPHome to check for an >> updated package again. >> >> — >> Reply to this email directly, view it on GitHub >> <#8 (comment)>, or >> unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AEN5KAAMFT7Q4XXUTNK5CSDYAAZOZAVCNFSM6AAAAAA6FWPPOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGI2DIMRVGA> >> . >> You are receiving this because you commented.Message ID: >> ***@***.***> >> >

Answer 7 · 2023-10-19T16:29:49.000Z

Update finally was installed on the other device too. Thanks

…

On Thu, Oct 19, 2023 at 6:18 AM Albertus de Wet ***@***.***> wrote: One of the two devices got updated and one still gives the same error message.I noticed today that there is another update to Esphome 10.1. It has not seem to have hit the individual devices yet. On Wed, Oct 18, 2023 at 3:10 PM Albertus de Wet ***@***.***> wrote: > Ignore that - I found the folder - I will rename it > Thanks > > > On Wed, Oct 18, 2023 at 2:53 PM Albertus de Wet ***@***.***> > wrote: > >> I only have a *config/esphome/* with all my esphome-devices' yaml files >> in it. There is no *.esphome/packages* directory. >> >> Thanks >> >> On Wed, Oct 18, 2023 at 2:09 PM Brian Kaufman ***@***.***> >> wrote: >> >>> Should be fixed now. Had to update the custom components for the >>> latest ESPHome release. In order for you to see the fix you'll need to >>> delete your .esphome/packages folder or wait 24 hours for ESPHome to check >>> for an updated package again. >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#8 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/AEN5KAAMFT7Q4XXUTNK5CSDYAAZOZAVCNFSM6AAAAAA6FWPPOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGI2DIMRVGA> >>> . >>> You are receiving this because you commented.Message ID: >>> ***@***.***> >>> >>