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
Thanks, I was able to add the device but the device always stays in alarm.
this is what happens (begin situation door open, then door closed, then door open again):
Please check the config of the device and make sure the report type is set to use "binary report".
setting is missing ?
should I run a debug again ?
Your previous debug showed:
[debug] node.CommandClass['COMMAND_CLASS_BASIC'].on('report') arguments: { '0': { value: 1, name: 'BASIC_SET' },We expect the changed parameter to be received by the Node, then moved to the COMMAND_CLASS_SENSOR_BINARY (instead of the COMMAND_CLASS_BASIC) and if so, the debug should show something like:'1': { 'Value (Raw)': <Buffer 00>, Value: 0 },
'2': null }
[debug] node.CommandClass['COMMAND_CLASS_BASIC'].on('report') arguments: { '0': { value: 1, name: 'BASIC_SET' },
'1': { 'Value (Raw)': <Buffer 00>, Value: 0 },
'2': null }
[debug] node.CommandClass['COMMAND_CLASS_BASIC'].on('report') arguments: { '0': { value: 1, name: 'BASIC_SET' },
'1': { 'Value (Raw)': <Buffer ff>, Value: 255 },
'2': null }
[debug] node.CommandClass['COMMAND_CLASS_BASIC'].on('report') arguments: { '0': { value: 1, name: 'BASIC_SET' },
'1': { 'Value (Raw)': <Buffer ff>, Value: 255 },
'2': null }
[debug] node.CommandClass['COMMAND_CLASS_SENSOR_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SENSOR_BINARY_REPORT' }, '1': { 'Sensor Value (Raw)': <Buffer ff>, 'Sensor Value': 'detected an event', 'Sensor Type (Raw)': <Buffer 0c>, 'Sensor Type': 'Motion' }, '2': null }
So run the app in Debug, wait 30secs, move the door/window and post the output of itI don't know what is meant by 'click the action button'. Is that an ordinary 'short' click or is it click-and-hold?
Anyone any idea how to get my multisensor hooked up?
Don't know how the Sensor6 is working with pairing, but the older motion sensor is OK with a short push on the "pair/action button".
Have you tried to remove the device?
This makes sure the device is not connected with another Z-Wave network AND (as far as I known) the settings of the Node/Device are reset.
Go to Homey>Settings>Z-Wave>Remove Device and let me know what the result was
It seems to report it every 1 hour, but this sample rate is too low.
I see something like the update interval value in the sensor settings, but there's a:
- Informatie update interval associatie groep 1
- Informatie update interval associatie groep 2
- Informatie update interval associatie groep 3
How the h*ll are we supposed to make sense of that...?
I thought the whole concept of apps would be make it much easier and noob-friendly to deal with Z-wave devices but why using such vocubalary instead of just making it plain and simple?
Hopefully Athom fixes this issue ASAP.
For now;
Your Homey is probably in "groep 1".
So if i remember well, the default (off-manufacturer) refresh rate was 1 hour. This is still unchangeable due to the bug in the Aeotec app, am I right?
If so, it's indeed to hope that Athom can fix this asap.
In the previous (non-app) era, this interval was also non-editable.
Some more info to Robin's posts;
Its up to the developer of the App to make the App in that way the user knows what to do with the settings.
In the ideal world, the App developer defines the perfect default settings and the end-user just installs the app, pairs the sensor and everything works as expected.
But there always will be users that want the insights to update every 5 instead of 10 mins. And then it should be clear to the end-user which setting (s)he should change.
I really hope Athom this week fixes the default settings bug
Is the doorsensor already working?
it seemed that my zwave network was a little bit busy but it works!
thanks a lot!
I really have no idea!
Z-Wave is still a bit buggy and yesterday Jeroen created this issue;
https://github.com/athombv/com.aeotec/issues/7
So maybe its better to just wait.....
@Jon How is the sensor powered? It needs to be USB powered in order to send information more frequently than the default setting.
Another thing to test, does it work when you enter the needed settings in the RAW settings field (Check my How-To thread for the Multi sensor what parameter,length and setting you need)
The manual says:
The App's code for parameter group 1 says;
{ "id": "241", "label": { "en": "All", "nl": "Alles" } }
This can be the cause of the fact the sensor isn't reporting as expected.....
1+2+32+64+128 = 227
Where did you find that manual @MarcoF?
The engineering sheet shows this (sorry for the page break):
If you calculate this it will be (in reversed order, all bits included) 128+64+32+16+0+0+0+1= 241
241 is the default according to the document:
Pepperbyte shows the same (but it's source is probably the engineering sheet)
http://www.pepper1.net/zwavedb/device/741
https://support.smartthings.com/hc/en-us/article_attachments/205315906/aeotec-z-wave-multisensor-6_manual.pdf
Its the first result when searching on;
"aeotec motion sensor 6 zw100 manual"
Also the parser Issue on Git could be a real killer.
Every time I opened my Zwave.me rollershutter it closes 3 minutes later. There's a parameter which for this "auto close" time and all what I tried; It kept closing.
I was almost certain the Parameter wasn't saved/sent on/to the Node, but couldn't verify.
Yesterday I had a conversation with Jeroen on Slack and he suggested to remove the Parser. After I removed the parser from the Zwave.me driver and set the parameter to "0" the sunscreen automagicly stayed open. This took me about 1,5 week searching, cursing (to Homey and the Node), etc. The most frustrating part was that I excluded it working from my Vera3 and 5min. later it was auto closing on Homey.....
First you need to be very certain if parameters are send correctly AND are saved correctly on the device.
Then you need to be sure which values are expected for these parameters.
I don't own this particular sensor and also I didn't wrote the driver for it.
So if you guys are experiencing problems with this driver; Robin is the guys to spam!
Ah, that looks like the one included with the sensor, Have to check that at home.
I've read your conversation on Slack, it was in the discussion about the settings longer than one byte right? Indeed very frustrating to find out after fighting with not working stuff...
I share your concern about the value's, information can be hard to find sometimes and not all sources show the same data. I Always try to find the engineering sheets for the Aeotec devices, but even those are not always right as there are several revisions around
And instead of using the settings on a device I tend to test it first with entering the Raw Configuration Parameters that way I know exactly what settings are applied (Just like the old days hahaha)
If I understand it right, the Z-Wave driver handles all the (string)numbers/integers as is.
The parser is only need to do magical conversion and also then the Parser is only needed when the Dev hasn't setup the settings rights.
See the ABC/DEF example where ABC = 1 and DEF = 2.
IF the developer adds a dropdown with:
Then he should use the Parser to convert these ABC/DEF strings into integers.
IF the developers adds a dropdown as next, then the parser isn't needed;
and it doesn't matter how big the integer is, the Z-Wave driver can and will handle it.
The parser is only in very exotic situations needed and for now it looks like the Parser is also breaking things.
So;
1. the parser isn't needed
2. the parser is probably breaking things
3. because of point 1 and 2 its preferable to drop the parser
4. try to design the settings in such a way the parser isn't needed