-
-
Notifications
You must be signed in to change notification settings - Fork 294
custom_components.json for custom_updater on Home Assistant #108
base: master
Are you sure you want to change the base?
Conversation
Just need to adjust the "version".
@tiagofreire-pt thanks for support but i've already mentioned a few times so far in the community forum and here that I'm not willing to support the autoupdate of this plugin. I tend to believe that a handful of people started using it and might have the devices in various configurations. because I don't have test devices most of the changes I do are sort of theoretical and I hope for the best output but I cannot risk it to push bugs that could break automations. it's best for people to stick to what it works for them right now and if they want to update they at least they will have a quick starting point to debug the problem. i'll leave this PR open for a moment when maybe I'll feel confident enough about the code's quality state. |
Hi @peterbuga. I understand your perspective. Regarding the maintenance of this integration on custom_updater, I believe may just be the version number inside the json, non considering possible new file structures imposed by HA. Speaking on the code confidence, from my experience, the final user always have the decision on his hands to update or not to, neither auto updating is an issue without his explicit consent. For this matter, I could maintain that json file myself, as long as my knowledge can achieve, collaborating with you on this project. |
I agree with @peterbuga but it does seem that other HA components don't care much about breaking changes. |
HA Version 100b0 broke this component; please re-consider adding HACS support -- so that there is a choice in either adding auto-upgrading functionality by using HACS or installing a particular version directly from repo and manually upgrading |
So for the time being, we won't be able to upgrade to the 1.0 release? What broke? |
Just need to adjust the "version".