-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Home Assistant] some topics fail discovery #29
Comments
Hi @fishbone-git, indeed it is the MQTT buffer size, please upgrade to 0.9.18 or newer which increases this (HA_VALUE_LEN) from 300 to 600 to resolve this issue. |
in progress |
The buffer problem appears solved, but there is a new problem. I'm using HA 2022.9.0b4. All topics appear in MQTT broker, and in th discovery topic. HA is having a problem with a number of them, and so they are no longer available entities in HA after upgrading to 0.9.18. Hard to check all topics, but the ones generating the error all seem to have state_class="". I do not believe this is allowed by HA. When I manually publish a discovery topic to remove state_class="", it immediately creates an entity in HA |
You're fast and fully correct! Sorry, I should have advised to jump to the newest version: 0fd7519 solves this too. |
I just spotted that too :). I guess let's close this and either I'll see if I can now get a working build or wait until next binaries are published. Thx! |
I'll make them available soon - was waiting for the climate and water heater integration to be finished and tested. |
Not as official release, but v0.9.20 images (for E_series) are here. |
The images have been replaced as the ATmega OTA upgrade didn't work properly due to a BSP issue on my side. The current Eseries images should be fine. |
Thanks. I'll try the images tonight and see if there is a difference. I did finally manage to get a build on arduinoIDE that seems stable |
Home Assistant logs attached below. I suspect te issue is an MQTT buffer problem as it seems to be the very long topic names that get cut off at the end, so the discovery topic fails to parse due to missing closing } at least
halogs.txt
The text was updated successfully, but these errors were encountered: