Do a backup of your HA first. Its probably not needed but a backup is never a bad idea ;)
The cleanest way will be to delete the surepetcarebeta integration completely and handle sureha completely independent. It will create the same entity/unique ids as before so your automations and graphs should not be affected.
# logging
logger:
default: info
logs:
surepy: debug
custom_components.sureha: debug
custom_components.sureha.binary_sensor: debug
custom_components.sureha.sensor: debug
Sorry for the bad naming and resulting confusion and chaos ๐ To "fix" this, I renamed surepetcarebeta to sureha.
Name | Repo | Type | Description | Need Help? |
---|---|---|---|---|
surepy ๐พ | github.com/benleb/surepy | Python Library | Library to interact with the API of Sure Petcare. Also provides Classes for the various Sure Petcare Devicess. Use this if you write an own python tool/app and want to interact with the Sure Petcare API | Issues |
surepetcare | github.com/home-assistant/core | Home Assistant Integration | Official Home Assistant Integration for the Sure Petcare Devices like Doors, Flaps, Feeders, ... | Issues, HA Forum |
sureha |
github.com/benleb/sureha | Home Assistant Integration | Home Assistant Integration developed in my own repo without reviews from the HA Team. This can be installed via HACS and is something like a preview integration for advanced users. Usually this provides more (experimental) features and faster fixes but lacks the code quality (reviews) and such from HA | Issues |
pethublocal | github.com/plambrechtsen/pethublocal | Home Assistant Integration | Home Assistant Integration developed by @plambrechtsen which works completely independent from Sure Petcare. Check outs his repo for more information! | Issues, HA Forum |