Fibaro FGFS101 Creates Basic Switch #6596
Unanswered
dcmeglio
asked this question in
Request Support / Investigate Issue
Replies: 2 comments
-
👋 Hey @dcmeglio! It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS. Please double-check that you uploaded the correct logfile. If you did, disregard this comment. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
0 replies
-
What the bot said. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening?
Fibaro FGFS101 (a leak sensor) has a Basic switch after the recent changes. I tried doing the proposed re-interview fix, and now I have two Basic switches:
Oddly doing it a 3rd time did not create a 3rd switch
What did you expect to happen instead?
This switch doesn't seem to do anything or make any sense for this device.
Steps to reproduce the behavior:
Pair a FGFS101 and look at the device entities in Home Assistant (Note I know this is about Home Assistant but https://community.home-assistant.io/t/psa-upcoming-z-wave-js-changes-and-z-wave-certification-how-it-impacts-you/638288#what-probably-brought-you-here-basic-cc-light-3 says to report it here)
#6516 seems to suggest this bug is fixed but I can't get the switch to disappear with a re-interview.
Software versions
Driver (node-zwave-js): NA
Z-Wave JS UI: 3.1.0
Home Assistant Z-Wave Integration: NA
Home Assistant Z-Wave JS Addon: 3.1.0
ioBroker.zwave2 Adapter: NA
If you are using something non-standard, tell us here: ...
Device information
Manufacturer: Fibaro
Model name: FGFS101
Node ID: 87
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
z-ui_2024-01-06.log
Beta Was this translation helpful? Give feedback.
All reactions