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
Any ideas whats wrong?
Log:
Chart:
I have the impression that LUX threshold is not working properly..
@caseda are you aware if there is a filtering of data entered into insights..
Support the motion sensor is providing every X minutes the LUX data, does Homey save all data points? or only when data points are different
when I have more time in the upcoming weeks I'm going to find out extensively what is going on over longer periods of time, not just what is reported in the log but on core receiving end of homey, see if I can find any common logic in it.
And will see in the meantime if the log file filters or not.
Or @annemarie can give a definitive answer for us if the log file has a filter, and how it filters
During the night, no reports are added to insights (most likely since the value did not change)...
With data nicely showing reports every 5 minutes (300 sec) if LUX value is changed:
v 1.1.1
add support:
FGWPx-102-PLUS
FGD-211 - Scene Activation
FGD-212 - Scene Activation
But cant get a scene working. Disabled dubbelkliking in the menu, but that didnt do the trick neighter.
Anybody got it working? I got pulse switches
I use: Left S1 2x push
that's not a problem it's a feature! oh wait that is someone else's line.
It's just not implemented in the FGK-10x sensors.
for now, it will cause a lot of trouble for people that have it already implemented, so probably not going to be implemented until the more easy re-add is implemented into homey, so that will result in not losing all flows and insights
I don't think you're doing something wrong. It just in't working (yet)
p.s. sorry for my english:)
what homey version are you running?
there has gotten a few bugs into the homey core since version homey firmware 1.0.1 was released if you include a sensor in that version, and athom is already trying to fix it for 2 versions, but without 100% result as of yet, even though it has become little bit better.
So if you are on the stable version (1.0.1), then this is your cause for not responding motion sensor(s)
and your english is fine.! most people on this forum don't have english as their first language, so you are not alone
It is not only Fibaro motion sensors that act up, also a Aeotec sensor seemed a bit more unstable.
Yesterday I did a PTP and it seems a bit more stable, but that could be a temporary effect.
I made a flow with 2 actions to set different dim levels after each other. First one to set 10% and the second one triggered 2sec later to set 60% but this does not work. The lights twinkle for a sec when the second action gets triggered but the dim level does not increase to the 60%.
Any advice is welcome
Still waiting for the dimmer capability rewrite for this
I added the ds18b20 temperature sensor to the Fibaro zwave+ device fgk-101 ZW5.
I installed the Fibaro app and paired the sensor. I am able to see the battery status and also if I move the magnet away and back from the sensor.
However I do not get any temperatire readings.
In the PC app I do see an Temperature icon, but in the insights overview I do not see an optio to show the temperature logging.
Is there anything I need to change in the settings after pairing the FGK-101 sensor.
I already tried to unpair the sensor, uninstall the app, rebooted and ptp Homey and install the Fibaro app and paired the sensor again.
I am using Homey firmware: 103 and Fibaro app: version 1.1.1