Hi
I’m trying to add a Fibaro HK (not the standard Z-Wave) leak sensor to HomeyPro. The app has the option of adding two Fibaro Leak Sensors: one unmarked and one marked as the Z-Wave model. I tried the unmarked with no luck and I’m wondering if there should be a HK model coming soon to the Fibaro app in HomeyPro or if I should focus on solving connectivity issues locally?
Hi Ceasar,
welcome to the Homey Community Forum.
HK means “Works with Apple HomeKit”, but I guess you know what it means.
Homey Pro doesn’t support Apple HomeKit devices and I guess it will never do.
There are workarounds, such as connecting HK devices via Home Assistant and importing the devices/their properties via a Homey Home Assistant App. But that may not be what you want.
In the future, you should better check the Homey App Store and here in the forum to see which devices are currently supported by Homey Pro before you buy a device.
I’m also a bit confused, I’ll take this opportunity to ask if it also works with RS2…I read the whole thread but I didn’t understand if I should use raw commands or if it can be managed with the slide like the photo you posted, thanks
Perhaps there’s a way to do it then, by sending custom commands?
I don’t know if that is possible.
@Caseda, do you know if it’s possible to use windowcoverings_set via Z-Wave raw command when windowcoverings_state is implemented in the App?
Btw, for the new Fibaro Roller Shutter 4 it seems that both functions are available.
How is that possible? A mistake? 
@DirkG @Caseda I have the roller shutter 4, but I only see “Set the position” and “Set tilt position”. No “state”.
I’m fine with using custom commands, if that’s an option, but I can’t figure out how from the RS4 manual 
If the device is included unsecure then it is possible with raw commands, if it is included secure then it’s not possible. (You can see the current security state in the devices settings) and you’ll have to reinclude it unsecure.
Only possible with Homey Pro though (any version), not Homey (cloud) with bridge.
If it is unsecure then let me look for the correct values when I have some time Friday or Saturday.
I haven’t tried including it as insecure, but I’m happy to do so if possible, as the blinds are absolutely not security feature.
I do use a Homey Pro, yes.
Haven’t seen an example of this command class being used anywhere for ternary functions, so it is a bit of a guess work (older Fibaro roller shutters used a different command class, not supported by the roller shutter 4).
But these commands should work, I have not tested them as I don’t have any roller shutters 4, but in theorie these should work:
Uncalibrated:
NODE_ID, 0x6A, 0x06, 0x00, 0x0C, 0x00NODE_ID, 0x6A, 0x06, 0x40, 0x0C, 0x00NODE_ID, 0x6A, 0x07, 0x0CNODE_ID, 0x6A, 0x06, 0x00, 0x16, 0x00NODE_ID, 0x6A, 0x06, 0x40, 0x16, 0x00NODE_ID, 0x6A, 0x07, 0x16Calibrated:
NODE_ID, 0x6A, 0x06, 0x00, 0x0D, 0x00NODE_ID, 0x6A, 0x06, 0x40, 0x0D, 0x00NODE_ID, 0x6A, 0x07, 0x0DNODE_ID, 0x6A, 0x06, 0x00, 0x17, 0x00NODE_ID, 0x6A, 0x06, 0x40, 0x17, 0x00NODE_ID, 0x6A, 0x07, 0x17It is possible that the direction might be inverted, so using down, it will go up.
Looking at the app code currently implemented for the roller shutter 4, then it will have ternary only if the roller shutter isn’t calibrated (as percentage control isn’t possible then).
but they remove it and add the percentage control as soon as it is calibrated 
.
Someone must have had some extra time left implementing all that.
Btw, if someone would be looking for FGR-224 Roller shutter (as I got another FGR-223 dead - Pulse blue…),
this is how it looks like on Homey.
Also it does NOT report actual power, just energy consumed, which is a bummer - eg. was using Power to monitor that the motors are alright, not got stuck the blinds etc. Not really innovative from Fibaro ;-( Now I can watch for trigger without knowing threshold but virtual devices I used so far can’t be used. Obviously they somehow monitor power and current but for some reason do not share it out.
Also seems they actively works on firmware, so as you know, you can’t update via Homey nor any other brand, you might not get the fixes / new functionalities.
How is the FGR-224 holding up for you?
Im sad to say another one of my roller shutter 3’s just died today, i posted some time ago on this thread with the same problem. Pulsating blue, approx. 5 sec on 5 sec off. I still don’t know what the problem exactly is, or what causes it. The unit is on its way to be replaced by the webshop who provided them; still its a hassle to keep replacing the units. Does anyone have some info on why this keeps happening?
Seems to be software issue, just it’s unclear if it’s on Fibaro or Homey side (I believe programmatically it shall not be possible to lock down any other ZWAVE component/chip and when it is, there is something wrong on both sides. 1st it should not happen, 2nd when it happens (eg. trigger occurs), it shall not lock down the chip).
So far no issues, I just miss the power metering functionality. Also the setup is slightly different but it’s the way forward (in case of Fibaro). Just beware it’s actively being developed so new functionalities will be added via FW upgrades…
Btw contact also Athom with your problem because there are not enough reports from users. Seems I’m the only one reporting any problems like that.
I’ll contact Fibaro and Athom about the problem. Thanks for your response, i hope the FGR-224 won’t experience the same failure.
It’s just a weird issue with the RS3, for example i have a lot of fibaro dimmer 2’s installed which dont have this issue, its just the RS3’s that are giving me problems.
Hope it can be solved.
Same for me, also have some other devices from Fibaro and issues I got only with RS3 … that’s why it’s so hard to solve this.
I have a Fibaro Door Window Sensor FGK-10X. I would like to connect the extra IN-port to a momentary switch. I cannot find this function in the Fibaro Homey app. How do I solve this?
Don’t think there is an extra input, it seems that either the input connection or the magnet is detected.
I have a Walli roller shutter and I want to control it with a Walli controller. I can’t do it, I don’t know how to put the Walli controller in blind mode and I’ve read that you have to put the Walli Roller in group 6 inside the Walli controller with the node.subdevice but I can only find the Walli Roller node in its advanced settings. Can you help me configure it from the beginning?
Currently I can only program one scene on each button on the Walli controller but it doesn’t work the same as my roller shutter. The top button opens the shutter, the bottom button lowers it and if I press one while it is moving, the shutter pauses.
I’m new to Homey and home automation. Thank you very much
Hi All, Why not same the Fibaro rollershutter and Fibaro Walli rollershutter device? Walli looks like a basic dimmable light, no direction control, no stop control. Can i configure the walli device to looks like not walli?
thx
Hi Christian and welcome!
I don’t understand exactly what you want to do. Do you want to connect the Walli Controller to the Walli RollerShutter via association? And which functions exactly should be controlled?
Here are two screenshots of the manual which settings has to be changed:
This means that you have to enter the NodeID of the Walli RollerShutter in association group 6 (for roller blinds) or 6 and 7 (for venetian blinds) in the advanced settings of the Walli Controller.
You must also set parameter 20 to 4, 5 or 6. However, as the parameter 20 is not available in the advanced settings of the Walli Controller, this parameter must be set via Z-Wave raw configuration.
But it’s possible to do it in the advanced settings of the WC. In the menu Z-Wave raw configuration parameter (hope this is the correct translation) you must enter the following value:
ID = 20 (ID of the parameter to be changed, in this case Operation Mode) [*1]
Size = 1
Value = 4 (RollerShutter Controller) or 5 (RollerShutter Step-By-Step Controller) or 6 (Venetian blinds Step-By-Step Controller)
Complete value = 20,1,5 [*1]
[*1 corrected]
If you are using battery mode, the WC must be woken up before saving the Z-Wave raw configuration values:
