All Activity

Today, the connection to my ZigBee devices magically came back all of a sudden. I wonder how long it will last. Of course, this is on the older firmware version (5.200). With 5.210 installed, I waited over a week hoping that the HC3 would restore the connection. You’re right @MAC71 They added ZigBee support five years ago, and since then, almost no fixes or improvements have been made. Unfortunately, it’s not even possible to replace everything with Z-Wave devices. And even if it were possible, their design and performance leave a lot to be desired (for example, I have great ZigBee motion sensors that have been running on a single watch battery for two years now!). Sometimes, when I’m at friends’ houses, I look jealous at their Home Assistant setups but I know it would take a lot of time to migrate over 100 devices and scenes to Home Assistant.

Hello again and thx tinman, I have done some testing and found the following: accessControlEvent does NOT work as a scene trigger on ZW3 (as you mentioned) centralSceneEvent works fine for both buttons (11 and 12) when parameter 1 = 2 (central scene mode) So for now I can using centralSceneEvent for both ARM (button 11) and DISARM (button 12) without PIN code The only thing I am missing is the PIN security for DISARM, which was possible with accessControlEvent on ZW2. Do you know if Is there any plan to fix accessControlEvent as a scene trigger on ZW3? Or is there any other workaround to use PIN + button for DISARM on ZW3? Thanks!

As a first measure, I did recreate the token - no change for the better!

I also experience the same issue from time to time – the Tedee plugin stops working. Removing and re-adding the plugin fixes the problem, but it would be nice if it worked continuously without requiring any intervention. While quickly searching the Tedee API documentation for the word “expired”, I found some references to token expiration. So perhaps the token expires after some time and the plugin is unable to refresh it properly?

Documentation showing differences on the API side (like parameters) is here: @Smarti as for the logs, yeap - those are mostly cutted out due the fact that in most cases those did not do anything worth mentioning. The errors of any action ( ex. issue with setting the association or the parameter is reported right away with the red toast in the interface).

There is also build-in log level setting in the quickapps: function QuickApp:onInit() self.logLevel = ERROR self:debug("this debug should not be visible in console") self:error("this error should be visible in console") end self.logLevel one of following constants: NONE, ERROR, WARNING, DEBUG, TRACE

Hi, I have enabled remote access now. HC3-00000454 Im not home at the moment but please check if you can resolve the issue without having to go back to ZW2 engine. Br Jimmie

Hi, We'd like to get back to the topic we discussed earlier and take a closer look at it. Would it be possible for you to share the hub with us for analysis? Please also let us know which device (deviceId) we can use for testing. Enable full remote access as well so that we can investigate the issue thoroughly. Thanks, and we'll be waiting for your update. BR

Hi @Brytho I have never had an active reconfigure button on my HC3. Fibaro's version/installation of Zigbee has always been 'Beta' even after all these years. Here in Australia, we don't have the variety of Zwave devices like in Europe so I am a heavy user of Zigbee as well. I have found that a lot of the time when my items drop off the network, like you are seeing, if i put my HC3 into pairing mode for Zigbee and wake up the Zigbee item, it usually will rejoin the network. I THINK the issue for me is when a battery powered device drops that it breaks the mesh connection, leading to further dropouts - then I go through the process as described; I'll be solid again for a long period of time until it happens again. I know it's far from a perfect solution, but we have all been sold down the river on the HC3 and its multi-protocol capabilities or lack there of (marketing material in Aust said Zigbee and 433mhz) It's my opinion that Zigbee will never be a full, stable component of my HC3 set up. so we either need to put up with these workarounds or bite the bullet and rebuild on another platform. just my $0.02c worth

I have an old FGMS001 (firmware 3.3) motion sensor that works perfectly which I use to control my blinds on one side of my house. My sun sensor (from Somfy) stopped working and I thought that I would replace it with another Fibaro motion sensor. But the new one dosn't work as expected (and differently from the old one). It reports lux up to ~15000 but above that it starts to report 0? I thought that the fsensor was broken and got a repalement for. But is does exactly the same?! The new one has frimware 3.4. I have tried the old one besides the new one and the old one reports lux above 15000 while the new one is at zero when there are to much light. Any configuration I can do to help this situation? (I don't think setting 40/42 will help for this and I have tried to alter them but without any improvement)

I noticed today that the Tedee lock plugin no longer works - neither scenes nor direct interaction via device preview. It neither locks nor unlocks anymore. Locking/unlocking directly from the Tedee app works - as well as via the Home Assistant integration. Can you please have a look into that issue? Thanks!

I've tried it this way, and it's working: local QuickApp_trace = QuickApp.trace function QuickApp:trace(val1, ...) if val1 == "onAction: " then return end QuickApp_trace(self, val1, ...) end

I forgot the val1 in hub.trace(QUICKAPP..self.id,val1,...)

This is clearly not a 3rd-party device issue. It is a crash of the HC3 internal Zigbee coordinator. The fact that the "Reconfigure" button is grayed out in your own UI proves that the internal backend process is dead or unresponsive. Please escalate this ticket to the R&D. This is an internal firmware bug, not an external vendor issue. Regards

Thank you very much, of course it works! I can’t believe I didn’t think of such a simple idea. I was sure it was going through some internal hub mechanism, and yet here we are.

Redefine the trace function in your QuickApp: function QuickApp:trace(val1,...) if val1 ~= "onAction: " then hub.trace(QUICKAPP..self.id,...) end end

It is possible to make a slave HC2 and the master is HC2 also. can you please help me how to solve this.

Hi, Unfortunately, we are unable to resolve this issue on our side. This functionality relies on integrations and services provided by third-party vendors, and therefore its operation is outside of our direct control. As a result, we are unable to make changes to it or guarantee its proper functionality. Best regards

After upgrading to ZW engine 3.0, I cannot change param on other device by scene, like color of the ring on Scene Controller, not even able to turn it the backlight on/off from block scene. Only the options enable/disable local protections are shown. At least via LUA scene the parameter setting works, however it is very annoying to find out, how to call the parameters properly. Definitely UX fail.

Currently, all actuators (switches, outlets) are offline. Surprisingly, the sensors have come back online. Unfortunately, the option to reconfigure all devices in the Zigbee settings is disabled (HC3). I have about 30 Zigbee devices. Manually adding everything again is pointless.

I am on 5.210.12 and have been for a few weeks. My Zigbee network is working just about the same as previous version. What issues are you seeing?

However, after a few minutes, Zigbee also stopped working after the downgrade! Probably the same issue as: WHAT DID YOU GUYS DO!?

TRAGEDY! With this new update, you’ve completely broken Zigbee! The power-off workaround—doesn’t work. Soft reset—doesn’t work. Only rolling back to version “5.200.13” helped. On 5.210, Zigbee doesn’t work at all. What a piece of junk you’re releasing!

Hi vitruv, (1) correct, though there might be a range problem (2) correct, if you use the old bridge version (not the Pro one) and the Fibaro plugin.

Here are the screenshots 1 = the one with updated Firmware 3.4 2 & 3 = Firmware 3.3