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.
TedTolboom
About
- Username
- TedTolboom
- Joined
- -
- Visits
- 7,633
- Last Active
- Roles
- Member
Comments
-
@Fire69 No, I'm not able to proof it (yet) Although I observed more crashes / failing motion sensor with an interval of 300 seconds or lower compared to the current 900... Which corresponds to @Ziglar's observations
-
@caseda I would add the link to the Fibaro manuals : http://manuals.fibaro.com/ it holds all manuals but also quite illustrative instruction video's (e.g. manual wake-up / reset of module) And to complement: Aeotec support page: http://aeotec.com/s…
-
@Ziglar Thanx for the feedback. At this moment I'm also running the motion sensor with a Z-wave wakeup interval of 900 (until the issue with data reports has been solved). It enables further testing of my flows to control my lamps in the living room…
-
@caseda your summary is real good. I would suggest to post it as separate discussion topic for easier finding it and that we all contribute to it, ok? Some additions: - "As this is different per device" > "As this is different per device and eve…
-
@ThijsDeJong Thanx for the honest feedback... I'm also just starting to understand the Z-wave devices (with 1 motion sensor and 3 switches) and corresponding difficulties to get what you want... And I was also under the impression that Z-wave is a s…
-
Fully support the feedback of @caseda : Fibaro has a quite extensive knowledge base (including video's on the different actions) explaining the association groups, parameter and recovery actions: check out: http://manuals.fibaro.com/
-
@scocz trying to combine the info you share above and on slack... On slack you indicated that you've reset the sensor... Did you follow the following steps: 1) Settings > Z-wave > Remove Node > 3x press of the B-button 2) reset the Fibaro…
-
@MarcoF I do understand your idea, but considering the state of development of Homey... I don't think setting up a NL section on the forum would contribute a lot. Already now, you see multiple topics where the same topics / discussions / questions …
-
gerbenz said: Place a , after each word That would be working for user-defined sentences (allthough cumbersome), but does not work with build-in responses (e.g. BuienRadar feedback) or external sources (e.g. news headlines / wikipedia)
-
@Bumblez same experience here... yesterday I was (eventhough I tried before) also able to install Better Logic and CountDown, but Kodi and BuienRadar keeps failing.. Even several reboots did not change it from failing to install
-
I'll make the next Github issue #506
-
See github issue #462 should be solved in 0.8.31
-
@caseda Just tried with the following flow: One observation is that the "set configuration card" does not accept 0 as input (for parameter 80 and 89) After testing the flow, the setting page remains empty... I will check after next wakeup…
-
@BasVanDenBosch Same results with my v2.7 sensor and the same parameters. Strange thing is that some parameters are updated correctly (e.g. 80 and 89 with clear visible effect) and above mentioned illumination and temperature parameters do not have…
-
Thanx for the feedback @caseda
-
scocz said: yay! @caseda helped me fix it! thanks @scocz good to hear! What solved it?
-
One reply to many questions... @Ziglar In your original settings (wake-up interval at 7200): - Did you confirm that the settings of the sensor were updated? Nice indication (that's why I use it) is parameter 89 (tamper alarm).. if correctly update…
-
@MarcoF I doubt whether it is stored on the cloud... After a full reset (clear data), the checkbox within settings to accept experimental updates is not ticked. You will have to re-apply for experimental updates. So I guess that with the update to…
-
@JanH See page 10 of the manual: Association allows direct transfer of control commands between devices, is performed without participation of the main controller and requires associated device to be in direct range. With these groups …
-
@JanH check the manual of Fibaro (v3.2) and or their website... Pretty much all settings are explained in more detail. See Fibaro Motion Sensor v3.2 manual @ ;;http://manuals.fibaro.com/motion-sensor/ Note for v2.7 (or below)... use the correspond…
-
jovink said: spoelly said: I have no problems. I can reach my homey without any problems. Are you on the same network connecting to homey? I am currently at work can't connect to homey. From my home it works. Y…
-
Ziglar said: is there a way to decrese the time between the LUX updates ? Fri Apr 22 2016 09:33:54 GMT+0200 (CEST),3513 ±2 hours Fri Apr 22 2016 11:34:05 GMT+0200 (CEST),10703 Wake: 7200 data: 80,1,0;89,1,0;40,2,5;42,2,1800 polling: 0 …
-
After this change, illumination data is also reported in between Z-wave wakeup intervals... * With 300 seconds interval, illumination data every 7200 seconds = Z-wave wakeup interval at 7200 * With 1800 seconds interval, illumination data every …
-
@Ziglar In this flow, you are using the generic alarm (motion sensor) to trigger a flow where the and condition is that the lux value (which is empty) is smaller than 25... Exchange the generic alarm trigger by the "The Luminance changed" card of t…
-
The Bellfire fireplaces do not use IR as remote, but 433Mhz. I think an app needs to be developed for controlling this fireplace. See Mertik Maxitrol Fireplace control
-
@Bumblez which router are you using? Do you have parental controls enabled (e.g. OpenDNS)? If so, disable @Fire69 mentioned today on Slack that the following solution was reported (in Dutch) on Tweakers: fire69 [9:27 PM] @weejewel: have you seen t…
-
By default the Z-wave wakeup interval (in Homey and Fibaro parameters) is 7200 seconds. Normally, it should wake itself up after this interval (and update it's settings). Otherwise, press 3x the B-button with the sensor in close proximity of Homey.…
-
See the support page on the new website: https://www.athom.com/en/support/KB000003/
-
I would propose to introduce / enable this only when the false triggering issue has been solved... otherwise we are adding a (currently quit frequent) "sorry I didn't understand you" in addition or as replacement to the "Oops I couldn't reach the se…
-
Just some feedback on my update interval "issue" Github #464: Yesterday, I changed the ILLUMINATION REPORTS INTERVAL (parameter 42) from 300 to 1800 (based on good results from @jorden) : Z-wave Configuration Data: 80,1,0;89,1,0;40,2,5;42,2,1800 …