PS:You can see on the attached video which I started when the device started to stop respond to ping requests and web ui was not working, from time 0:30 the device seems to reboot but never makes it through until the end of the video-

This always happens after a power outage.

The devices work after restoring the last stable version (not beta) for 2 hours - then they are all inactive, I've exhausted the search options that came to my mind.

So

- I did it through the recovery system A and B - I reset them and restored the copy and still the same.
- I restored the backup copy on A and B, reset
- I unplugged it for 10 minutes ...

Does anyone have any ideas?
Can you help me?

In one of our projects, we are using Heltun Smart Switches and Smart Thermostats with Z-Wave Engine 2. While the devices are configured and working, there's an issue:

• When I turn on/off the lights manually from the smart switch, the status does not update in the mobile app.
• However, if I control the lights through the mobile app, the status updates correctly.

In our office demo unit running Z-Wave Engine 3 (Beta), this issue does not occur. It works perfectly for both manual and app-based controls. When adding the Heltun device in Engine 3, I noticed it prompts for a security key ("S2"), which I understand is only available in Engine 3.

From the Fibaro Forum, I gathered that upgrading to Engine 3 requires a factory reset and re-adding all devices with their security keys, which is not ideal as we have already configured many devices in this project.

Is there any way to resolve this issue without upgrading to Engine 3 and re-adding all devices?

Thanks in advance for your help!

MSJ Smart Home 

Technical Team

Another question that arises is the new properties, interfaces, and actions in the device structure. These new items add better functionality but their implementation seems to be lacking (or I haven't figured out how to trick the system into using them). Is there any idea when these might be functional? Would there happen to be any documentation available as to how to use them? Fibaro is not known for producing any meaningful documentation so I'm not holding my breath.

Thank you.

Peter

The latest Hotfix does not let install itself, as the "Install" button does not become active. 

How to do this? 

regards, Jeroen 

Please login or register to see this attachment.

Improved performance for executing bulk actions.

Improved device availability-check module (marking devices as not reachable).

Support for MOES Human Presence Sensor ZSS-QY-HP added.

Please login or register to see this image.

New install and it doesn't work, I guess it would need a new update ............ :)))))))))

1) Unique PIN Error - When I go to label an existing Pin slot it won't let me without setting the pin, which is fine. However, if I attempt to use the existing pin it errors stating the PIN needs to be unique. This results in the extra step of setting it to a different PIN, saving, and then going back and setting it back to the preferred PIN per person. Not the end of the world as I don't expect to be adding a lot of already programmed locks, but it is annoying.

2) PIN not displaying - When clicking the eye icon to view existing PINs it simply changes from 4 small asterisks to 4 larger and higher placed asterisks. Not very helpful.  While I understand that anything not program through the hub wouldn't be known and this would be the expected function. I however would expect the hub to remember the pin for display after I set a new one. Otherwise, what is the point of the eye icon to display them?

Cytat

Support for FGDW-002 in version 3.3 added.

I was hoping I will be able to get huge list of devices solved finally. Ufortunately that's not the case. There's however a difference in the experience. Previously clicking on update was resulting in whole Z-Wave being very busy and unresponsive. And update resulting with an error right after clicking the update the button.

With new HC firmware, the experience is that it tries to update the software - it goes from 0% to 100%. Meanwhile the z-wave is very laggy again (up to couple of minutes to react to opening doors etc). After hitting 100% device disappear from the list and reappear after few minutes, and HC remains laggy.

Please verify this information. To me, release of 5.170.13 did not improve the situation.

I'd like to report one bug with this type of QA device. It is same problem regardless of the role setup, for which is actually missing drop down menu so must be changed within the code: self:updateProperty("deviceRole","Rgbw").

When warm white slider is moved this is what I get:

Please login or register to see this code.

As you can se from above debug, trace prints some table that show correctly received value from the slider, but  value of w is always 0 from:

function QuickApp:setColor(r,g,b,w)

second debug line is get from this code:

Please login or register to see this code.

Can you please check and revert? Also, how I can get and read that table from the trace line from LUA code?

Thank you in advance!

Oh, and why is slider name "WARM WHITE"? What If I get clod white LED? I think it is enough to call it "WHITE".

On updating to version 5.170.13 the /scenes/{sceneID} PUT API gives an error code 500 and 'Internal Server Error'. 

This occurred with both the Admin account and an account with the new access structure.

Rolling back to version 5.160.42 it works fine, completing the changes successfully with a 204.

Has anyone else had this?  Any workarounds?

I started to use drop down selector on my QA devices. It is in many cases much better than adding 5 to 6 buttons to scroll through options usually saved as table in some variable.

Now I come to the problem related to the view of devices in Yubi Home mobile app (which BTW I prefer over the Yubii app).

In the QA device old view drop down selector is of definite size (usually shows few items), but if QA is really small, like has one label above drop down list and drop down list then list is not shown completely (bottom part is below lower edge of my mobile screen).

The good thing is that I can still scroll options with finger and select the last one on the bottom of the list.

Bad thing is that to have it properly shown on mobile app I have to add few more labels or buttons to get better view. Good thing is when I select an option then list is closed.

On the other hand QA device new view when opened expands QA and is of nice size, but bad thing is that drop down list is NOT closed after an option is selected. If list is bigger then I still have to scroll back up to use yet another tap to close drop down list.

BTW - similar is on GUI Dashboard when QA is in view mode. Big difference and same behavior.

Can you please verify with development team. Maybe it is not bad practice to at least test this basic stuff. Trust me, look & feel + functionality is the must for most of the users

Today when I logged in to my HC3 I found that order of rooms on GUI home page was different than my original setup. Don't know what caused this. I use Yubii Home app, but didn't do any changes with app. Mostly I use app to check my solar system status for now.

Anyway, after sorting rooms in order I want them under the Settings -> Rooms and going back to home page rooms were still shown in different order until I logged out and logged in again. Is this expected behavior or there is a bug?

Update 5.170 broke Billing periods comparison. The Previous data has always same value it doesn't matter if you select "Week", "Month" or "Year".

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Will we be able to disable the new mobile view on child devices to soon?
Or should it follow the main device view? 
Main:

Child:

Main features:
 

1. New device control views

    A new way of controlling all device types from the Dashboard and preview in device settings for a better user experience.

2. Advanced user

    Introduction of a new type of user in the system with configurable access to system settings. 

    From now on, the administrator can decide which parts of the configuration interface will be accessible to users who are not system owners.

3. Gateway Connection with Z-Wave Engine 3.0

    Systems using the new Z-Wave engine can now use the Gateway Connection feature.

4. New icons sets for sensors, binary and multilevel actors

System provides new sets of icons for presenting the devices and their states in more clear way. New icons apply to the following devices:

• Binary Sensors
• Multilevel Sensors
• Binary Switches
• Multilevel Switches.

Make sure that you are using the newset version of the mobile application for the best experience.

What's new:

Access

New UI for configuring access settings for normal users.

Alarm

By default, triggering an alarm will now result in sending a Critical Push (iOS) and Push (Android) for the new Yubii Home app.

Climate

A new way of direct zone control from the climate dashboard.

Dashboard

Adjusted icon sizes for better visibility.

Devices

Support for the dark theme for the new binding wizards in the mobile application.

Updated and added new binding instructions to the binding wizards.

Support for FGDW-002 in version 3.3 added.

Updated some parameter templates for various supported devices.

Minor UI/UX improvements in the binding wizards.

Improvements in Linked Devices (blinds).

Calibration of devices now available in advanced device settings.

FGT-001 external sensor temperature offset setting removed.

Added support for Zipato RFID.**

Gateway Connection

From now on, the upper limit for allowed slave hubs is set to 15. 

Nice*

Added support for 2nd favorite position for Nice screens and blinds.

Added a feature for synchronous movement of blinds and shutters using Bidirectional radio protocol when used in group actions.

Other

From now on, restoring a backup or switching the system won't disable Remote Access for support if it was enabled before the procedure.

Minor UX and UI improvements.   

Plugins

WakeOnLan plugin UI fixes.

Improvements in Nice Cameras plugin for better streaming performance.

Quick Apps

Added the possibility to set custom views for child devices.

Added the possibility to copy view definitions to the clipboard (works with HTTPS connections only).

Added the possibility to add custom view elements to thermostat views.

Improved webview performance.

Remote users

    Added the possibility to download and upload backup for Support and Installer user.

Scenes

Support for the dark theme for Simple Scenarios.

The Sound Switch device type added to Simple Scenarios.

Added new sets of icons for scenarios. New icons relate to:

• • Garage Door - open and close
  • Gates - open and close
  • Shutter - open and close.

Z-Wave

User Code command class support added.**

Simple AV Control command class support added.**

Inclusion and configuration of supported devices performance improvements.**

Added support for numerous old-gen devices (ZW300, ZW500 series).**

Disabled blur on the Z-Wave console during the device-adding procedure.

The Security S0 adding mode disabled by default.**

Zigbee

Improved performance for executing bulk actions.

Improved device availability-check module (marking devices as not reachable).

Support for MOES Human Presence Sensor ZSS-QY-HP added.

Bug Fixes:

Access

Fixed access rights for Advanced user.  

Fixes in the UI for configuring rights for advanced user.

Backup

Fixed rare error during backup restoration. 

Cameras

Fixed camera previews in some cases.

Climate

Fixed displaying values in Fahrenheit in the preview of the climate zone.

Dashboard

Fixed Drag&Drop for devices on dashboard, enabling the reordering of devices in room.

Devices

Fixed default icons for some device types.

Toggle action support fixed for the multiposition switch device type.

Fixed incorrect message when performing calibration of FGD-221 device.**

Fixed setpoint graph for FGT-001, which was not correctly shown in some cases.

Unable to add device in Security S2 if the PIN was incorrect (out of allowed range).**

Minor UI fixes in FGR-224/Roll-Control 2 advanced settings.

Refreshing advanced parameter values in the wizard binding procedure did not work correctly.

Fixed setting favorite positions for some blinds.

The icon for the Door lock changes according to the state of door lock.

Fixed setting user codes on Yale, Kaadas and other doorlocks.**

Fixed preview and tile view in dashboard for thermostats.

Fixed status presentation on Door Locks icons in some cases.

Fixed current override status presentation for thermostats control dialog.

Fixed issue with automatic change of device icon based on selected role for some device types.

Gateway Connection

Fixed issue with special characters in passwords for the slave hubs.

Update visibility for slave hub did not work correctly.

Fixed issue with connecting a new Slave hub that occurred in 5.162 Beta.

Fixed issue with accessing backups on the Slave hub in rare cases.

History

Some duplicated events removed.

Lack of icon for some events from FGT-001.

Nice*

Fixed support for MHouse protocol gates with new hardware revision.

BiDi-Multisensor is temporarily marked as disconnected when resetting some device parameters to default.

Notifications

Redundant intervals removed from the configuration page for event-type notifications.

Other

Minor translation fixes.

Minor UI/UX fixes.

User is logged out from the system after creating a backup.

Issues with saving Sprinkler Schedule.

Plugins

Fixed preview for the Sonos plugin.

Quick Apps

Added QuickApp is placed in the incorrect room in some cases.

Fixed issue with icons handling for some devices types like Weather provider.

Remote users

Fixed access for LUA Scenes for Support and Installer user.

Recovery

Fixed issue with updating the hub from Recovery from 5.140 to 5.153 Beta.

Fixed issue with checking system version when using the Repair option.

Rooms

Fixed issue with setting the default room icon after removing a custom icon from the system.

Cannot remove custom SVG icon in room settings.

Custom room icon is not visible when editing the room settings.

Fixed uploading custom icon for the room by Advanced user.

Scenes

When a new scene is added, the window does not scroll to the newly added element.

Possibility to type too long a name for Simple Scenario, which blocks the possibility to save it.

Lack of some scene icons after system restart in rare cases.

Small UI fixes in Simple Scenarios.

Main Z-Wave devices available in block scenes device selector.

Fixed issue with Scene Activation feature in block scenes.

Swapped triggering the scene on Doorlock state.

Update

Download progress bar visibility depends on the checkbox selection (beta).

Z-Wave

Error 500 in some rare cases during the Z-Wave device reconfiguration process.

Requesting Neighbors update action not always triggers correctly.

Fixed setting the device polling interval manually.

BiDi-Zwave device is added with a wrong system role by default.

Qubino 0-10V Dimmer parameters are being restored to default during inclusion.

Resolved issue with displaying Advanced tab for Door lock device.**

Fixed rare issue with starting the Z-Wave service when controller Node ID is different than 1. 

Solved issue with mesh network reconfiguration not working.

Fixed issue with not hiding automatically console log after finishing adding or removing process.

Zigbee

Device removal procedure fixed.

State of the light in the system is synced with the real light state for Ikea lights.

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.