That’s no problem. It may well help others trying to learn how it is done
I’m not out of the woods yet though, This is the log output but the system does not disarm…
2019-01-16 20:08:00.429 [ome.event.ItemCommandEvent] - Item 'SEND_DSC_ALARM_COMMAND' received command 040,1
==> /var/log/openhab2/openhab.log <==
2019-01-16 20:08:00.430 [INFO ] [se.smarthome.model.script.Alarm test] - ---------------> Alarm off
==> /var/log/openhab2/events.log <==
2019-01-16 20:08:00.439 [nt.ItemStatePredictedEvent] - SEND_DSC_ALARM_COMMAND predicted to become 040,1
2019-01-16 20:08:00.446 [vent.ItemStateChangedEvent] - SEND_DSC_ALARM_COMMAND changed from 500: A command has been received successfully. to 040,1
The command is (and the actual code is stored in the binding config through PaperUI):
sendCommand(SEND_DSC_ALARM_COMMAND, "040,1")
Sending the disarm through HabPanel works fine, so I’m just stuck on this issue.
I don’t see your definition for the SEND_DSC_ALARM_COMMAND item in the item file. Is that defined elsewhere? It doesn’t seem to be linked to the correct channel.
Excellent spot. The problem was a mistake in my item definition (as you correctly pointed out it was not linked to the correct channel). Now it works fine.
Apologies for resurrecting this old thread but I just finished my remote alarm control page and I had to use 071 because 040 only works with the user code stored in the config (which I don’t want to store). Is there a possibility to allow 040 to work with a user code appended? The Envisalink documentation warns users to avoid using 071 because it is possible to accidentally enter installer mode and you may need to power cycle the alarm system to get out of it.