I am trying to disable the led ring for the Fibaro wall plug with HABmin. When I change parameter 41 the interface continues showing a ‘waiting…’ message. I can see the new parameter value in paper UI. But the led ring itself is not changing.
While talking, I was updating my RPi, so I’m currently running build #884. The “waiting…” message does not show anymore, but the ring still isn’t working.
The log does not show much when I click the Save button in HABmin (setting log level to TRACE does not show anything else:
It does - but it doesn’t log “you clicked the save button” - it logs when configuration is updated though, and it logs the messages sent from the controller to the device, and it logs the responses… All useful stuff
I can’t see how this is possible since both UIs are reading the same information. Neither UI is deciding the device type - the binding does that. Can you provide a screenshot of what you mean when you say they are being identified differently by the two UIs?
You state that the 102 device does nit support the 41 parameter, but it is available in HABmin. See my screenshot. Or do you mean the 2 versions of the 102 device in the database?
If so I will check the database against the manual and update accordingly.
HABmin will only display what’s in the database - it’s not deciding anything itself.
I just noticed when looking at the two versions in the database, that only 1 version (the newer one I think) has parameter 41. The older one doesn’t have this parameter.
I found this manual for (probably) a different type of device. This device has parameter 61 instead of 41 for color setting. I have not properly investigated yet, but perhaps the versions got mixed up. The 3.2 version is zwave plus compatible.