Issues with parameters saving on zwave devices via GUI. | Home Assistant | Page 1

true hemlock Sep 16, 2025, 6:01 PM

#

I cannot seem to get the configuration parameter changes to stick. For example, I queue changes, both in the config or simply change it on the device info page, but they all just reset to the default.

This happens on this device as well as a temp sensor of another decent brand, leading me to believe I'm not doing something right ..

Any ideas are appreciated!

Device info
FGMS001
by Fibargroup
Connected via USB Controller
Firmware: 3.4
Z-Wave info
ID: 6
Ready: Yes
Highest security: None
Z-Wave Plus: Version 1

true hemlock Sep 16, 2025, 10:32 PM

#

I was able to get the motion sensor to work, but the aeotec temp sensor still will not take, it only seems to update every 6 plus hours, and if I 'queue' changes, it just changes back eventually 🙁

blissful canopy Sep 16, 2025, 11:14 PM

#

Did you wake it up?

#

"will be updated when the device wakes up"

true hemlock Sep 17, 2025, 12:13 AM

#

So, I'm waiting on that, but the last time it did not update when it 'woke up'

#

i ping it, and it can wake up, but immediately sleeps it seems. The command seems to just cycle back to the default time as it waits on the webpage

#

kind of an odd one, going to mess with it some more this week

#

blissful canopy Sep 17, 2025, 12:24 AM

#

ping? you can't really ping battery devices

#

a ping doesn't wake it up, you need to perform some procedure on the device, e.g. pressing the inclusion buttons. manual has instructions.

true hemlock Sep 17, 2025, 12:25 AM

#

clicking the 'ping button' in the config, or identify, seems to wake it up

blissful canopy Sep 17, 2025, 12:25 AM

#

that's not really possible. what are you calling "wake it up"?

true hemlock Sep 17, 2025, 12:26 AM

#

#

pushes this to the log book

#

#

so i assume its waking it up in some fashion

blissful canopy Sep 17, 2025, 12:26 AM

#

those aren't from the device though

#

Did the node status sensor actually go from asleep to awake during that time?

#

Yeah, I checked those logs are misleading. A button entity state always changes to the time the button was pressed. Has no relation to device activity.

#

https://aeotec.freshdesk.com/support/solutions/articles/6000227918 see section "Communication with a Sleeping device (Wakeup)."

true hemlock Sep 17, 2025, 12:30 AM

#

yea it does seem its still sleeping now that you point that out

#

Diagnostic
Battery level
20.0%
Last seen
1 hour ago

#

thanks

blissful canopy Sep 17, 2025, 12:31 AM

#

Battery devices (except ones like locks) are always sleeping, they will never respond to commands except for the "wake up interval", which could be hours, days, weeks.

#

Pressing the button (on the device) will wake it up immediately

true hemlock Sep 17, 2025, 12:32 AM

#

yeppers, i should have noticed it sleeping on the zwave map

blissful canopy Sep 17, 2025, 12:32 AM

#

I pretty much disable all of the battery Ping buttons, they are mostly useless.

true hemlock Sep 17, 2025, 12:32 AM

#

I'll have to go down in a bit an do that manually, i'm guessing that will fix it but will report back

blissful canopy Sep 17, 2025, 12:32 AM

#

Are you using the Z-Wave JS add-on, or Z-Wave JS UI?

true hemlock Sep 17, 2025, 12:33 AM

#

.. good question.

blissful canopy Sep 17, 2025, 12:35 AM

#

Ok, well if you download the diagnostic file from the device page, ... -> Download Z-Wave diagnostics, you can find the wake up interval time.

#

Search for wakeUpInterval, value is in seconds.

true hemlock Sep 17, 2025, 12:36 AM

#

yea, the config seems to have that avail just fine, but like i mentioned the device sleeps for like six hours before it wakes up, so the webpage doesn't 'hold' the change right ..

blissful canopy Sep 17, 2025, 12:36 AM

#

The config page won't tell you whether the setting is pending or not

true hemlock Sep 17, 2025, 12:36 AM

#

gotcha

blissful canopy Sep 17, 2025, 12:36 AM

#

Once you leave the info is lost

#Issues with parameters saving on zwave devices via GUI.