Open JGrantman opened 11 months ago
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.
It does not appear to have worked... same issue.
Compiling .pioenvs/kplug-front-room/src/esphome/components/select/select_call.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->dnsserver->start(53, "*", (uint32_t) ip);
| ^~~~~
Compiling .pioenvs/kplug-front-room/src/esphome/components/select/select_traits.cpp.o
*** [.pioenvs/kplug-front-room/src/esphome/components/captive_portal/captive_portal.cpp.o] Error 1
========================= [FAILED] Took 21.01 seconds =========================
FYI -- Nothing was in esphome folder before I deleted it other than hidden file ".gitignore" which reappeared once I tried to update plugs.
ESPHome comment suggests Kauf update needed.
If compile is failing, nothing about the plugs has any bearing on the issue. It is only an issue with the dashboard and what code the dashboard is pulling in. If you are still having errors, they should resolve after 24 hours since we released an update that fixed this. The only way to get ESPHome to see the update before waiting 24 hours is to delete the packages folder. If you can't find it I'd just wait 24 hours and it should work.
Sorry I did not reply sooner. I was able to update all 4 plugs 4-5 days ago.
Thanks,
John Grantman
Email: @.***
On Thu, Oct 19, 2023 at 1:16 PM Brian Kaufman @.***> wrote:
If compile is failing, nothing about the plugs has any bearing on the issue. It is only an issue with the dashboard and what code the dashboard is pulling in. If you are still having errors, they should resolve after 24 hours since we released an update that fixed this. The only way to get ESPHome to see the update before waiting 24 hours is to delete the packages folder. If you can't find it I'd just wait 24 hours and it should work.
— Reply to this email directly, view it on GitHub https://github.com/KaufHA/PLF10/issues/25#issuecomment-1771489590, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4KLSSOGGTHO7QDJQIF62LYAFU7RAVCNFSM6AAAAAA6F7S2U6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRGQ4DSNJZGA . You are receiving this because you authored the thread.Message ID: @.***>
I waited and the update worked, now it's not working on the 2023.10.6 update.
Are you still having issues? Need you to post error from logs.
I figured out my issue, sorry to cause any churn. I factory reset the plug added it in and everything is working.
Home Assistant showing 2023.10.0 update for all 4 of my Kauf Plugs. Normal update via UI fails. Restarted firmware on all devices, restarted Home Assistant multiple times. All updates fail at exact same point (see log detail below):
Compiling .pioenvs/kplug-office-1/src/esphome/components/kauf_hlw8012/kauf_hlw8012.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->dnsserver->start(53, "*", (uint32_t) ip); | ^
~~~~ *** [.pioenvs/kplug-office-1/src/esphome/components/captive_portal/captive_portal.cpp.o] Error 1 ========================= [FAILED] Took 10.53 seconds =========================I also attempted to enable (add captive_portal) to yaml file and restart firmware, restart Home Assistant and manually update 1 plug. No change - same error.
All 4 plugs have updated without issue for a year or more. Looking at GitHub looks package file (referenced in yaml config) was changed an hour ago. Unable to pinpoint change that may contribute so the updated file is just a variable to rule out and may have nothing to do with the issue.