Closed TNTLarsn closed 4 months ago
Any plans on when this will be released?
I created pre-release 0.7.3 please test and report here.
After restart, write automation do reload config is ok
After you make changes to the configuration of the plate you can apply them by either restarting Home Assistant or by reloading the integration from Lovelace user interface with option found in Configuration > Devices & Services > openHASP > (your plate >) 3dots menu > Reload. Note that this has to be done individually for each configured plate.
After you make changes to the configuration of the plate you can apply them by either restarting Home Assistant or by reloading the integration from Lovelace user interface with option found in Configuration > Devices & Services > openHASP > (your plate >) 3dots menu > Reload. Note that this has to be done individually for each configured plate.
You can achieve the same by with a service too:
service: homeassistant.reload_config_entry data: entry_id: 95f7d6fe3fa5f4e242797e9ae4a5dd1d
With the entry_id found in .storage/core.config_entries file from your main Home Assistant configuration directory (do NOT edit this file!).
@kydang789 I know that is what i did. before 0.7.3
@fvanroie It seems that 0.7.3 fixes the issue. Thanks
So far so good :) No need to reload integration anymore. Many thanks!
Thanks for the feedback, I release 0.7.3 of the custom component in the wild 🤞
After upgrading to HA 2024.6.0 all Display related entities where unavailable. I had to reload the configuration of every display by hand in order to get it to work again. Also logging errors (see further down) appeared.
Version of the custom_component
0.7.2
Configuration
shorten because of:
Describe the bug
A clear and concise description of what the bug is.
Debug log