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 am on 0.8.38.
What do I set in the settings field? I already have polling on 300, I assume this is 300 seconds (5 minutes)?
Still I only get a value once per hour...
@Jon Polling is not needed for the Aeotec Sensore, you have to set parameter 111,4,300 (300 seconds = 5 minutes) AND you have to use USB power!
It is not advisable but it should also be possible to do this on battery powered sensors if you set 111,4,300 and change the Z-Wave Wakeup (Z-Wave ontwaak) to 300 but I haven't tried that so I can't confirm it works.
Also see https://aeotec.freshdesk.com/support/solutions/articles/6000115071-difference-between-usb-and-battery-power-and-recommendations for the difference between USB and battery powered.
Okay, @DaneeDeKruyff so you suggest as follows (in the polling box):
No, no polling needed, the parameter should be added to the Z-Wave Configuratie Data field. The field now has 5,1,2;201,1,205 and should become 5,1,2;201,1,205;111,4,300
I'm sure there's a screenshot of it somewhere in this thread
Polling interval should be 0 (The polling fiels is only there for legacy products)
Or is it simply related to .39?
It is indeed .39 that breaks the triggers and insights of all (or at least most) Z-Wave devices
maybe tomorrow, or at least not before 0.9 comes out.
Tried:
- factory reset of device
- remove device on homey
- this like 3 times already
have you tried to power cycle homey yet?
had a bug as well that solved itself by power cycle
just tried getting it off power for 30 sec. retried, no sigar
well actually, your in bad luck. (sorry, that i only just noticed this)
The only default capability for z-wave devices without an app is On/Off, but the sensor doesn't have an on/off feature.
So you will have to wait for the Aeotec app to be released, shouldn't take too long. (few (working) days)
tested it and multisensor is working perfectly here on usb power put in batteries tomorrow
@emile great work !!
https://github.com/athombv/com.aeotec
only changed reset after motion from 240 to 10 sec
update time to group 1 300 to 30 (testing purposes)
Also set 'Command to send when motion sensor triggered' to Basic, then save, then set it to Sensor Binary Report, and save it again. This is necessary pre-0.9.1, to make sure the motion reports are send correctly. When paired with 0.9.2 it will set these settings automatically.
Let me know if you guys encounter any issues!
no success adding the multisensor
gives this back:
Stack trace:
Error: Cannot find module 'homey-zwavedriver'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/drivers/ZW096/driver.js:4:21)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)