-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] ESPHoMaTriXv2 not compatible with ESPHome 2024.10.0 #248
Comments
Confirm |
I too have multiple challenges with 2024.10.0 and my Ulanzis. See:
(The "120m" caused an error. I changed it to 120min and it installed, don't know if that is correct, though). But I have additional issues with the integration. It keeps finding my Ulanzis, eventhough they are already configured. And one really annoying one: My Ulanzis randomly switch identities! |
@clfberlin I attempted to work around the issue by updating to version 2024.3.0 (EspHome 2024.10.0), but unfortunately, it did not resolve the problem. I had to flash back to version 2023.9.1 (EspHome 2024.9.2) and rejoin the Ulanzi device to Home Assistant. By doing that it also changed the swich entity name for me. BTW the refresh value is in seconds: |
Thanks! I have three Ulanzis in use. Let's call them Ulanzi01, Ulanzi02 and Ulanzi03.
All three Ulanzis can be reached via browser. And they react ok there. When I push the left button on Ulanzi02, the state on the page changes accordingly for Ulanzi02. But when I try to add an Ulanzi that was discovered as an integration, I get the following warnings:
|
Oh, and another one: |
Hi, can confirm the same Problem here, used also a Ulanzi Device.
tried ref: main, 2024.3.0, 2024.4.1 and 2024.5.1 on each of them i got the error:
He compiles, when i remove the Line "show_date: False", but after the reboot i get a black screen and he reboot each few minutes and in Home Assistant i get always a new device.
|
@clfberlin This sounds to me like it could be an mDNS issue or an issue with the ESPHome / Home Assistant discovery process. It's certainly not directly an eHMTX problem. If this error is due to mDNS, it's going to have this kind of error even if your YAML is barebones. Why not try a more thorough "cleaning-out" by 1) unplugging ALL clocks, 2) deleting ALL eHMTXv2 clocks from the ESPHome integration (and any entities leftover - double check, not just in the ESPHome integration), 3) reboot your router by unplugging it for a full minute (if it's an mDNS issue this will help), 4) flash one manually via USB (if the integration shows up in HA, nevermind it until flashing is done), 5) when it comes back online, add that one to HA properly... repeat steps 4 and 5 until finished. I did have a similar problem with mine because I decided to switch names of my clocks and there was some leftover integrations and entities in HA... until I did the above cleaning. Also, you really should open your own issue instead of hijacking another... As for the original issue, that sounds very concerning. Got me a bit worried to upgrade my ESPHome container. Have y'all tested this out with other devices...? Does it just affect the EHMTXv2s? |
I've got the same problem, but no idea yet where it comes from. I have to check the esphome changelog for hints |
@trip5 - Thanks. I already removed the Ulanzis from integration and from ESPHome and reinstalled via USB. That didn't do the job. But what I didn't do was sweep through the system to delete all entities and such. Should be worth a try. And yes, I also considered this to be an ESPHome problem (and it might be). But I do have other devices in there and unlike the Ulanzis, they all have proper MAC-addresses. To me this indicates a problem that ESPHome 2024.10.0 might specifically cause for ESPHoMaTriXv2 (or the Ulanzis in this case). |
possible troublemakers from the esphome change-log: [wifi] Use custom MAC address if programmed esphome#7498 by @kbx81 [wifi] Fix error message when no custom MAC is set esphome#7515 by @kbx81 [wifi] Replace USE_ESP32_IGNORE_EFUSE_MAC_CRC with IDF’s CONFIG_ESP_MAC_IGNORE_MAC_CRC_ERROR esphome#7502 by @kbx81 Perhaps also the changes to the idf |
@clfberlin To resolve the issue, you need the ESPHome 2024.9.2 backup and should downgrade the ESPHome version from 2024.10.0 to 2024.9.2.
|
Downgrade is no option, i think we should watch this: esphome/issues#6333 |
@idodov Thanks for the input. You are talking about ESPHome downgrade only, right? Because just today I had a major cleanup session in my system, getting rid of many, many obsolete entities and old configuration stuff. ZHA alone involves 100 devices in my household. A full restore of the entire system would be a setback of many clean-up hours. I'd rather sit out the situation and take the Ulanzis out of the game for a while until a proper solution is at hand. |
Bug report
Home Assistant Entities Unavailable After ESPHome 2024.10.0 Installation
After updating to the new ESPHome 2024.10 version, the Ulanzi device disappeared from Home Assistant. Only a rolling back to version 2024.9.2 resolved the issue.
While the device remains accessible via the local control URL after the 2024.10.0 installation, its services and entities are unavailable in Home Assistant.
Additional information
The text was updated successfully, but these errors were encountered: