Aeotec garage door controller settings not retained after power outage

I have disabled the alarm on the garage controller, but after a power outage, the settings that disable the alarm are lost and I have to redo the settings to disable it again. I’ve also noticed that if I go back in to habmin after disabling the alarm the default settings are displayed. I suspect the default settings are sent after a power outage. does anyone know how to permanently disable the alarm?
Thanks

RPi3 OH 2.3

This part is something I remember from way back when. Even though you changed the parameter from the default it doesn’t change in Habmin.

Have you looked at the Thing in PaperUI? It supports parameters now and perhaps in this one regard it works better.

You can look at the debug or trace logs for the binding and verify whether or not the default is being resent to the device I think.

So you are saying that it’s not possible to set configuration parameters using HABmin? Or they set, but still retain the same value (which makes no sense either unless the device doesn’t send back the data).

What does the log show?

I can change the parameters and the device accepts the change. By which I mean the alarm does not sound when I open/close the overhead. But, if I go back into Habmin after verifying that the alarm is disabled, I see the default values for those parameters. These values are not doubt sent to the device after a power outage. I’ll look at the logs as well.

I’ll try PaperUI. I haven’t been using it to modify parameters for zwave devices, as I had always been getting 500 errors when changing settings for those devices. I don’t think I’ve tried since upgrading to 2.3. I’ll give it a try this evening and see if my changes persist.

This was years ago (maybe even back as far as 1.8, though I think it was 2.0 release timeframe) but I remember being told that after I set the parameter in Habmin that the next time I start up Habmin, or maybe it was even refresh the page, or even immediately that the default parameter is what would return instead of the new value that I sent. Maybe this was never a problem or maybe it got fixed? I can’t find the original post nor my notes from back then. I just remember making a mental note that I couldn’t always trust Habmin to reflect my changed parameters.

I’m not certain I have changed any of the parameters on any of my zwave devices any more. I can try it and see, though I suspect @lazloman’s logs will be more immediately useful.

Since I’m wrong more often then I’m right, I try not to respond to zwave postings anymore unless they have gone more than a day without a response. I apologize for all the messes you have to come in and clean up in my wake. :slight_smile:

That is exactly what I remember being told way back when.

Strange - what does the debug log show? The binding should read the value back, and this is what it is displaying. Maybe the device isn’t saving the value, and this is why it’s not surviving the power outage.

I’d be very surprised if it makes any difference as it sends exactly the same calls to the binding.

I’d check the debug logs - this will tell you what’s happening, otherwise it’s a but of guesswork.

If it was 1.8, then this is a totally different HABmin. It was completely rewritten at OH2.

Please check the logs so we can see what is happening as I don’t really see what it can be based on these explanations.

It will probably be tomorrow before I can get to my machine to generate some logs. I haven’t changed a zwave device parameter in months and don’t have any logs hanging around where I can get at them.

I sent the parameters to disable the alarm again from Habmin. Here is what I got in the log, debug level:

    2018-09-10 16:45:17.408 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27:     Configuration update received
    2018-09-10 16:45:25.431 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 02 06 31 05 01 2A 03 00 EF 
    2018-09-10 16:45:25.439 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2018-09-10 16:45:25.444 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 02 06 31 05 01 2A 03 00 EF 
    2018-09-10 16:45:25.449 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 02 06 31 05 01 2A 03 00 EF 
    2018-09-10 16:45:25.453 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 06 31 05 01 2A 03 00 
    2018-09-10 16:45:25.456 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
    2018-09-10 16:45:25.460 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2:    Starting initialisation from DONE
    2018-09-10 16:45:25.463 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@178d1bc already registered

Node 27 is the GDC.
Even after sending the parameters from Habmin. PaperUI displays the defaults. I tried to change on parameter 37, but got an error saying the minimum value is 1. I set this and all values from param 37-40 to 0. This is what it takes to disable the alarm.

This is the not right log - this is only the first entry with no information, and a temperature report from node 2. I think the only way this can be the only log entry is if there was no command processed at all.

Please can you provide the full log from just before the time you send the command, to 20 or 30 seconds later.

Here it is:

2018-09-10 16:45:17.408 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Configuration update received
2018-09-10 17:04:22.217 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling...
2018-09-10 17:04:22.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:f21cd9de:node27:switch_binary
2018-09-10 17:04:22.223 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 27: Generating poll message for SWITCH_BINARY, endpoint 0
2018-09-10 17:04:22.226 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Creating new message for application command SWITCH_BINARY_GET
2018-09-10 17:04:22.229 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:f21cd9de:node27:barrier_state
2018-09-10 17:04:22.232 [DEBUG] [verter.ZWaveBarrierOperatorConverter] - NODE 27: Generating poll message for BARRIER_OPERATOR endpoint 0
2018-09-10 17:04:22.235 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Creating new message for command BARRIER_OPERATOR_GET
2018-09-10 17:04:40.641 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 25 02 25 6B 95 
2018-09-10 17:04:40.661 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: Sent Data successfully placed on stack.
2018-09-10 17:04:40.682 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 107, Status = Transmission complete and ACK received(0)
2018-09-10 17:04:40.685 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:04:40.710 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2018-09-10 17:04:40.713 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:04:40.718 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class SWITCH_BINARY
2018-09-10 17:04:40.721 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Switch Binary report, value = 0
2018-09-10 17:04:40.724 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-10 17:04:40.727 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_BINARY, value = 0
2018-09-10 17:04:40.730 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:f21cd9de:node27:switch_binary to OFF [OnOffType]
2018-09-10 17:04:40.759 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-09-10 17:04:40.765 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 27: Response processed after 120ms/4887ms.
2018-09-10 17:04:40.779 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 66 02 25 6C D1 
2018-09-10 17:04:40.810 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: Sent Data successfully placed on stack.
2018-09-10 17:04:40.825 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 108, Status = Transmission complete and ACK received(0)
2018-09-10 17:04:40.826 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:04:40.851 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2018-09-10 17:04:40.853 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:04:40.857 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class BARRIER_OPERATOR
2018-09-10 17:04:40.859 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Received BARRIER_OPERATOR command V1
2018-09-10 17:04:40.860 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Barrier Operator report, value = 0
2018-09-10 17:04:40.864 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-10 17:04:40.866 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = BARRIER_OPERATOR, value = STATE_CLOSED
2018-09-10 17:04:40.869 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:f21cd9de:node27:barrier_state to 0 [DecimalType]
2018-09-10 17:04:40.885 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-09-10 17:04:40.887 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 27: Response processed after 104ms/4887ms.
2018-09-10 17:34:22.217 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling...
2018-09-10 17:34:22.219 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:f21cd9de:node27:switch_binary
2018-09-10 17:34:22.220 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 27: Generating poll message for SWITCH_BINARY, endpoint 0
2018-09-10 17:34:22.222 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Creating new message for application command SWITCH_BINARY_GET
2018-09-10 17:34:22.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:f21cd9de:node27:barrier_state
2018-09-10 17:34:22.225 [DEBUG] [verter.ZWaveBarrierOperatorConverter] - NODE 27: Generating poll message for BARRIER_OPERATOR endpoint 0
2018-09-10 17:34:22.227 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Creating new message for command BARRIER_OPERATOR_GET
2018-09-10 17:34:40.633 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 25 02 25 A6 58 
2018-09-10 17:34:40.662 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: Sent Data successfully placed on stack.
2018-09-10 17:34:40.671 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 166, Status = Transmission complete and ACK received(0)
2018-09-10 17:34:40.674 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:34:40.699 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2018-09-10 17:34:40.704 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:34:40.708 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class SWITCH_BINARY
2018-09-10 17:34:40.712 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Switch Binary report, value = 0
2018-09-10 17:34:40.717 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-10 17:34:40.719 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_BINARY, value = 0
2018-09-10 17:34:40.722 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:f21cd9de:node27:switch_binary to OFF [OnOffType]
2018-09-10 17:34:40.739 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-09-10 17:34:40.741 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 27: Response processed after 106ms/4887ms.
2018-09-10 17:34:40.751 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 66 02 25 A7 1A 
2018-09-10 17:34:40.777 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: Sent Data successfully placed on stack.
2018-09-10 17:34:40.790 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 167, Status = Transmission complete and ACK received(0)
2018-09-10 17:34:40.793 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:34:40.813 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2018-09-10 17:34:40.815 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2018-09-10 17:34:40.820 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class BARRIER_OPERATOR
2018-09-10 17:34:40.822 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Received BARRIER_OPERATOR command V1
2018-09-10 17:34:40.824 [DEBUG] [ass.ZWaveBarrierOperatorCommandClass] - NODE 27: Barrier Operator report, value = 0
2018-09-10 17:34:40.828 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-10 17:34:40.830 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = BARRIER_OPERATOR, value = STATE_CLOSED
 2018-09-10 17:34:40.832 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:f21cd9de:node27:barrier_state to 0 [DecimalType]
 2018-09-10 17:34:40.847 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
 2018-09-10 17:34:40.849 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 27: Response processed after 94ms/4887ms.

Thanks - there doesn’t appear to be any configuration being sent to the binding. I’m not sure what version you are using? Newish versions print every command that is received, but even without this I see no configuration being sent at all.

I would suggest to use the latest snapshot so we have the full debug. Also, in future please don’t filter the logs by the node number as it makes it difficult to process the logs with important information missing.