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.
Official Z-Wave Aeotec
Comments
I prepared you a zip file(see attachment) with (check for the second time) all driver enable debug "debug: true".
Please try to run the file at the NodeJS console with this command "athom project --run".
For more instruction read this topic and developers.athom.com
While the app is running in the NodeJS console, go to the Homey zone where you want to device to show up.
In the pairing wizard, go to Homey, select Z-Wave, follow the instruction and set your Z-Wave device in pairing mode.
Wait until the magic is finished and if the device you try to pair is supported by this Aeotec app, the device will show up. When the device isn't showing up, your specific device isn't supported by this Aeotec App.
Please let us know the results.
For more detailed info/help on the NodeJs stuff; please contact Athom ( @Robin )
Downloaded the latest master.zip from https://github.com/freemann/com.aeotec
When I ran it in debug mode in Node it crashed with this error:
After deleting the homey-zwavedriver folder and copying the driver from a earlier version of com.aeotec
it ran without errors.
Its something Athom came up with and not my fault.
You need to download the driver and copy it into the node modules folder.
so it looks like my door sensors are not supported.
best way to get in contact with @Robin to solve this?
Hi @Robin do you perhaps know a solution to receive a more frequent update from my sensor (at least for luminance) than only once per hour. Although I have set 300 seconds, see above, it still does not report more than 1 time per hour.
The spec sheet below indicates that there are multisensors that do not support the reporting intervals.
http://www.pepper1.net/zwavedb/device/741
I have the Aeon Multisensor 6, does this support it? It's actually their newest sensor..!
http://www.pepper1.net/zwavedb/device/824
http://www.pepper1.net/zwavedb/device/741
Did you compare the A-B-C versions?
The only thing I'd really like to know in this issue if my multisensor will or won't support more frequent sample rates than only once/hour.
Then Google is probably your best friend .
You can't expect Athom to answer all the answers on "basic" question about device you bought.
Is there a producttype label on the device? Could you post a pic of the label?
[edit]
Also; did you test it with the new Aeotec app?
Hi @MarcoF ; if you read my previous posts you could read that - yes - I installed the new Aeotec app from the appstore - and also I wrote which type number I saw on my multisensor.
I assume it's kind of logical sense to expect that if someone (in this case @Robin) poses a certain feature, that he could expect questions to explain his point a bit more.
I'm trying to help, but without useful info that's very hard.
Also the app supports the feature you ask for, but your sensor isn't doing it, that with Robin's answer makes it very simple.
Again: please test it with the new app.
Here's a photo of the label. I am very curious if you make any conclusion with it... I can't. Also, from Robins answer I cannot derive which sensor does and which doesn't support the frequent sample rate. Can you? If so: please enlight me
So please check the installed aeotec app on your homey is the same version as the current one in the store.
If that's the case, check the parameters. Best it to change them one by one to 301 secs and after each change wake-up the node.
This way you are "sure" the parameter is saved. When this done, wait some time and see what's happens.
The pic is indeed not showing extra info.
I added one of my sensors, motion sensor stayed on -> entered 5,1,2 in RAW parameters -> motion sensor working good*
interval was default at 300 but it didn't report every 5 minutes. Added 111,4,300 to the RAW parameters (thus beeing 5,1,2;111,4,300) and presto an update every 5 minutes.
*motion sensor working as good as implemented currently. The Multi Sensor 6 isn't really supported in the way the sensor is engineered. The sensor exposes a Motion Alarm and a Generic Alarm (and Tamper) The Motion Alarm is send when an actual motion is detected, the Generic alarm starts at the first detection of movement and is cancelled the duration of parameter 4 in seconds after the last motion is detected.
I sure hope that this will be corrected and that the Engineering sheet is Athom's source and not the previously linked pepper1 pages!
Yes
@DaneeDeKruyff ;
Raw seems a proven way, but let's test the UX of the more user-friendly settings part.
Based on the most recent app? And what did you test?
Thanx and your welcome!
Most of the credits go to @JeroenVollenbrock! ;
Athom, as far as I know, still didn't confirmed it as a official bug.
Lets wait on the next big mighty awesome rocksolid update and hopefully it fixes this (probably) small and high impact issue.
still very(!!!) disappointing there wasn't released a hotfix for this, now all app "owners/developers" need to fix there drivers because of this fix and the wrong example/sample code.