thank you for help

regards lahoucine

Please login or register to see this attachment.

Hello community!  

ZigBee no longer works since this update!! 😔  

other people having the same problem?

I Cannot fall back to a prior firmware due to a lot of changes and clean ups I've done in the new 5.171 and only discovered the problems later on.

I Do not want that clean up to be removed so now I'm stuck on this broken release. It's been almost 4 months now, is there any planning or release date scheduled for a follow up release?

In addition, unable to change hours/days/weeks/months. It's just stuck on current date.

Works fine on previous version.

Please login or register to see this spoiler.

Previous version - 5.170.16

Please login or register to see this spoiler.

Hopefully will be fixed in next release.

Previously I was getting this view;

Please login or register to see this image.

but in edit mode, all labels are still present and correctly defined:

To go back to the previous Labels view, I had to suppress in editor all thes labesl and recreate them all with the same ID and decription.

Note that only after deleting the first Label and recreating it, Fibaro is showing a Warning message that there is a duplicated Label with same ID; Accepting this is making this label to be visible again.

Is there a better way to recover Labels and Select buttons?

I am using fibaro for almost 5 years and I am on the brink to give up. I have 180 devices and around 200 scenes. The hardware looks to handle this

I make updates praying that at last this time everything will work properly. 

My experience so far after updates, in case they might work properly:

- need to exclude include some devices, afterwords checking all scenes

- losing connections constantly with devices even the nearest ones

- Not possible to configure parameters for example auto off delay in smart implant....looks configured but it stays ON

- constantly lagging and very slow reactions

- need for restart one or two times per day

- 5 or 6 attempts to include fibaro devices in secure mode, adding/removing freezing very often

- smart implant with humidity sensor freezes the humidity readings. After power the implant off and on again working 1 day and than the same

- many many other issues like not logical battery drainage of some door/window sensors, walli switches being OFF, but seen as ON into the web interface

I remember ONLY ONCE an update working properly around 2 years ago and I have the following question:

- IS IT POSSIBLE TO MAKE ONE UPDATE WORKING PROPERLY AND DO NOT TOUCH IT ANY MORE?

I am desperate as I have systems that do not have possibility to control manually and I think that I should replace fibaro after quite big investment in fibaro.... 

Thank you for your attention,

Regards

Boris

When trying to activate device from Alexa, HC3 is losing internet connection for a sec.

Interesting that devices connected to HC2 are working fine.

Usually automatic logout works the way if user does not interact with GUI home page for some certain time then automatic logout is preformed and login page should appear in browser.

Unfortunately this is not the case with Fibaro HC3(L), Yubii firmware.

I noticed if I was not interacting with GUI home page for some time, automatic logout is preformed, but home page remain in browser and usually show wrong statuses of the installed devices. In that case, I can still interact with GUI, scroll, filter, but when Settings is clicked then login page appear.

Even worst is that in many cases automatic logout is preformed even I was constantly busy clicking around my QAs and editing them. It happened several times that I was not able to save QA after correcting code, but after refreshing page then login page appear asking me to login to my HC3 to continue work.

It is not very often, but it happens enough times to start annoying me

BTW - this appeared at least several versions before this last beta. Since nobody else reported it till now, I guess that other users do not work that long as me, or they are regularly  logging out, while I like to stay logged in for long time

After updating my HC3 to the latest beta I noticed that when I open console in new browser tab then slider is positioned on the oldest debug line and it is not automatically scrolling as new debug lines are added.

It is not problem in my Firefox since when I open console for my Yubii home which is still on version 5.163 then console is properly scrolling as new debug lines are added.

Can you please check with your dream team to correct this since it is important during making of new QA devices and scenes? Thank you!

is reconfiguring z-wave mesh network working for you?

If I select entire network and then I press reconfigure I get a warning but then, in the console, I didn't see any activities. In the past releases I can see all node asking for neighborhood list.

Raffaele

A restart and re-configuring my meters did not solve it.

Please login or register to see this attachment.

How can I clean up this list?

Please login or register to see this attachment.

the notification settings seems doesn't work on this beta.

I have this device that continuously send notification about battery despite notification setting that is set to once a week.

Please login or register to see this attachment.

Please login or register to see this attachment.

Raffaele

Please login or register to see this attachment.

I have an old QA that work flawless since last update.  Here the error of the crash:

[02.01.2025] [22:42:01] [ERROR] [QUICKAPP512]: QuickApp crashed[02.01.2025] [22:42:01] [ERROR] [QUICKAPP512]: Unknown error occurred: LuaEnvironment: /opt/toolchains/aarch64-buildroot-linux-gnu_sdk-buildroot/aarch64-buildroot-linux-gnu/sysroot/usmqtt/endpoint.hpp:2219: void mqtt::endpoint::async_publish(mqtt::endpoint::packet_id_t, std::string, std::string, mqtt::publish_options, mqtt::endpoint::async_handler_t) [with Mutex = std::mutex; LockGuard = std::lock_guard; long unsigned int PacketIdBytes = 2; mqtt::endpoint::packet_id_t = short unsigned int; std::string = std::__cxx11::basic_string; mqtt::endpoint::async_handler_t = std::function]: Assertion `(pubopts.get_qos() == qos::at_most_once && packet_id == 0) || (pubopts.get_qos() != qos::at_most_once && packet_id != 0)' failed.

the QA is this one by the way:

Any guess?

Please login or register to see this attachment.

New Beta

Please login or register to see this attachment.

Old firmware Fibaro

Please login or register to see this attachment.

After updating my Fibaro system to version 5.171.13 (beta), I noticed that the updateView function in QuickApp no longer works correctly. Below are the details of the issue:

1. I create a new label in the QuickApp interface, assigning it an ID, e.g., label_ID_0.
2. In the QuickApp code, I use the updateView function to update the label's text, e.g.:

   Please login or register to see this code.

3. In the logs, I see that updateView is being called correctly:[DEBUG] Text updated: New text

   Please login or register to see this code.

4. However, the text in the QuickApp interface (user view) does not update. This issue occurs with both existing and newly created QuickApps.

What I Have Tested:

• I created a simple QuickApp with the following test code:

  Please login or register to see this code.

• Although the code runs without errors (as confirmed in the logs), the text in the QuickApp interface does not change.

• I also tried manually editing the label in the QuickApp interface and reassigning its ID, but this did not solve the issue.

• The problem affects all QuickApps in my system.

Assumption:

It seems that theupdateView function stopped working properly after updating the system to version 5.171.13 (beta). Before the update, the view was being updated correctly.

System Details:

• Hub Model: Home Center 3
• Software Version: 5.171.13 (beta)
• QuickApp Type: Roller Shade integrated with Zigbee2MQTT
• Additional Notes: The issue affects all QuickApps in my system and started occurring after the 5.171.13 beta update.

Request:

Please investigate this issue. If it is a system bug, could you provide an estimated fix date? If additional configuration or code changes are required on my side, I would appreciate detailed instructions.

Thank you in advance for your assistance!

Please login or register to see this image.

Now that I have upgraded my HC3 with 5.171.15 beta version, I had to reconfigure one of them and now the icon has change to:

which seems to be a SVG type.

 I have not found a way to change this icon to the previous one.

Any one knows how to get back to the previous icon which is a png type

The above icons are only shown in the PC web view so no issue in mobile applications are the are not displayed at all but I will ahve preferd to ba able to change the icon as for aother device type.

[08.12.2024] [11:35:36] [ERROR] [SCENE860]: stack index 1, expected number, received number: not a numeric type that fits exactly an integer (number maybe has significant decimals) (bad argument into 'int(unsigned int, const sol::basic_protected_function, false, sol::basic_reference >&)')

Is this a bug in the update?

In one of my scenes, I use a table of devices to switch off the lights by calling fibaro.call(devices, 'turnOff'). This worked fine before the updates. However, after the updates, running the scene now results in the error: "String expected, got table." or something like that.

This is puzzling, as the call uses a number, string or table.

To work around this issue, I now loop through the table and send multiple fibaro.call commands, but this is not ideal.

Please login or register to see this code.

The workaround is simple, but not ideal...

Please login or register to see this code.

What exactly is happening with the updates? Looks like there are more added issues than the fixes.