basbruss / adaptive-cover

An Adaptive Cover component for HomeAsisstant to control covers based on the sun's position
MIT License
71 stars 10 forks source link

Modify Automation Configuration doesn't save #106

Closed The-Moops closed 4 months ago

The-Moops commented 4 months ago

System Health details

System Information

version core-2024.4.3
installation_type Home Assistant Container
dev false
hassio false
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.5.0-25-generic
arch x86_64
timezone America/New_York
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1402 Downloaded Repositories | 11
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | April 15, 2024 at 8:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | us-east-1-6.ui.nabu.casa certificate_status | ready instance_id | 0319c6ee631e4b35a0514cd43d18ff3f can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Dashboards dashboards | 5 -- | -- resources | 3 views | 3 mode | storage
Recorder oldest_recorder_run | April 5, 2024 at 11:58 PM -- | -- current_recorder_run | April 15, 2024 at 10:43 AM estimated_db_size | 67.26 MiB database_engine | sqlite database_version | 3.44.2
Spotify api_endpoint_reachable | ok -- | --

Checklist

Describe the issue

Any changes to the Automation Configuration menu don't save, both when initially setting up the integration and when editing an existing one.

Reproduction steps

  1. In the Integration page click CONFIGURE for any entry
  2. Click Modify Automation Configuration
  3. Change any setting
  4. Submit
  5. Re-enter menu to see if changes persist ...

Diagnostics dump

No response

basbruss commented 4 months ago

Thanks, everything is saved in the backend, but not displayed after reopening the menu. This PR #94 already covered the fix