So I figured out a workaround for the time being…
Setup the symfonisk and assign the push button to a single function like Turn Off.
Then using a REST client, change the rule to be a next scene function.
GET /api/<apikey>/rules
Find, and note, the turn off rule with the symfonisk, looking for its mac address makes it easier.
Copy the rule of interest, for example rule id 15 here:
"15" {
"actions": [{
"address": "/groups/5/action",
"body": {
"on": false
},
"method": "PUT"
}],
"conditions": [{
"address": "/sensors/65:4e:5f:c5:80:a2:f2:1c-01-1000/state/buttonevent",
"operator": "eq",
"value": "1002"
}, {
"address": "/sensors/53:03:a3:69:5e:36:5d:18-01-1000/state/lastupdated",
"operator": "dx"
}],
"created": "2021-10-26T13:57:43",
"etag": "89we07rf0w98fsdnofiusdoifuho9387",
"lasttriggered": "2021-10-26T14:23:20",
"name": "Rule OFF",
"owner": "J8ASKA9A7H",
"periodic": 0,
"status": "enabled",
"timestriggered": 25
}
Modify it to become like this:
{
"actions": [{
"address": "/groups/5/scenes/next/recall",
"body": {},
"method": "PUT"
}],
"conditions": [{
"address": "/sensors/65:4e:5f:c5:80:a2:f2:1c-01-1000/state/buttonevent",
"operator": "eq",
"value": "1002"
}, {
"address": "/sensors/53:03:a3:69:5e:36:5d:18-01-1000/state/lastupdated",
"operator": "dx"
}],
"created": "2021-10-26T13:57:43",
"etag": "89we07rf0w98fsdnofiusdoifuho9387",
"lasttriggered": "2021-10-26T14:23:20",
"name": "Rule CALL_NEXT_SCENE",
"owner": "J8ASKA9A7H",
"periodic": 0,
"status": "enabled",
"timestriggered": 25
}
Then put the modifications into place using:
PUT /api/<apikey>/rules/<id>/
Symfonisk button now works as a scene changer, still shows up as Turn Off in Phoscon.
Some specifics have been randomized.
More details:
https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/
https://dresden-elektronik.github.io/deconz-rest-doc/endpoints/rules/