I have several z-wave devices from different manufacturers and I don't understand why in some I don't see any parameters to configure them.
I have tried to send them manually and it says "index outside the limits of the matrix"
I am doing something wrong?
Two of the devices that happen to them are Fibaro RGBW Controller and Qubino Flush RGBW Dimmer.
I would greatly appreciate a solution, at least I can send the parameters manually.
I'm running bOS 4.7 on Jigsaw KNX with a Z-Stick.
I have many Fibaro modules in my set-up, including a Fibaro fgd-211 dimmer, and a Fibaro fgs-221 2 relays switch.
Group 2 of the dimmer is connected to a second switch, and can be used to control other devices thanks to group association.
I want dimmer Group 2 to control group 1 of the fgs-221.
When I set-up the association, I did find the fgs-221 node, but I didn't find each of the relays. So, I associated dimmer group 2 to fgs-221 node. And it did work : I can now control relay 1 with dimmer switch 2.
However, I'm now having the following error message on bOS when I click on Associations : "La référence d'objet n'est pas définie à une instance d'un objet" which would translate approximatively as "Object reference not set to an instance of an object". And I cannot view / modify associations anymore.
I upgraded to
Since this upgrade, the Associations screen is not working anymore : when displayed, it's a completely blank screen : the existing associations are not displayed, and the usual buttons and tabs to manage associations even don't appear. It's a blank screen with only a border.
This is a big problem as I cannot handle associations anymore. Any workaround about this ? Or quick fix ?
I have a YALE lock YDM3168 connected to bOS Colibri through FIBARO HC3. I have made some programs and I am able to control it and to read its position. The problem is that from time to time the HC3 seems to lose its connection with COLIBRI even if they are in the same LAN all the time and there are no any interruptions in the network. I don't know if the problem is caused by COLIBRI or by HC3 itself. By disabling and enabling back the FIBARO gateway in the configurator it comes back online.
Unfortunately I cannot yet connect the door lock directly to COLIBRI because of the Z-WAVE driver limitations so I am looking for a possibility to revive the connection between HC3 and COLIBRI from time to time. Something like keep alive. Anyone has any ideas?
I am having problems adding correctly a qubino Flush 1 relay module(ZMNHAD3) it can be added to BOS with no problem, but i can only control the relay and view watts reading. but it will not show binary sensors status and will not show any temperature data ( i have the temperature Sensor already and works find in other controller). also i am having problem to add the parameters manually, everytime i would like to set the parameter it display "index outside the limits of the matrix".
I'm trying to add Aeotec Trisensor to my Z Wave network but the device is not visible in bOS Configurator.
The sensor is paired with my Aeotec Stick Gen 5 but un-visible in the Comfortclick.
Any idea on how to fix it?
So i updated my home bOS to the 4.6.17 version, now i cant seem to get my fibaro 2x1,5KWh relay to switch. I get an error the "Value cannot be null. Parameter name: collection". So i added the parameters again manually, but I still get the same error there are no parameters starting with 0 . Fibaro smart plugs are working though.
I was playing around with Fibaro again, because someone had this great idea that we will make a new visualisation in bOS for all of them, a total of 58 apartments.
Then I noticed that when I added the gateway, bOS found relays and thermostats, but it didn't find any universal binary sensor FGBS-321. As the doorbell still works fine with fibaro i dont think its fibaros fault that its not displayed in bOS.
I had it set up as a doorbell input. Then it sent the signal to fibaro app and acted like a digital doorbell.
Has anyone else noticed this, is there a known fix for it? Do i need to manually include them again?
Customer support service by UserEcho