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.
Comments
I'm on 0.8.32 and have the current settings:
5,1,2;3,2,10;40,1,1;43,2,10;101,4,241;111,4,600
I have tried 60 seconds as my lowest value (as it's not battery powered).
See my last update in Z-Wave: Fibaro multisensor
With this sensor, there is apparently an offset of ~255x in setting several parameters. Meaning that settings a parameter to a value of 1 second, the actual interval will be 255 seconds.
I did the testing today (so no feedback from Athom), but it would be interesting to get the confirmation that this is a Z-wave generic issue (and not Fibaro specific)..
Just tried setting it to 3, it does not appear to change anything (If it does overnight I'll let you know tomorrow morning).
I don't expect that the sensor went through it's wakeup interval by itself; you're response was too fast for that.
My suggestion: after saving the settings, manually update the sensor and reboot Homey afterwards
it does makes sense that you do not see a difference.
Parameter 43 is defining the threshold based on which illumination reports are being send (and is a 2-byte parameter)... You just set it to 3 (Lux). Assuming that the same factor is applicable for all Z-wave devices; Homey changed the threshold to 3x255 Lux = 765 Lux.
With an indoor positioned sensor, you will not see these light intensity changes....
I would change this one back to defaults.
The parameter to look for is 111:
But this is a 4-byte size parameter and I don't know if the same factor applies for 4-byte size parameters...
You could try a relative should value (e.g. 10) and see what the interval in Insights will be...
(https://forum.athom.com/discussion/comment/21340/#Comment_21340)
I just connected the aeon to the homey, so happy to try some settings - but please chew it out for a noob what goes where (completely )
let me know
ow and currently its constantly triggering the generic alarm - i aimed it at the wall 20min ago... still going nuts
One thing that strikes me as odd is that the pepper1 site and zwave alliance site report different values (i.e. for parameter size).. Anyone knows if Aeotec has their own version of these tables?
If I check the settings on Pepper1, it also shows a 4 byte size for parameter 111.
Can you compare device ID's with this page?
You are right, similar settings as the link you provided. The ID is the same as well.
See Github #464 Homey not able to receive (multi) sensor data, only with polling or wakeup
Short version: It looks like there is a byte conversion error which converts the value of 5 seconds into 83886080 / 84215045 seconds (as send to the sensor)... Which will not give you an additional data point in the next 2 2/3 years..
I think the issue #464 now has sufficient leads to squash this bug...
@Taco confirmed the cause of the issue with 2 and 4 byte (relevant for the Aeotec multisensor) size parameters::
According to the statements made on Slack regarding the release of 0.8.33 on May 6th:
- option to get more frequent updates from sensor (more then 1 an hour)?
- more carts and options?
right?
So Betaalbare Domotica's Gertjan let me return my sensor to have its firmware updated and he would then try to pair it with his own Homey (yes, he luckily had one!). This didn't turn out to work, so now Gertjan sent me a new one (after succesfully trying to pair this one, of course). Woohoo, a working multisensor is coming my way now!
In conclusion:
Props to Gertjan at www.betaalbaredomotica.nl, he deserves some free publicity after all.
I was using the example flows of @BasVanDenBosch on page 1 of this thread, so I wanted to create 2 flows like below. But I encountered 2 issues:
- the first flow can't be saved, due to some unclear error with the Variable name.
- as for the 2nd flow: how do I set my flow in order to have my light switched on?