Fibaro Motion Sensor - Change Parameters by Rule

Hi,

which command can I use to change any parameter of the Fibaro Motion Sensor (“Magic Eye”), e.g. LED colour?

Thank you!

I don’t know if this will work:

check http://IP_OH2:8080/doc/index.html#!/things/updateConfiguration and play with the json

in theory, you can use sendHttpPutRequest to modify conf parameter #80: LED Signalling Mode on the FibEye (FGMS001 Motion Sensor)

@chris is this feasible?

Yes, this should work, or if this something people want to see, we can add it as a channel rather than having to use the rest interface.

1 Like

Personally, I don’t play often with the config params of my Z-Wave nodes…
After initial setup, I leave them as I like them
I don’t see many people backing up such feature enhancement (although it would be cool if it doesn’t take too much effort to develop)

just a quick encyclopedic question: How often / when will that config parameter reach the actual Z-Wave node?
Is this related to the wakeup interval?
scenario: I submit a config change now and I wait for 30 mins (wakeup interval) for the change to reach the endpoint and be actually implemented ? (edit: of course I can manually wake it up to avoid the delay… correct?)

If it’s a battery node, then yes, it will be transferred when the device wakes next. If it’s a mains node, then it will occur almost instantly.

Correct for battery nodes. Not though that it may not be 30 minutes - the device wakes every 30 minutes, so depending on when you send it, it will be up to 30 minutes.

1 Like

Thank you very much for these very quick responses! :blush:
@chris: Dealing with these parameters by channels would be perfect, of course, especially for beginner-greenhorn-newbies like me … :upside_down_face:
@Dim: Could you please provide an example command line please?

This is incomplete, so you need to fix it:

val String OH2_URL = "http://<OH2_IP>/doc/index.html#!/things/updateConfiguration"
val String Parameter_ID = "80"
val String Thing_UID = "zwave:device:512:node2"
sendHttpPutRequest(OH2_URL, "application/json", '{"blah_blah_using_val"}')

see https://www.openhab.org/docs/configuration/actions.html#http-actions

the “difficult” part will be figuring out how to structure the blah+blah
check the REST API to see how to structure a json payload to modify a config parameter.

Thank you very much! :slightly_smiling_face::+1:

1 Like