[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Z-wave start

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Initializing Z-Wave

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Opening port

This happens every hour. Does anybody have an idea, what the issue is?

I can see location requests from the app on my phone, but the scene doesn't trigger.

Is anyone else experiencing this issue?

I would like to ask for clarification regarding the current state of Z-Wave 3 support in the Fibaro ecosystem.

Is the migration from Z-Wave 2 to Z-Wave 3 now considered safe and fully functional, or is it still in a beta stage?
In particular, I’m interested in how well Fibaro devices - especially the Fibaro Heat Controllers - perform when connected through Z-Wave 3.

The migration process requires a considerable amount of work on my side, so I’d like to make sure that the new implementation is stable and reliable before proceeding.

Below I’m quoting part of Fibaro Support’s response regarding Z-Wave 3 and Heat Controller. At that time, it was true.
Now, perhaps this information is already outdated?

Info from ticket dated 10.01.2024

Ticket ID: 288045

Chcę też zauważyć, że używa Pan centrali Z wersją silnika Z-wave 3.0, który jest obecnie w wersji beta. System z takim Z-wave'em należy traktować jak środowisko testowe. Wersja Z-wave 2.0 jest w wersji stabilnej.
 

I have a question are there any circumstances under which the HC3 might restart automatically?
I’ve noticed that roughly once a day the system reboots by itself. It happens quickly, so it’s not easy to catch during normal operation.

At the moment, around 89% of RAM is in use could it be that when it reaches 100%, the controller triggers a restart?
In the past, the HC3 occasionally froze and stopped executing scenes, but since the latest update, I haven’t noticed that issue anymore.

My setup is quite large  over 112 Z-Wave devices, with around 35% of internal storage used.
I also have many energy meters reporting data every 10 seconds.

Right now, the system seems stable, but I’d like to understand whether these periodic restarts are normal behavior or if they might indicate a hidden problem.

Thanks in advance for any insights!

Best regards,
Grzegorz

can any help me out?

Unfortunately the fibaro id is not connected and I don't know where to connect it. 

My HC3 is wired. 

When looking at the cloud its active.

How do I connect to HC3 with my fibaroID?

Thanks!

Please login or register to see this attachment.

Please login or register to see this attachment.

Hi Fibaro Support/Users,

I am writing regarding a critical problem with my Home Center 3 installation. I am the installer and end user. The controller is used as the main brain for all lighting in my house, so this is currently a severe issue.

Hardware setup

– 1 × HC3 master – Serial number: HC3-000XXXXX 

– 1 × HC3 slave – Serial number: HC3-000XXXX1

The master (HC3-000XXXXX) has been running stably for about 5 years and controls all lighting and scenes. The slave is used as an additional controller.

Problem

Suddenly, all scenes and Z-Wave control stopped working. The house is effectively without light control (only “dumb” lamps work). At the same time:

– The master HC3 shows a red gear LED / error state.

– The web UI is reachable on the IP address, but only shows the login screen.

– None of my known credentials work (admin/admin, password from label, or previous user credentials).

What I have tried (on HC3-000XXXXX)

1. Power cycle (several times) – no effect.

2. Recovery Mode via + button:

   – Power off, hold “+” button, power on, release when LEDs start the left-to-right sequence.

   – Yubii Finder correctly shows the unit as “Recovery Mode”.

3. From the Recovery web interface (System A v5.190.38), I have run:

   – Auto Repair

   – Repair System A

   – Recover / Factory Reset from the Recovery screen

4. After Factory Reset, I:

   – Tried to log in with admin / admin → rejected.

   – Tried the password printed on the label → rejected.

   – Tried my usual HC3 user credentials → rejected.

5. I also attempted to restore from Cloud backup after Recovery, but this just restores the previous (unknown) passwords, so I am effectively locked out again.

In other words:

– I can access Recovery Mode and execute all repair/recover options without error messages.

– But I cannot log into the normal UI at all, even after a Factory Reset, and scenes/Z-Wave do not work.

– The behaviour does not match the manual (which states that after Factory Reset, I should be able to log in with admin/admin on a clean system).

Why this is critical

– HC3-000xxxxx is the master for the whole house lighting.

– There is currently no functional Z-Wave control from the master.

– The unit appears to be stuck in a state where Recovery works, but normal system/login is corrupted or not reset correctly.

My questions / what I need from you

1. Can you confirm whether this is a known issue with the current firmware (v5.190.38 or similar)?

2. Is there an official procedure to:

   – Completely re-flash the firmware on HC3-000xxxxx (beyond the standard Recovery/Factory Reset), and

   – Ensure that the unit comes up as a truly clean system with admin/admin?

I have multiple cloud backups available, and I am willing to:

– Either restore from backup once the unit is truly clean, or

– Start from scratch if necessary, after a proper low-level reset or replacement.

At the moment, the key issue is:

Even after Recovery and Factory Reset, HC3-000xxxxx does not behave as a clean controller and will not accept any documented default credentials.

I would appreciate a concrete recommendation (re-flash procedure, downgrade, or RMA) and, if possible, step-by-step instructions for the next actions.

Kind regards,
Carsten

Any idea why?

Please login or register to see this attachment.

Please login or register to see this attachment.

Quote

The update was not performed due to an incorrect system image verification. If the update was performed manually through the system Recovery, please ensure that the correct version of the system was used.

Please login or register to see this code.

Please login or register to see this attachment.

But the major issue that after reboot all ZigBee devices are disconnected and inaccessible. Needs to reset Zigbee and to upload lates backup and after 30~40 minutes everything back to normal. 

Until this update I was able to change or add device property "mainFunction", but not anymore. New quick app of type "com.fibaro.deviceController" refuses it. Why? I just added following quick apps types:

com.fibaro.genericDevice

com.fibaro.deviceController

com.fibaro.player

com.fibaro.weather

com.fibaro.colorController

and they are all missing property "mainFunction" and can't be added. Note that same type of devices added prior to this update have this property.

So history repeats itself. Same was when I was developing UHAS for HC2. With almost every stable version I had to go back to the beginning and rewrite my code because somebody decided to remove or change something. It seems that nothing in your world of automation is not definite and there is no guarantee that will work after next update. Very disappointing 😪😪😪😪

Just tested this function and found that is useless.

I wanted to send "MobilePopupNotification" with following code:

Please login or register to see this code.

Above code does not work in quick app.

When executed I get following error:

[09.10.2025] [18:43:00] [ERROR] [QUICKAPP37]: QuickApp crashed[09.10.2025] [18:43:00] [ERROR] [QUICKAPP37]: main.lua:30: attempt to index a nil value (field 'homeCenter')

When run from scene, then it seems it works and debug is:

[09.10.2025] [18:47:45] [DEBUG] [SCENE5]: response: {"wasRead":false,"recipient":2,"priority":"info","id":3,"created":1760028465,"canBeDeleted":true,"data":{"text":"sampleText","buttons":[],"title":"sampleTitle"},"type":"MobilePopupNotification"} code: 200

but I get only this in GUI:

Please login or register to see this attachment.

and there is nothing received in Yubii Home mobile app latest update.

So @m.roszak, any comments on this one?

Am I doing it wrong, or this part is still not finished since 2020?

Thx

@A.Socha @m.roszak

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this attachment.

Important notice:

    Version 5.190.38 is a hotfix for version 5.190.36.

    The update resolves:

        Fixed control of venetian blinds when using BiDi-Shutter and BiDi-Awning modules.
        Fixed the display of the scene list in the interface for the Norwegian language.

Main features:

1. New interface design.

A new, refreshed user interface design that will make using the interface even more enjoyable.

2. New Smart Implant / Smart-Control device pairing wizard.

A new, dedicated device pairing process in the Yubii mobile application and web interface, where you can easily add and configure your device.

3. Improved security.

Application of cybersecurity guidelines in accordance with the new regulations (RED) and the Data Act.

What's new:

Access

    Added the ability to delete a user yourself in user settings.

Devices

    Added new sets of icons for roller shutters.

    Improved curtain behavior when controlled via interface.
    Adapted the Husqvarna plugin to the new manufacturer API.

Elero

    Support for Elero Bi-rec device (Veinor).
    Support for Elero RGBW device (Veinor).
    Reduced polling for the VarioTec-868 device.
    Improved the type definition for the Revio4M device from a light to roller blinds and venetian blinds.
    Improved the name and icon for the Sun Motion 868 device.
    Add new device types for new RolAir motors.
    DuoSON-868 device integration.
    AstroSON-868 device integration.
 

Energy panel

    Added the ability to set rates for tariff with the precision of quarter of an hour.

Nice*

    Support for TTDW and TTDRGB LED strips devices controllers.
    Improvements in binding procedures using already memorized transmitter.
    Improved communication with the radio chip.
    Group actions are now handled simultaneously for quicker reaction to commands. 
    Added generic support for devices with unknown product types.
    Reduced polling for battery-powered devices.
    Support for the ERA Inn Li-ion battery-powered device.
    Cleaned up the system devices model for monodirectional devices by removing redundant device's roles.

Other

    Documents for Privacy Policy and Terms of Service have been separated when updating the Hub.
    Changelog history added when updating the Hub version.
    Changed graphics for Energy Panel charts.
    Added Swagger documentation for /api/mobile/settings.
    Updated Privacy Policy according to the new Data Act regulation.
 

Quick Apps

    The preview tab is updated on-the-fly after copying the JSON view.

Scenes

    Performance improvements in scenes execution in large systems.
    Scene launch optimization.
    Possibility to send e-mails to Installer from LUA and block scenes.
  

Z-Wave

    Improvements for handling the reports in Alarm V2 Command Class.
    Z-wave engine 3.0 is set as default in the FTI process.
    Updated parameters template for FGR-224/Roll-Control 2 for version 8.2.
    Added support for class Thermostat Fan Mode version 5.
 

Bug Fixes:

Access

    Improved display of full screen camera view for advanced user.
    Fixed an issue with the use of an outdated password reset email template for some languages.

Climate

    Fixed incorrect calculation of the temperature value for thermostats auto mode.
 

Devices

    Fixed assigment of the whole device to specific room when adding devices from the mobile app.

    Added the ability to manually enter values for Multilevel sensors when pairing devices in the mobile app.
    Fixed the slider display when the thermostat is set to the maximum value in the device preview.
    Fixed the control dialog for the Nice BiDi-Shutter device as a Venetian blind.
    Missing source information in DeviceActionRanEvent.
    Fixed the display of long device names in modal windows.
    Full https support for Nice Cameras and NVRs.
    Fixed display of statuses in the Dashboard for colorController and multilevelSwitch devices.
    Optimised web UI wizards for some devices.
    Fixed an issue where the device removal process in the mobile app would loop.
    Fixed issue with loading multiple icons for devices.
    Fixed a screen freeze in the device removal process in IOS mobile apps. 
    Fixed slider performance in advanced device settings.
    Added missing toggle action for MultiPositionSwitch devices.
    Fixed the issue of displaying a message disconnected when the camera preview was working properly.
    Fixed saving of advanced settings when changing tabs in the device list.
    Fixed display of the "on" status for devices inheriting from the colorController type in the interface
    Unlocked the process of adding devices when Z-wave learning mode is enabled in the interface.
    Fixed display of device statuses in the history panel.
 

Elero

    Improved the connection process when grouping Elero devices.

Gateway connection

    Fixed an issue with reverting to the schedule for MCOHome MH8 devices on a slave Hub.
    Removed duplication for Support and Installer users in the database after updating from version 5.161.15 or higher with gateway connection setup.
    Fixed device counting in backups for the Master Hub.

Nice*

    Fixed moving to favorite position for mono devices.
    Improved wake-up from the Hub for the Climatic sensor battery-powered device.

Other

    Fixed selection of devices on the Reset Elero network dropdown list.
    Fixed the 8-character limit for entering Wi-Fi passwords during the FTI process.
    Improved handling of the /api/scenes endpoint in Swagger.
    Fixed SVG icon colors in dark mode for scenes.
    Access Point is available again in Recovery Mode.
    The save button is active again after setting a new location from the map.
    Minor UI/UX fixes.

Quick Apps

    Improved refreshing in the setColorComponent function for Quick Apps.
    Added support for uploading external icons for Multilevel Sensor device type.
 

Scenes

    Removed redundant unsaved changes dialog when no changes were made when editing scenarios.
    Fixed issue with saving default Morning Scenario after making changes.
    Fixed scenes trigger based on current color for Block Scenes.
    When creating a new scene from the Scenes Dashboard, the editing screen opens.

Users

    The "Continue" button is not active during the user deletion process.
 

Z-Wave

    Improved node id (associations) handling when controller has different NodeID that 1.**
    Fixed the issue of lost Zipato RFID device reports.**
    Fixed invalid parameters 2,3 value for HeatIt Z-Temp3 device.
    Fixed a rare issue where learning mode would freeze.
    Fixed template for Aeon Multisensor 6 device.
    Fixed an issue where the “Check for updates” button was inactive after adding a Z-Wave device.
    Console opened in new windows does not scroll automatically when ZW3.0 is used.

Known issues:

Z-Wave Engine 3.0

    Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine.

* - Does not apply to HC3L (Home Center 3 Lite).
** - Applies only to Z-Wave 3.0 engine.

Security:

    The option to use only the HTTP protocol in network settings has been removed.
    Log security has been improved through additional security measures for private user data.
    Security actions have been separated into separate, additionally secured Hub logs.
    Secure communication for the Z-Wave device update service has been added. 
    The master Hub communicates with the slave Hub only via a secure https connection.
    Restricted unauthorized API and backup file requests.
    Updated some low-level libraries.
    Database protections against storing private data.
    Fixed error codes returned for authentication errors.
    Fixed potential RCE vulnerabilities.
    Removed information regarding the existence of usernames in the system for the password reset mechanism.
    Reduced vulnerability to DoS attacks.
    Improved log file encryption.
    Due to the upcoming new cybersecurity regulations (RED), work has been implemented to improve the product's security level to comply with the EN18301 standard and the latest security guidelines.
    The user password reset procedure has been changed - user sets a new password himself.
    The number of required characters in a user password has been increased to 12 - for new users and when changing the password for existing users.
    Added email notification for administrator regarding unauthorized login attempts when an unknown user logs in.
    The default login password for the FTI process has been changed for the ones from device label.
    Improved security for requests from localhost.
    Increased security for plugins: Husqvarna Mower, Tedee.
    Cross-Site Scripting vulnerabilities fixed.
    Additional security for users in the Recovery Mode area.
    Added protection against PIN brute-force attacks.
    It is possible to make 3 attempts to disarm alarm partition before the alarm is triggered.
    The procedure for assigning passwords to new local users has been changed - the user sets his own password in the system.
    Improved encryption and security in databases.
    Added the ability to report a security issue has been added as an extension of the Support Department option.
    Added information for the user when attempting to perform potentially dangerous actions in the interface.
    Sensitive device data removed from databases.
    Due to the EU Data Act regulation, changes have been introduced to enable the download Hub data and user data
    - from the Hub settings level
    - from the user settings level.
    The Privacy Policy and Terms of Service are accepted by every user, not just the administrator.
    Data submitted for analytics is available in Swagger for administrators.
    Improved crash dump encryption method.