changing parameters of modi does not store

[pvklink]

Alarmo Version

1.9.12

HA Version

20231017.0.dev - latest

Bug description

when i change the modi paramers in and out delays, the changed values dont store!
I use the latest docker on a rpi 4b with the latest os

All other applications works fine on this hass docker config
This is the only part that dont save.
Does it auto save, or do i get a save button, because i dont see one..

Steps to reproduce

when i change all values for home, away night, the dissaper after the latest is changed and checking the first

Relevant log output

No response

[ghost]

Can confirm. Same with my Alarmo installation.

[samtate]

Happens for me too. Is this from the latest update

[nielsfaber]

Could anyone check the HA log if any error is displayed here when making a change?
Changes should automatically be saved.
Is there any difference between changing a delay and enabling/disabling a mode?

[samtate]

Hi @nielsfaber I can enable/disable alarm modes and they will stick but I cannot change the entry/exit time or trigger time, as it will just revert to the previous value on refresh.

I do not see any errors in the browser console or in the home assistant logs. I looked on the /config/logs page under "Home Assistant Core", is that right?

[samtate]

I think I must have been able to change them in the past as my away mode was using non-default values.

I reinstalled the integration, having deleted it from the device list, and the issue still persists. Happens on mobile and desktop

[ghost]

No error messages in the HA logs when changing the values.
Also only 3 messages in the system debug logs containing "Alarmo" - all error unrelated.

2023-11-02 18:11:42.081 INFO (MainThread) [homeassistant.setup] Setting up alarmo
2023-11-02 18:11:42.082 INFO (MainThread) [homeassistant.setup] Setup of domain alarmo took 0.0 seconds
2023-11-02 18:11:42.125 INFO (MainThread) [homeassistant.components.alarm_control_panel] Setting up alarm_control_panel.alarmo

[aurelmarius]

Same problem here. Just installed alarmo and can't set none of the delay settings.
I manually edited .storage/alarmo.storage and set the values:

    "area_id": "1698947412",
    "name": "Hol",
    "modes": {
      "armed_away": {
        "enabled": true,
        "exit_time": 60,
        "entry_time": 60,
        "trigger_time": 600

[nielsfaber]

I can confirm the issue is caused by the HA 2023.11 update (I was on 2023.10 until today and could not reproduce this).
The issue is related to this change: home-assistant/frontend#18168.
I will have to make some changes to Alarmo to restore functionality.

[nielsfaber]

I made a new release which should fix this issue.
@pvklink Could you please update and confirm the issue is solved for you now?

[Nicko33127]

Amazing work! I had the same issue, just tested it and it works now. Thank you!

[aurelmarius]

I can confirm, it is fixed now. Thanks a lot.

[lanieuwe]

No I installed te laterst version Firmware: 1.9.13 from HACS.
The problem is not fixed. I still cannot change the delay. The Alarmo site bar on the left hand site is v1.9.12 but the alarmo in the integration says firmware 1.9.13. That is strange....

[pvklink]

it works!thanks nielsVerzonden vanaf mijn Galaxy -------- Oorspronkelijk bericht --------Van: Niels Faber ***@***.***> Datum: 04-11-2023 08:10 (GMT+01:00) Aan: nielsfaber/alarmo ***@***.***> Cc: peter van klink ***@***.***>, Mention ***@***.***> Onderwerp: Re: [nielsfaber/alarmo] changing parameters of modi does not store (Issue #823) I made a new release which should fix this issue. @pvklink Could you please update and confirm the issue is solved for you now? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[lanieuwe]

Thank you Niels!
It works fine now!

[jperns]

I updated to the latest version using HACS and restarted HASS but it is still not saving for me?

[jperns]

I updated to the latest version using HACS and restarted HASS but it is still not saving for me?

Ok, so while I had updated Alarmo to 1.9.13 in HACS, the version shown in the Alarmo UI was still 1.9.12. I switched to a different browser/no cache and it works. So yeah, clearing cache of your browser should sort it.