New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fibaro Walli Switch cannot set config #3557
Comments
Hi! Which parameter (configuration option) does not work? Can you please enable debug logging on the Z-Wave controller, then do "Refresh node info" + whatever config you are trying to change then zip and upload OZW_Log.txt? I'll have a look at it.
I remember, I merged the PR for you.
The "protection" instances you see are not "parameters", they are a different command class and OpenZWave can obtain them by interviewing the device. So even though you did not write that in the config/fibaro/fgwds221.xml file, OZW discovers them. That is OK. Parameters cannot be discovered (in general) and that's why you have to enter them in the config file. |
@TerrorSource, the process of getting new configuration files inside Domoticz from the OpenZWave repository is not an automatic job and needs to be done manually |
Here the requested data. Already removed the unnecessary lines from the log(working sensors) 013 (0x0d) | FW_Badkamer | FIBARO System FGWDS221 Walli Double Switch+ | FIBARO System | 0x1000 | 0x1b01 | 2019-08-12 08:50:06 | No 2019-08-12 08:48:39.384 Status: OpenZWave: Closed |
Thanks, very kind of you and interesting, but that log does not contain any useful information about this issue. The log does not have the level of detail I expect. If it would, it would be much, much larger and that is why I asked to zip and drop it here... Don't paste it in a text box... Can you please enable debug logging on the Z-Wave controller, then do "Refresh node info" + change whatever config you are trying to change, then zip and upload OZW_Log.txt? That file would contain hundreds or thousands of lines, quite a few with hexadecimal codes, like this
|
I did exactly that.
I can change a config on the Walli Switch but i cannot save it. I can press the "Apply configuration for this device" button but it does nothing. While i can change config's on non-Walli sensors. |
I believe you, but you did not zip and drag & drop the OZW_Log.txt file here... That file is in your Domoticz folder, under Config |
Hopefully this is what you want/need. |
Yes, excellent, that is the file! I had a quick look and I can see you've refreshed the node info, that's good. Detailed analysis will take more time. |
I am pretty sure it is caused by the definition of parameters 30 to 34. They are actually not lists, but 32 bit integer values. I don't own this device so I cannot test this, but I can revise the config file so you can test it... |
Here's the file. Please stop Domoticz, unzip, overwrite the existing file in your domoticz/config/fibaro folder with this one, start Domoticz and do "refresh node info" on this node (in hardware, openzwave panel of domoticz). Then please try to change a parameter and tell me what happens, and zip and drag & drop the OZW_Log.txt file here like you did previously. That was really helpful. |
hello, I had the same issue, not able to apply the configuration. I did what you mention and it's working now! thanks! |
Thank you for chiming in! I'll push the change to OpenZWave master, probably today. |
@petergebruers Works! Can you do the same for the Walli Dimmer? Which has the same issue. |
Voilà. Definitions fixed in OpenZWave Version 1.6-912-gcc7a277c |
Fixed by @petergebruers |
Hi,
I've written the OpenZwave config for the "FIBARO System FGWDS221 Walli Double Switch+" which is now merged into Domoticz.
When i wrote the config, i was able to set config's and apply them on the sensor. Now, it is not possible anymore with the latest version of Domoticz.
I also see config's i did not set in the OpenZwave config.
Config i wrote is on OpenZWave/open-zwave#1869
config's which i did not wrote:
3001. Instance 1: Protection: Unprotected
Protect a device against unintentional control
Instance 2: Protection: Unprotected
Protect a device against unintentional control
Instance 3: Protection: Unprotected
Protect a device against unintentional control
The text was updated successfully, but these errors were encountered: