This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
5th Generation Fibaro Multisensor (v3.2, Z-wave plus)
Hello guys,
The 0.8.30 firmware has fixed the pairing issue of the v3.2 Fibaro sensors . However not all of them can communicate with homey after pairing/reset/restart/data parameters/wake up. Some people has managed to make it work but others using the same settings can`t make it work. I have exchanged couple of emails with Stefan who confirmed that they know about the issue, the new chip uses secure communication. I thought it would be kind and helpful to share it:
The 0.8.30 firmware has fixed the pairing issue of the v3.2 Fibaro sensors . However not all of them can communicate with homey after pairing/reset/restart/data parameters/wake up. Some people has managed to make it work but others using the same settings can`t make it work. I have exchanged couple of emails with Stefan who confirmed that they know about the issue, the new chip uses secure communication. I thought it would be kind and helpful to share it:
So don`t have to wait long for the official solution, but of course you can keep trying if you wish.I just got word from our Z-Wave engineer that this is a known problem on our side. To make the sensor work...
1) remove the sensor from Homey
2) wait until your firmware version is > .30 (we are releasing an update soon)
3) add the sensor to the network again
4) done - you don't have to set associations no more.
Comments
As already mentioned in other corners of this Forum I could add the Fibaro Multi v3.2 with Homey 0.8.30.
The diffferent sensors are working for me for about a week now.
Being honest, there have been some complications, but trial and error with the data parameters and, more effective, with the wake up interval was quite effective.
Maybe relevant, but I am not able to check that, is that I did NOT check the securebutton. It seems to be that unchecking after checking is not possible without a complete removal of the device.
It is not possible to add firmware v3.2 to an v2.5 - v2.8 sensor.
v3.2 is Z-Wave plus only, which is a new (and thus completely different) chip inside the sensor.
And i guess you are indeed familiar enough with the parameters,
because you can active/deactivate the secure setting Only with the B-Button, and not parameters.
Hmm, i guess i misread it somewhere..
As it seems you can not take off the secure tick with the B-Button..
As in, you can not take off the secure completely.
There is, however, a Parameter for them
Parameter 18: Associations in Z-Wave network Security Mode
Values:
0 - off
1 - Group 2 Secure
2 - Group 3 Secure
4 - Group 4 Secure
8 - Group 5 Secure
Values not stated in the manual:
3 - Group 2&3 Secure
5 - Group 2&4 Secure
6 - Group 3&4 Secure
7 - Group 2&3&4 Secure
9 - Group 2&5 Secure
10 - Group 3&5 Secure
11 - Group 4&5 Secure
12 - Group 2&3&5 Secure
13 - Group 2&4&5 Secure
14 - Group 3&4&5 Secure
15 - Group 2&3&4&5 Secure
(13 and 14 could be switched)
Not necessarily, Group 1 will always be Secure in the Secured mode, even when parameter 18 = 0
Sorry, i forgot to add that to the parameter 18 explanation.
Just a fast learner and i find it easy to put 1 and 1 together.
But i do agree with you that until homey their Z-Wave firmware has been more matured.
keep it as simpel as possible with Z-Wave.
It should be possible when you are adding it as a device.
(so you need to delete it first, reset the sensor and then while adding there should be an option.)
You are not able to unchecked it afterwards.
This is with every controller (for security reasons of course)
I am not fully sure though.. I have not seen the add pop-up for the 3.2 version
Two observations:
- With the v3.2 sensor you do not get a dialog to add secure or non-secure (not able to change afterwards)
- With the v3.2 sensor you also do not get a dialog to set the "report to association group" group number
For the latter, this is the only way to make sure that the sensor reports are send to the right main controller.
Adding it later on (via settings) is still buggy... this might explain the issues with the inclusion and data reporting of the v3.2 sensor
I would suggest to also add this to you Github issue #515
The notification command class is complete for the multisensor on version 0.8.31.
I had a second part of this video where I have showed that the settings are not sent to the sensor as there is no communication so does not matter what you set at #18 parameter (eventually I cut that out from the video because it was too long)
@Taco Thank you so much for confirming this.
It was not because of problems with the parameters not being send by/to homey, it is because all sensor's send their lux etc via notification protocol to homey, instead of the already implemented Binary.!?
Could you confirm this @Taco ?
So first try: No security option but the issue was the same: Homey was not receiving values, sensor not receiving settings.
2nd try: Security option selected by default (and beyond this point it was always selected a grayed out). However homey was receiving values. Alerts were cancelled in due time. Had some figures in the insight, though not everything. So I have restarted homey. After that no response.
3rd, 4th, 5th, ......Nth try. Various issues every time:
Homey has been been restarted after every un-pair, Z-wave network reset. Sensor was also reseted, battery removed. The distance between the Homey and sensor is still the same. And I have 3 sensors, so it is not a product fault.
So what is it? Is it a conspiracy or a solar flare?
The ambulance is here.
I'm asking because I want to buy one but only if Homey is developed so far it supports the Fibaro sensor..
I hope the complete Z-wave rewrite will sort the range issue.
Yesterday I received my Fibaro sensor with Z-Wave+. It's working.
Only difference is that I don't see the 'Generic Alarm' and 'Battery' options. Any idea why?
My Z-wave configuration;