Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team
- 0
Question
Vitruv 0
Good Evening
I am writing to report a critical bug affecting the FGS-213 Single Switch 2 after updating its firmware from version 3.3 to 3.4 on a Yubii Home Pro hub running firmware 5.210.12.
Environment:
- Hub: Yubii Home Pro, firmware 5.210.12
- Device: Fibaro Single Switch 2 (FGS-213), 3 units installed
- Z-Wave Engine: 3.0 (ZW3)
Steps to reproduce:
1. Perform firmware update 3.3 → 3.4 via Settings → Devices → Updates
2. Update completes successfully (status: "Fertiggestellt" / Completed)
3. Click "Reconfigure device" ("Gerät neu konfigurieren") as suggested by the UI
Observed behaviour:
- After reconfiguration, the device's Parameter Template is set to "No" (Parametervorlage: Nein)
- The Parameters tab in the device view becomes inaccessible
- Z-Wave Type drops from 3 to 0, SDK Version drops from 4.24 to 0.0
- Each additional "Read configuration" click further degrades the device profile
- Endpoint XX.1 (Binary Switch, the actual switching channel with energy metering) is permanently deleted from Yubii — not hidden, but fully removed
- Endpoint XX.0 remains and can switch the load, but has no energy metering capability
- Energy reporting (Watt / kWh) is permanently lost until a full Exclude + Include cycle is performed
Important note: The "Reconfigure device" button appears directly in the Updates view after the firmware flash completes, with no warning that it may destroy the device profile. This makes it a high-risk trap for end users.
Additionally, I observed that on two of the three units, the firmware update did not complete at all (devices remain on version 3.3), despite the update process appearing to run.
Requests:
1. Is this is a known bug and do you know if a fix is planned?
2. Anyone knows whether there is a recovery path short of a full Exclude + Include cycle?
I am happy to provide log files, device IDs, or further technical details if helpful.
Thank you for your help.
Edited by Vitruv0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.