-
Notifications
You must be signed in to change notification settings - Fork 8
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
Service "clean_config" not documented #34
Comments
I added documentation with 0.5.5. (in the service description) It should do what you think: the duofern python module keeps a list of devices that are paired. In normal operation, the list should rebuild itself - whenever a message is received from a device that was previously paired it should appear in the list.
It's not very well tested because it's not a common situation. I ran it, restarted homeassistant, and my devices became available again after a few seconds. |
OK, that warning is helpful. Indeed I gave all my covers (entities and now also devices) custom names... I'm not happy having to rename all of them again. But as a last option if 0.5.5 does not work around the Update: read it twice. I was talking about the entity registry, the warning aims at I tend to close this issue for the initial documentation cause, but still not confident enough using that service... -.- |
Update: ran the service. The only thing it changed (prior to restarting HA) was: it wiped the "system_code" section at the EOF out of it, the curious long "devices" array/list is unchanged. Update after HA restart (before that I put the system_code section back in, just to be safe): |
See #36 for following up on the ghost devices issue. This issue is "fixed" as the docs have been updated regarding the |
I am wondering what the service
clean_config
actually does. It callsstick.clean_config
but no idea what that function actually does.Let's just put it in https://github.com/gluap/pyduofern-hacs#usage as the other services are too.
I started to see some "ghost covers/devices" after using
service: duofern.sync_devices
at 2023-03-24 (and corresponding new entities and devices as updated to 0.5.3 today) and was wondering if that service could remove them.The text was updated successfully, but these errors were encountered: