July 07, 2015
As we're all waiting for the new Aeotec MultiSensor 6 to be officially added to the list of supported devices by all major Z-Wave gateways, I have been testing and researching a way to properly include the device to my VeraEdge. I was finally able to configure 4 basic child sensors a couple of days ago. It looks like another few weeks before we see the UV and vibration sensors on Vera's interface but all other 4 are functional after a quick manual fix.
Here are the steps to set up the ZW100-A MultiSensor with a VeraEdge. Make sure you have the latest version of UI7 firmware installed on your hub. If not, click here to perform the update first. If you're planning to use the sensor on batteries, the manufacturer recommends pairing it with the sensor running on batteries, not connected to the USB port.
1. Bring the MultiSensor close to your hub and add it to your Vera choosing the 4-in-1 sensor as device type and single-clicking on the action button. It will come up as a "D_GenericIO1" device. You may have to exclude it first (simply send an unpairing command from your Vera and click on the MultiSensor’s action button - read more here).
2. Once the device is included, please wait for all children nodes to show up. Then press the action button quickly 3 times to put the device in the wake up mode. DO NOT hold the action button. The LED indicator on the sensor should blink - do not press anything else on the sensor at this point.
3. Select the new device, then click on Advanced.
4. Go to the Params tab and make the following changes:
- device_type: urn:schemas-micasaverde-com:device:MotionSensor:1
- device_file: D_MotionSensor1.xml
- device_json: D_MotionSensor1.json
5. Wait for the led indicator on the MultiSensor to stop blinking. Do not press anything on the device until the process is completed.
6. Put the sensor in the wake-up mode again and send the “Configure Node Now” command from your Vera.
7. Once the device is configured (the LED indicator will stop blinking), restart your Vera.
Let me know if you find a shorter way to set it up or if I've missed something!
January 04, 2018
Thank you for that article. It helped me. My VeraPlus is alls working fine with about 40 z-Wave devices, 20 devices trough the RFXtrx433 Plugin, 15 devices trough MySensors Plugin, A netatmo station with 2 additional indoor modules wind and rain. Plugins like PLEG, VeraAlerts, GCal3, MySensors, Netatmo, RFXtrx, EventWatcher, Day or Night, Virtual Switch and Simple Alarm. I did it as a fresh install excluded z-wave devices from VeraLite and included to VeraPlus then created inputs to PLEG and copy/paste all the conditions.
August 19, 2015
Jerry, thank you for the feedback. I have only tested my sensor successfully with the VeraEdge, I’m not sure how the Vera 3 is with Z-Wave Plus devices. On the bright side, I hear that Vera Control is working on having the device fully supported by end of September. Let’s see if it checks out. Hopefully it will work across different controllers on UI7.
August 17, 2015
Similar to above issues with “getting secure classes” or “purging associations” I have tried numerous times to exclude/include but this simply will not work. Note, I have the Vera 3 and the latest U17 firmware. I have other sensor types that always show errors, but they at least work. This does not work. No one should purchase this item until they find a simple solution to include this, and for the full design functions.
August 15, 2015
I just updated the instructions in the blog post which worked for the latest firmware version of the MultiSensor 1.06 and the latest Vera UI7 version. Give it a go and if it doesn’t work for you, feel free to contact our customer service so they can help you with getting the updated version of the MultiSensor: firstname.lastname@example.org
I hope the update is helpful!
August 13, 2015
Yes, my Vera reports – “You are running the latest version: 1.7.1320” – but, if I can manage to delete the devices then I am going to give the instructions one more go at the weekend. I am not optimistic… and part of me just thinks I should wait for a version of Vera firmware that will work with this, but I have no clue when that will come. I might be different to most because I do want to use this via USB in a covered porch area, so I’m comfortable with that aspect. I saw that there was a way to update the firmware, but I need to have a Z-Stick (more expenditure on something I haven’t got a lot of confidence in right at this very minute) to do that.
August 09, 2015
Hippo, Did you update your UI7 to the latest version? I’m experimenting with the sensor under this and the previous version plus there are 2 versions of the firmware for the MultiSensor itself which technically should make no difference for the pairing process (according to Aeotec) but apparently it helped some users to make it work.
The closest I got to having it work after the update was on USB as well but with 2 adjustments to my initial instructions: pressing the action button ONCE instead of twice when including the sensor and pressing the action button quickly 3 times to wake it up instead of pressing and holding for 10 seconds. Again, I’m still trying to figure out a way to have it work on batteries the same way (since USB is useless to most people) and apparently it’s supposed to be included on batteries when you’re planning to use it with battery power.
I am trying to get an official update but may be another week before I have anything conclusive with other projects going on. Sorry for the hold-up!
I wondered if there was any update on this? At the moment I can’t even seem to delete the devices that were created by the failed installation, so I’m a little bit stuck. The only other bit of possibly useful information I think that I can provide right now is that all my attempts were done with the device connected to my laptop via the USB cable, not on battery power.
July 28, 2015
Thanks for clarifying Hippo. The sensor does seem to wake up for a short period of time and then stops blinking so it may not be catching all the communication Vera is sending. I’m trying to find a way around it but in the meantime the Z-Wave module on my Vera seems to be dead so I have some network work ahead before I can go back to the MultiSensor. I’ll try to put together a comprehensive guide as soon as I have the device working again on both Veras (I hope by tonight). Feel free to send any new feedback in the meantime!
July 27, 2015
Jan – by “stopped blinking” I mean the following… I waited until the child devices showed up OK, then nothing was blinking on the physical device, at that point I pressed the button and held it for 10 seconds and I saw a few blinks but then it stopped. What I was supposed to see, I believe, was it blinking for some time, but that did not happen. Anyway, I am very eager to see what the results of your further testing are… fingers are crossed.
July 25, 2015
Guys, Thanks for all your feedback. I’ve been doing some more testing on both VeraLite and VeraEdge this weekend, different scenarios, both on batteries and on USB power. I will need to spend a bit more time to get all the details and should publish a revised post on Monday/Tuesday so stay tuned.
July 24, 2015
Rafael, It is not. I upgraded to edge for this one. They have a $50 rebate deal going this month.
Is it compatible with veralite???
July 23, 2015
Hi JAN, I have some more info for you. We are all getting stuck on step 2. I can not get past this step without an error.
- If you hold the action button for 10 seconds, it blinks a red light (once) and then nothing
- If you hold the action button for 5 seconds, it blinks a yellow light for about 20 seconds then errors (purge associations)
- If you hold the action button for 7 seconds, it blinks a purple light for about 20 seconds then errors (Getting secure classes)
There’s something we are all missing. Can you verify I have the right firmware (below)? Also, can you try the set up again and watch the LED light on the front while setting up?
Vera Edge firmware version: 1.7.1248
THANKS! Completely lost without you.
July 22, 2015
You mentioned that it “stopped blinking” – if the sensor was blinking before you pressed the action button for 10 seconds it means that it was probably still communicating with the controller. Try excluding it and adding again, then wait for the led indicator on the sensor to go out, you should see all child nodes on the dashboard by that time. Continue with pressing the action button for around 10 seconds (but not more than for 15) only after the MultiSensor does not blink anymore. Maybe that will help!
I’ve failed to get this to work myself. The difference I see between what I’m experiencing and the instructions here is that my device stops blinking (red) when I hold the button down for 10 seconds to put it in wake-up mode. The article here implies it keeps on blinking, mine does not. So I end up with 5 devices – none of them appear to be doing anything useful, and the GET_LANG(genericsensor,sensor) I have zero idea about. There is red text below the PIR sensor saying “Purging associations” and I cannot seem to get beyond that point.
July 21, 2015
Sorry for not replying earlier. I guess I was not clear in the post about the device type, I chose “Generic Z-Wave device” from the list and by secure I meant adding it by click TWICE on the action button on the MultiSensor. This will allow for the device to be added as a Z-Wave Plus and should get rid of the error. Also make sure you have your Vera updated to the latest version of the UI7.
I hope that was helpful! Let me know if I missed anything.
July 20, 2015
Andrew…. Yes, I have the same problem (purge associations) with VeraEdge. I’ve wasted a little too much time trying to get this thing to work. I guess we better wait for Vera/Aeon to sort things out.
July 13, 2015
Have you run into this causing VeraEdge to continually try to purge associations and never finish setting up the device?
July 11, 2015
Hello, I’ve tried it 5 times now. I think I’m missing something. I do not have an option for “add it to your Vera as a secure Generic Z-Wave device” I have the generic option but no secure generic. Does yours say secure? Seems to be getting hung up at “Getting secure classes” – Thank You!
Comments will be approved before showing up.
August 06, 2020
If you already have Amazon Echo set up, you know how convenient it can be. There’s nothing like walking out the front door with full hands and telling Alexa to turn off your lights last minute. But these smart lights and plugs can be slow to react as you keep adding more smart home devices and clogging your network.
Alexa only “speaks” WiFi (and ZigBee if you have the EchoPlus). It currently doesn’t support Z-Wave, the protocol of choice for home automation thanks to its high speed and low interference with other connected devices in your home. That means you can’t have a Z-Wave switch or plug speak directly to your Echo. BUT you can use a smart home hub as a bridge between your Z-Wave devices and Amazon Alexa. Now that’s a whole other level of functionality to unlock!
And if you already have a Z-Wave hub but no smart speaker, you might be thinking how cool it would be to have voice control for your automations and smart home devices. It’s a step towards a more integrated, easy-to-use smart home with improved security, comfort, and convenience.
May 10, 2020
Starting May 13, 2020, Wink will be charging its users a $4.99 monthly subscription fee. If you don’t pay, you’ll lose your automations, smart rules, and access to voice control. [Update 5/30/20: Wink has since backed out of the decision, at least for now. Update 7/27/20: The subscription service for Wink is finally in effect.]So is it worth paying $5 a month for Wink’s service? The platform hasn’t been adding new features or expanding its list of supported devices for a while now. The announcement introducing the subscription model didn’t include any details on when and how the system would start updating again. They also failed to give users at least 30 days notice to consider how to move forward. If you’re thinking about switching to another platform, we can’t blame you. Here are a few alternatives for reliable smart home solutions that are most popular among our customers and the team here at The Smartest House. They’re all one-time investments without monthly fees. You’ll find a list of benefits and limitations with each platform, but if you have any questions about specific features we didn’t cover here, get in touch or post in the comment section below.
November 05, 2018
Winterizing your home used to mean lots of physical labor - caulking windows, installing heavier drapes, maybe even changing out older windows and doors that were too efficient at releasing insulated air. Winter prep can still mean all of the above, but new Z-Wave technology has made certain aspects of winterization easier while adding another level of protection as those temperatures drop.
Here’s what we’re using to stay cozy and make sure our energy bills don’t make us freeze in our tracks:
This is one of our winter must-haves. It’s the first Z-Wave line voltage thermostat in North America (but be careful, it won’t work with forced air systems!). Use it to control electric baseboards and convector heaters all from your Z-Wave hub’s app interface. Reduce your energy consumption by 30% with custom heating schedules, or just switch to the thermostat’s built-in Economy mode to keep things efficient.