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.
Closed Official
[App] Fibaro by Athom (v1.5.18)
This discussion has been closed.
Comments
these are my two motion sensor's information found on setting (the same):
Manufacter ID 271
Product Type ID 2048
Product ID 4097
really don't know what does it means..
and for both the node association are:
Group 3: 1
i tried many times to change values (tamper alarm cancelation delay fe) and set them back to the original but seems don't do the job
Product Type ID 2048 = id for a multi sensor normal z-wave
Product ID 4097 = Motion Sensor Z-Wave
keep tamper cancellation delay to 30.
put Tamper operation mode to value 1th, 3rd or 4th mode
save.
put back the Tamper operation mode to 2nd value
wakeup your device, the press save in a short periode of time (within 3 seconds is the best)
now it should give the message "Device settings saved." then it should work properly
The distance between Homey - Dimmer 2 is very short, 15 - 20 cm.
Any ideas?
Can I change the name or can I easily find out what Node ID is related to the Fibaro WP?
on which step does it timeout?
and what are your homey and app version numbers.
@Fire69 amazing, but good to know. I did a reset of the dimmer (hold B button until led is yellow followed by 1 click) the dimmer's led was green after calibration with lamps. The pairing with Homey just will not work. Is there a way to check if it is not the Dimmer 2 itself?
That way if it works you're sure it's properly reset and if it doesn't work you know it's not tge inclusion giving you problems.
When you're that close, the range can't be the problem either.
What firmware version is your dimmer?
it all depends on when my homey gets fixed by @JeroenVollenbrock (or at least, by athom)
already got it implemented in my github repository.
Can't add it to a PR yet because i want to test it first.
So i can't say for sure that it will work for the Double switch.
You can try it but be very careful,
there is some experimental code implemented for the Dimmer 1 (FGD-211) and Dimmer 2 (FGD-212),
so if you have one those 2, it might break the drivers for that.
Please follow the instructions of @Fire69 and let it finish with its calibration (if a lamp is attached it will take a little longer, but at least visible)
after that it should definitely be possible to include it.
or maybe a homey (soft)restart is needed (Settings -> System -> [Reboot])
I followed Fire69 instructions (remove device):
and did an attempt to include the Dimmer 2. That did not work.
Additionally I did a reset of the Dimmer 2 (hold B button until menu mode: yellow followed by a quick B click)
followed by a calibration.
and again did an attempt to include the Dimmer 2. I even try to include it as a Dimmer and as a generic zwave device.
It is tempting to order another Dimmer 2, just to check is my current Dimmer 2 is broken.
try to add a (temporary) load (lamp) to the output, it might need to calibrate something before it can enter into inclusion/exclusion mode, that is also the steps when reading the manual, if it really is the case i will adapt the "learnmode" instructions for this.
Can't test this myself just yet.
if it even works, for some modules it is (was) not fully reliable (maybe it is better now since an update)
but as you mention "never been able to connect to a controller", you have tried it with more controllers?
if so then it's definitely the module that is broken
(the only way to find if it is the module (i guess), is trying to connect it to an other controller)
The next step would be to let homey respond to the "event". For example, would it be possible to change the light or play a sound when the manual switch is used?
I know recent updates to the Homey firmware opened up the way for some improvements. I'm wondering if this is currently in scope.
If you have more devices than just the motion sensor, you had to do it with all those devices.
This makes the FGS223 useless, what is the difference between the FGS-222 and 223 that makes the 222 working and the 223 not ?
internally/technically there is a big difference between the FGS-222 and the FGS-223,
if you are knowledgeable in electronics i can explain.
but also (the reason why it's not having S2) the version type of a Command Class (MultiChannel) it is using has been upgraded vs the FGS-222,
which has not been implemented yet,
it will be in the next homey update (0.10.6) when it's there i will add the S2 again.
Got a question regarding the FGD-212 (Fibaro Dimmer 2). In flows, we can use "Aangezet" as a trigger. But it fires both with pushing the switch on the wall, as well as when another flow switches the light on. This causes some unwanted behaviour for me.
Has this question been asked before, or is there a solution maybe? If not, I'll create an issue in Github, but wanted to ask here first.
that issue is not fixable at the moment, it is the dimmer itself that is sending the "i'm on" signal to the controller, we can't distinguish between these 2 ways of reporting.
if the dimmer 2 finally works with scene activation (currently it won't report the scene id's to homey, bug in the z-wave driver or core) you can use the card "scene, pressed 1x S1" for triggering on only the single click of the S1 button (or S2 of course).
Thanks for your input. Couldn't recall having the issue with my Fibaro Home Center 2, but indeed, I used scene activation there :-)
Have worked around it for now by using a variable, but scene activation support would be awesome.