-
Notifications
You must be signed in to change notification settings - Fork 111
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
Make sensor settings editable (OptionHandler) #102
Comments
The old way of setting it up using yaml is still supported. But you can’t mix yaml and config flow. |
+1 for adding option handler to configure the integration in UI. Just showing the configured values would be a good start |
I have a weird issue. I have not set VAT when installing the plugin, and later on I have configured in the yaml with VAT. How do I sort this mess out? |
@Hellowlol are there any showstoppers for implementing Options support? I would love to help out if I can |
from looking at the code Probably need a major rewrite since changing these tough options would generate a new entity. It would be nice if softer things like lowprice_cutoff and VAT was editable through Options and thus not included in entity id. Any thoughts on this @Hellowlol? |
Hmm. The only thing that needs to be set initially is currency. The rest should be easy to change. We do need another logic for creating ids. your welcome to send a pr if you want |
The huge problem is actually the additional costs In Denmark the tarifs have 4 steps per day and the actual amount changes each month. you have to adjust the additionals almost monthly. Below is my current additional cost I have had to experiement and tweaking the numbers to match the app from the supplier. I had to restart Home Assistant at least 20 times just yesterday because the only way you can edit this is in yaml and the only way to reload yaml based integration is a restart. and it is not possible to edit this in a UI added sensor. In fact the UI sensor is in my view useless unless all you want is the raw Nordpool price. We really need to be able to edit this in the UI. Both at creation and changing it.
|
It would be very nice to change the configuration via the UI. In order to update the additional costs annually. |
Many integrations offer a reconfigure option to revisit the options |
Also voting for a reconfiguration option in UI. Need to change cost template |
Yes, same here, tax is changed |
+1 |
What is the workflow now to change sensor settings (trying to switch from EUR -> cents) when it has been configured through UI? PS. It would be helpful to note on the setup instructions that settings set via UI can not be changed afterwards! I regret using the UI :D |
Create a new sensor in yaml so you have control. And remove the old. The integration can work with mix of yaml and UI sensors. The yaml you can change later. The UI sensors you have to delete and create a new. |
Home assistant now support to change configuration without implementing options flow. Pretty straightforward implementation, I might just give it a go with a PR https://developers.home-assistant.io/docs/config_entries_config_flow_handler#reconfigure |
#365 is a showstopper for implementing reconfiguration flow. Reconfig flow is a |
It would be nice if it was possible to edit the sensor setup data.
Right now you can only setup the sensor data when creating it, and if you want to change some setting, you need to delete the sensor and make it again, with the new data.
I would suggest, either putting the settings in a "text file" that can be edited or make the sensor data editable from the GUI.
The text was updated successfully, but these errors were encountered: