Aeotec Multisensor 6 Tips & Tricks
Moderator: leecollings
Aeotec Multisensor 6 Tips & Tricks
Hello all Aeotec Multisensor 6 users
I want to collect some info to help us with this device.
Could you help me? I will update this post with the new info.
GUIDE (with params): http://www.benext.eu/static/manual/aeot ... W100-C.pdf
some questions:
- Enable polling with power supply? yes/no
- Enable polling with batteries? yes/no
- enable polling vs awake
some tips & tricks
I want to collect some info to help us with this device.
Could you help me? I will update this post with the new info.
GUIDE (with params): http://www.benext.eu/static/manual/aeot ... W100-C.pdf
some questions:
- Enable polling with power supply? yes/no
- Enable polling with batteries? yes/no
- enable polling vs awake
some tips & tricks
- gizmocuz
- Posts: 2352
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Maybe state your issue with this device ?
Quality outlives Quantity!
Re: Aeotec Multisensor 6 Tips & Tricks
I'm receiving from mi aeotec sensors a lot of logs messages like this: ERROR: Dropping command, expected response not received after 1 attempt(s)
Now my sensors (2) die randomly
I'm plugged both in USB and works perfectly around 2 weeks
I don't know how to configure It, so I created this post to help all newbies like me
Now my sensors (2) die randomly
I'm plugged both in USB and works perfectly around 2 weeks
I don't know how to configure It, so I created this post to help all newbies like me
Re: Aeotec Multisensor 6 Tips & Tricks
Nobody has this device? I read old post with some confs, but I think that we need an updated post.
Please post your sensor config
Please post your sensor config
-
- Posts: 18
- Joined: Wednesday 04 March 2015 20:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
I'm using this particular sensor, USB-powered. All sensors are working fine so far, except for the calibration through Zwave. Got it working from Sept 30th without a flaw.
First of all: try the latest beta updates, that partly did the trick for me with the errors.
Second: did you include the multisensor through Domoticz of through some Z-stick device? Including through Domoticz gives ye all the parameters to change. If you included wrongly, make sure you exclude it before including again.
Third: my config:
First of all: try the latest beta updates, that partly did the trick for me with the errors.
Second: did you include the multisensor through Domoticz of through some Z-stick device? Including through Domoticz gives ye all the parameters to change. If you included wrongly, make sure you exclude it before including again.
Third: my config:
-
- Posts: 18
- Joined: Wednesday 04 March 2015 20:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
And the last part:
Good luck!-
- Posts: 18
- Joined: Wednesday 04 March 2015 20:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
And after an update of Domoticz: try rebooting, twice if necessary. Sometimes the first time won't work for me, but after the second reboot all of my zwave items are recognized and up and running.
-
- Posts: 56
- Joined: Wednesday 24 December 2014 16:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
I just bought this sensor. I noticed it reports temp en humidity in one sensor in domoticz.. Is there a way to seperate them?
-
- Posts: 18
- Joined: Wednesday 04 March 2015 20:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Not as far as I know.
Re: Aeotec Multisensor 6 Tips & Tricks
thx Gettingthere, I will try and update the post.
Re: Aeotec Multisensor 6 Tips & Tricks
Gettinthere I'm receiving a lot of logs messages like these ones:Gettingthere wrote:Not as far as I know.
Code: Select all
, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 11:58:33.802 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:04:56.204 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:05:17.646 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:05:32.270 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:05:42.271 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:06:49.576 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:09:47.952 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:10:24.819 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2015-11-24 12:10:25.781 Error, Node002, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Have you got the same problem?
-
- Posts: 8
- Joined: Wednesday 25 November 2015 18:24
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Great topic! I am having some issues with this sensor as well. Attached you see its showing 4 unknown devices. I am missing my motion sensor and vibration sensor. This is strange cause I see 4 unknown devices and only 2 sensors missing. How do I know which is which?
Thanks in advance!
Thanks in advance!
- Attachments
-
- 2015-11-25_1825.png (69.86 KiB) Viewed 11956 times
-
- Posts: 18
- Joined: Wednesday 04 March 2015 20:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
@Zoviel:
I had this for some time, especially after not rebooting for too long. I don't see it anymore though, at least not any different than in the screenshot shown below. I strongly suggest that, if you didn't do that yet, you put your settings to beta updates (top right 'Setup' - 'Settings' - tab 'System' - Software updates release channel 'beta'), than update to the latest beta version.
If you're already running the latest version, I'd suggest you reboot Domoticz (top right 'Setup' - 'More options' - 'Restart system'). At your first time, it might fail to recognize all Zwave nodes. When you try again, you will probably have more luck. Works for me all the time: as you can see in my log below, my sensors are running fine. My timeout notifications are always only temporarily: node 10 is my Aeon 1.
@mvd87:
It's confusing, agreed. With a little help, I figured it out... I think.
When I'm looking at my own ID's, yours should be:
0000200: Motion
0000233: Alarm type
0000232: Alarm level
0000235: Burglar
Supposedly (heard this from Gizmocuz sometime ago) only temp+humidity, lux and UV are numeric sensors, giving a numeric value. You found those already (UV is working well in broad daylight, but not inside your house). The others (motion and vibration) only turn on or off. Compared with my Multisensor 5, the 0000200 must be motion. But... vibration is supposedly given by the Burglar sensor (on / off). I was disapointed by that as I hoped to be able to notice vibrations, but it doesn't work that way.
The other 2 sensors (Alarm type and Alarm level) are also to be found on the Multisensor 5. They don't do a lot for me, maybe Gizmocuz could explain. I read before that alarm type has something to do with the type of signal that triggers the multisensor in sending its signal (dunno how), and the level with the level of activation. But these 2 are very obscure for my, and I don't use 'em. You will find though, that your burglar is mostly triggered when your motion is triggered. I didn't get much extra from this one yet. But... the Lux-sensor is alot better than the one on the Multisensor 5. I think you got yourself a great sensor, and I hope it all works out the way it does for me since quite some time with both sensors.
I had this for some time, especially after not rebooting for too long. I don't see it anymore though, at least not any different than in the screenshot shown below. I strongly suggest that, if you didn't do that yet, you put your settings to beta updates (top right 'Setup' - 'Settings' - tab 'System' - Software updates release channel 'beta'), than update to the latest beta version.
If you're already running the latest version, I'd suggest you reboot Domoticz (top right 'Setup' - 'More options' - 'Restart system'). At your first time, it might fail to recognize all Zwave nodes. When you try again, you will probably have more luck. Works for me all the time: as you can see in my log below, my sensors are running fine. My timeout notifications are always only temporarily: node 10 is my Aeon 1.
@mvd87:
It's confusing, agreed. With a little help, I figured it out... I think.
When I'm looking at my own ID's, yours should be:
0000200: Motion
0000233: Alarm type
0000232: Alarm level
0000235: Burglar
Supposedly (heard this from Gizmocuz sometime ago) only temp+humidity, lux and UV are numeric sensors, giving a numeric value. You found those already (UV is working well in broad daylight, but not inside your house). The others (motion and vibration) only turn on or off. Compared with my Multisensor 5, the 0000200 must be motion. But... vibration is supposedly given by the Burglar sensor (on / off). I was disapointed by that as I hoped to be able to notice vibrations, but it doesn't work that way.
The other 2 sensors (Alarm type and Alarm level) are also to be found on the Multisensor 5. They don't do a lot for me, maybe Gizmocuz could explain. I read before that alarm type has something to do with the type of signal that triggers the multisensor in sending its signal (dunno how), and the level with the level of activation. But these 2 are very obscure for my, and I don't use 'em. You will find though, that your burglar is mostly triggered when your motion is triggered. I didn't get much extra from this one yet. But... the Lux-sensor is alot better than the one on the Multisensor 5. I think you got yourself a great sensor, and I hope it all works out the way it does for me since quite some time with both sensors.
-
- Posts: 8
- Joined: Wednesday 25 November 2015 18:24
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
@gettingthere
Thanks for your quick reply and elaborate explanation. This is very useful stuff for a newbie like myself. I renamed the devices as you specified and I'm testing the response. I indeed noticed that the motion and burglar pretty much fire off at the same time and with the same condition. Would be very interested in knowing what the underlying difference in logic is. Sames goes for the alarm level and alarm type. Will disable those for now but if gizmocus or anyone else can share any more info on that I'd love to hear it.
Will keep a close eye on this thread for any updates and hope to quickly get familair enough with the sensor and domoticz to share my knowledge.
Thanks for your quick reply and elaborate explanation. This is very useful stuff for a newbie like myself. I renamed the devices as you specified and I'm testing the response. I indeed noticed that the motion and burglar pretty much fire off at the same time and with the same condition. Would be very interested in knowing what the underlying difference in logic is. Sames goes for the alarm level and alarm type. Will disable those for now but if gizmocus or anyone else can share any more info on that I'd love to hear it.
Will keep a close eye on this thread for any updates and hope to quickly get familair enough with the sensor and domoticz to share my knowledge.
-
- Posts: 8
- Joined: Wednesday 25 November 2015 18:24
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
It seems i'm not there yet. I set the Wake-up interval for the hardware to 300 seconds. Now every 300 seconds it fires the motion sensor device. Even though the sensor is placed in a closed box for testing, making sure there is no motion at all. I think my 0000235 ID is actually the motion sensor. Still very strange why one the sensors would fire on every wake-up. Maybe its in fact the alarm type, which always returns a certain value for 'no alarm' on every waktup? Any thoughts?
-
- Posts: 63
- Joined: Saturday 06 December 2014 16:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Great to read about the Multisensor6!
Synology DS218+
Homey controller
Z-Wave stuff (Fibaro / Aeotec / NEO Coolcam)
Zigbee stuff (Aqara)
HUE lights
Logitech Harmony Ultimate + Hub
IP camera's
Homey controller
Z-Wave stuff (Fibaro / Aeotec / NEO Coolcam)
Zigbee stuff (Aqara)
HUE lights
Logitech Harmony Ultimate + Hub
IP camera's
- Dnpwwo
- Posts: 819
- Joined: Sunday 23 March 2014 9:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Melbourne, Australia
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Hi, great thread, this really helped me out getting started with my 2 sensors.
I have them both configured the same and pretty much in line with @Gettingthere except I report on 224 instead of 241 (I've tried both and the results are the same for me).
The problem I have is that one sensor reports Temp + humidity *ALL* the time while the other seems to respect the 300 seconds Group 1 report. Both have reporting thresholds disabled.
Worryingly, the one that reports all the time also has a value for Barometric Pressure (30.3 kPa) which is not good.
Has anyone else seen anything like this? I've excluded/included to no avail. Will raise a call with Aeotec if I'm the only one.
I have them both configured the same and pretty much in line with @Gettingthere except I report on 224 instead of 241 (I've tried both and the results are the same for me).
The problem I have is that one sensor reports Temp + humidity *ALL* the time while the other seems to respect the 300 seconds Group 1 report. Both have reporting thresholds disabled.
Worryingly, the one that reports all the time also has a value for Barometric Pressure (30.3 kPa) which is not good.
Has anyone else seen anything like this? I've excluded/included to no avail. Will raise a call with Aeotec if I'm the only one.
The reasonable man adapts himself to the world; the unreasonable one persists to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw
-
- Posts: 37
- Joined: Friday 19 February 2016 13:29
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
Hi guys
I'm using my multisensor only for motion detection, but still after reading manual and threads I have difficult to understand which settings are supposed to trigger motion detection immediately.
I have build an event in Blockly but it takes rally long time before it detect motions. Appreciate some help
Also, is it possible to adjust the sensor time depending on the alarm is set to armed or not?
I'm using my multisensor only for motion detection, but still after reading manual and threads I have difficult to understand which settings are supposed to trigger motion detection immediately.
I have build an event in Blockly but it takes rally long time before it detect motions. Appreciate some help
Also, is it possible to adjust the sensor time depending on the alarm is set to armed or not?
Last edited by sweup on Wednesday 24 February 2016 0:08, edited 1 time in total.
- gielie
- Posts: 290
- Joined: Tuesday 12 January 2016 11:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: latest β
- Location: The Netherlands (Alkmaar)
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
I have this sensor but it doesnt work very well.
I run this on a Synology NAS with the latest beta and on a cable not a battery.
I dont get any uv or Lux values and the temp sensor is also acting strange
Al those spikes are not normal, the temp should be stable.
I run this on a Synology NAS with the latest beta and on a cable not a battery.
I dont get any uv or Lux values and the temp sensor is also acting strange
Al those spikes are not normal, the temp should be stable.
- Aeon Labs USB Stick met Z-wave plus
- Aeotec MultiSensor 6
- FIBARO FGS223
- FIBARO FGWPE Wall Plug
- Neo CoolCam Power plug
- Popp Smoke Detector
- Toon
- Kodi Media Server
- Aeotec MultiSensor 6
- FIBARO FGS223
- FIBARO FGWPE Wall Plug
- Neo CoolCam Power plug
- Popp Smoke Detector
- Toon
- Kodi Media Server
- gielie
- Posts: 290
- Joined: Tuesday 12 January 2016 11:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: latest β
- Location: The Netherlands (Alkmaar)
- Contact:
Re: Aeotec Multisensor 6 Tips & Tricks
I figured out why my lux values are zero, I use LED and i tested the sensor outside and it gave perfect lux values but when i went back to the bathroom (with LED) again zero. so i tried a normal light bulb and yes high values even when i played around with a dimmer and the normal light bulb nice changes in values.
So i went back to a LED and there is no way i can get any value with a LED.
So my question is, do other people have this same experience? Is this a known problem with light senors?
How is it possible that LEDs are not measured with this sensor, I tried an other Lux sensor and this one picked up nice values.
So i went back to a LED and there is no way i can get any value with a LED.
So my question is, do other people have this same experience? Is this a known problem with light senors?
How is it possible that LEDs are not measured with this sensor, I tried an other Lux sensor and this one picked up nice values.
- Aeon Labs USB Stick met Z-wave plus
- Aeotec MultiSensor 6
- FIBARO FGS223
- FIBARO FGWPE Wall Plug
- Neo CoolCam Power plug
- Popp Smoke Detector
- Toon
- Kodi Media Server
- Aeotec MultiSensor 6
- FIBARO FGS223
- FIBARO FGWPE Wall Plug
- Neo CoolCam Power plug
- Popp Smoke Detector
- Toon
- Kodi Media Server
Who is online
Users browsing this forum: No registered users and 0 guests