Can't config bodymiscale
bratmat opened this issue · comments
I can't set a configuration of bodymiscale - I get this message after trying to add this addon {"message":"Invalid handler specified"}
How to clean old settings of bodymiscale ? I tried to remove directory and reinstaling it from hacs but no success at all. How to definitly remove this addon with it's settings from HA ?
@bratmat You must have a bodymiscale entity... Look in devices and services -> entity
I already errased this entity :-(
delete via hacs then restart ha and then reinstall in 3.0.9
I've done it and no success {"message":"Invalid handler specified"} after trying to config this addon :-(
Error occurred loading flow for integration bodymiscale: cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)
ah that's one of the things I touched in the last version. Are you using the latest version of HA 2023.10? otherwise you can switch to 3.0.8
Home assistant core 2023.8.2
Supervisor 2023.10.0
interesting that must come from there. You can select an earlier version in hacs. 3.0.8 should work. I will update to specify that version 2023.10 is mandatory.
should update core ? Tried 3.05 - the same problem
That’s curious. if you have the possibility to update tried
I will try it tommorow :-) . Ok I unistalled bodymiscale from HACS , reset, updated HA to 2023.10 and installed bodymiscale 3.09 and now the configuration tab appear again :-)
@bratmat
Have you solved your problem?
I'm having the same problem after upgrading HACS & Bodymiscale to the latest version.
Home Assistant 2023.8.4
Ok I found out what's causing the issue in my case:
the class DeviceInfo has been moved from the core/homeassistant/helpers/entity.py file to core/homeassistant/helpers/device_registry.py, during the trasition from 2023.8 to the 2023.9 version of HA.
bodymiscale made the change in this commit.
Then:
- bodymiscale@v3.0.8 works with HA <= 2023.8
- bodymiscale@v3.0.9 works with HA > 2023.8
Upgrading HA to 2023.9 solved the issue 🙂
This is what we were thinking about during our last discussions. I will put a lock on the next version. I leave it open until the update is done.
@bratmat Have you solved your problem?
Yep, updated core and everything works correctly
Update available with the minimum version required to avoid this error.