I am trying to add an Ecolink Garage Door Tilt Sensor (Z-Wave Plus version) to my Vera Plus Controller. I have Excluded the Device to start, then included it (several times). it always gets added as two devices as shown in this picture:
I have seen other posts (http://forum.micasaverde.com/index.php/topic,38657.msg289291.html#msg289291) that suggest there is a well defined set of steps to solve the problem of the device registering as a motion sensor versus a tilt sensor. The parameters settings are already set to the suggested settings:
The difference is on the Variables page. The settings that are suggested to change, NodeInfo and PollingState and ChangeState don’t exist on my installation.
My current situation is the device is added, it shows as two devices and does not show any change state when the device is tilted and I can’t seem update the settings based on other posts to fix the problem. Anyone have any suggestions?
I added directly at the Vera3 because I did not see the device listed in the add devices menu.
You would think that for a device that has been available since 2014 that it would work properly in Vera by now.
When tilted I get a push notification from the generic IO, nothing from the door / window sensor. Nothing on the devices page updates to indicate tripped.
I also don’t get the manufacturerinfo info in vera, it shows as 330,4,3 the info from Ecolink shows Manufacturer ID of 0x014A ( 330 dec ), Product Type 0x0001, Device Product ID 0x03 ( tilt sensor ), so I would expect to see a 330,1,3, but I’m no expert.
So Vera should be able to properly identify the device as an Ecolink Tilt Sensor and display it as a single device, but it does not.
I got this working today on Vera Secure 1.7.2817, I was running into the same issue as above so I combined steps from a few scattered threads dealing with this sensor. The fix seemed to be modifying the Params and Variable sections. After a Configure command I instantly got a working tilt sensor. Before I’d get tamper alerts for the generic device only, but it was hardly helpful. Eastside was on the right path, but it’s not the PollingState and ChangeState you’re looking for. It’s Capabilities.
The steps required me to change:
Advanced/params
Change subcategory_num to 1
Change device_file to D_DoorSensor1.xml
Change device_json to D_DoorSensor1.json
Do the following within the Advanced/Variables Tab:
Under Capabilities add a ‘32’ directly after the ‘|’ pipe in the middle
Under NodeInfo add ‘20’ to the very beginning.
Finally, go to Advanced/Commands and ‘Configure Node Right now’. I removed the cover of the sensor because another thread mentioned it may be the only way to set/change settings. When it came back it looked like a standard Magnetic Door Sensor and responded to tilts correctly, with battery indicator and an arm/disarm. I did notice the Nodeinfo and Capabilities settings I mentioned above didn’t persist after the Configure Command, but it’s working, so I don’t mind. Hopefully this helps.
So I got the device working, but it just says state changed. Is there a way to have it actually tell you if the garage door is up or down? Just knowing that the status changed, doesn’t really help me know if the door went from open to closed or vice versa.
If you have the need to control the garage door with your Vera, do yourself a favor and get a garage door sub controller with a hardwired sensor switch included. Install it once, forget it and don’t look back.
No batteries to worry about.
Always gives status of the door. Completely closed = CLOSED or open an inch or more = OPEN.
Trigger scenes off of status and control the garage door as an action.
[quote=“Slartibartfast, post:11, topic:196010”]All I know is a NECO controller.
I would love to go with the MIMO2+ but despite the blurb on their website there is no EU version yet. and I don’t want to go for 2 x Mimolight.
I will have to go for dual output relay (pulse type) FIBEFGS-222
and a separate input module for status input FIB_FGBS-001
Such a shame though that it can’t be all in one.[/quote]
What would you say is the percentage of garage door openers that are triggered like yours in the EU? Open, Close and Stop?
I would say 99% of US openers are one pair of wires = normally open and on close = Garage Door Closes. Normally open and on close = Garage Door Opens.
[quote=“Jamr, post:12, topic:196010”][quote=“Slartibartfast, post:11, topic:196010”]All I know is a NECO controller.
I would love to go with the MIMO2+ but despite the blurb on their website there is no EU version yet. and I don’t want to go for 2 x Mimolight.
I will have to go for dual output relay (pulse type) FIBEFGS-222
and a separate input module for status input FIB_FGBS-001
Such a shame though that it can’t be all in one.[/quote]
What would you say is the percentage of garage door openers that are triggered like yours in the EU? Open, Close and Stop?
I would say 99% of US openers are one pair of wires = normally open and on close = Garage Door Closes. Normally open and on close = Garage Door Opens.[/quote]
I can’t say for everywhere but all the ones I have seen are two buttons plus a stop.
It will indicate the ‘open’ or ‘up’ by showing what would normally be motion in a sensor. You’ll see the two curved lines above the sensor icon turn red, this means that the door is opened, once it is closed you’ll see those lines gray out again. It’s not the best, the Linear Garage Door opener I have actually gives you the icon of a garage door with straight forward indicators, it’d be nice if this did the same. I suspect you may be able to play with the device type to change this, but I haven’t spent the time.
[quote=“havik34, post:6, topic:196010”]I got this working today on Vera Secure 1.7.2817, I was running into the same issue as above so I combined steps from a few scattered threads dealing with this sensor. The fix seemed to be modifying the Params and Variable sections. After a Configure command I instantly got a working tilt sensor. Before I’d get tamper alerts for the generic device only, but it was hardly helpful. Eastside was on the right path, but it’s not the PollingState and ChangeState you’re looking for. It’s Capabilities.
The steps required me to change:
Advanced/params
Change subcategory_num to 1
Change device_file to D_DoorSensor1.xml
Change device_json to D_DoorSensor1.json
Do the following within the Advanced/Variables Tab:
Under Capabilities add a ‘32’ directly after the ‘|’ pipe in the middle
Under NodeInfo add ‘20’ to the very beginning.
Finally, go to Advanced/Commands and ‘Configure Node Right now’. I removed the cover of the sensor because another thread mentioned it may be the only way to set/change settings. When it came back it looked like a standard Magnetic Door Sensor and responded to tilts correctly, with battery indicator and an arm/disarm. I did notice the Nodeinfo and Capabilities settings I mentioned above didn’t persist after the Configure Command, but it’s working, so I don’t mind. Hopefully this helps.[/quote]
[quote=“Slartibartfast, post:13, topic:196010”][quote=“Jamr, post:12, topic:196010”][quote=“Slartibartfast, post:11, topic:196010”]All I know is a NECO controller.
I would love to go with the MIMO2+ but despite the blurb on their website there is no EU version yet. and I don’t want to go for 2 x Mimolight.
I will have to go for dual output relay (pulse type) FIBEFGS-222
and a separate input module for status input FIB_FGBS-001
Such a shame though that it can’t be all in one.[/quote]
What would you say is the percentage of garage door openers that are triggered like yours in the EU? Open, Close and Stop?
I would say 99% of US openers are one pair of wires = normally open and on close = Garage Door Closes. Normally open and on close = Garage Door Opens.[/quote]
I can’t say for everywhere but all the ones I have seen are two buttons plus a stop.[/quote]
Yea the Telguard is US frequency so it will not work on your EU Z-Wave system. You will probably have to build one.
For safety, please do not use a high voltage relay.
Good luck.
thank you, this worked for me as well and shows open and closed just like a door sensor would, I am using the zwave plus version on veraedge
Z-wave Plus Gold Plated Reliability Garage Door Tilt Sensor, White (TILT-ZWAVE2.5-ECO)
I had to replace the battery before I could get it to join (CR123A), the LED lit up but would not work with battery that came with it, so I must of got a dud, but that is ok, good to start fresh
[quote=“havik34, post:6, topic:196010”]I got this working today on Vera Secure 1.7.2817, I was running into the same issue as above so I combined steps from a few scattered threads dealing with this sensor. The fix seemed to be modifying the Params and Variable sections. After a Configure command I instantly got a working tilt sensor. Before I’d get tamper alerts for the generic device only, but it was hardly helpful. Eastside was on the right path, but it’s not the PollingState and ChangeState you’re looking for. It’s Capabilities.
The steps required me to change:
Advanced/params
Change subcategory_num to 1
Change device_file to D_DoorSensor1.xml
Change device_json to D_DoorSensor1.json
Do the following within the Advanced/Variables Tab:
Under Capabilities add a ‘32’ directly after the ‘|’ pipe in the middle
Under NodeInfo add ‘20’ to the very beginning.
Finally, go to Advanced/Commands and ‘Configure Node Right now’. I removed the cover of the sensor because another thread mentioned it may be the only way to set/change settings. When it came back it looked like a standard Magnetic Door Sensor and responded to tilts correctly, with battery indicator and an arm/disarm. I did notice the Nodeinfo and Capabilities settings I mentioned above didn’t persist after the Configure Command, but it’s working, so I don’t mind. Hopefully this helps.[/quote]
As a few others have noted, on a VeraPlus, when you make these changes the device just disappears. Any idea on why or how to prevent that?
Also wonder why you would not change the schema to DoorSensor1 from MotionSensor1
I’ve unpaired and repaired at least 5 times. It detects as motion sensor every time heck once I even got a text message notification. But when I configure it - poof! Gone.
UPDATE - Apparently it takes a long time to reconfigure. It finally popped back up and seems to be working fine. I changed the Schema to DoorSensor from MotionSensor as well with no ill effects.
I have been working on this all afternoon. Sometimes it pairs and when I change the parameters as suggested, I do get it to show only one icon (not a door). However, tilting the sensor doesn’t cause anything to happen. At one time it showed my battery at 100% and the next time 61%. Sometimes I get a solid green light before it pairs and sometimes I get a flashing green light. I have never got a solid red light. I’ve chosen Eco Motion Sensor and Generic z wave devices for pairing. What am I doing wrong?
After spending way too much time on this little sensor, I opened a support request with Ecolink. This is their response:
== quoted from Ecolink support response ==
We actually have received a few emails about this same issue with the Vera controllers with the Vera system causing the problem and we found that there are some steps to hopefully get it to work correctly. Below are those steps to get things working correctly:
log into Vera web portal through the following web portal Login
Learn the device into your Vera control system using the generic learn process.
Devices → Add Device
after the device is learned in, it should appear as a generic Z-wave device.
click on the 500 series tilt device
Click on Advanced
Change the following parameters to match the following and press enter:
device_json: D_MotionSensor1.json
category_num:4
subcategory_num:3
=== end quote from Ecolink support ===
I made the above changes and the sensor worked, except it would give me messages about “motion detected”. Also, a ghost IO device showed up in Vera like another user mentioned on this thread.
I then changed the device_file and device_json to D_DoorSensor1 (instead of MotionSensor1) and also changed the subcategory_num to 1 (after seeing this link http://wiki.micasaverde.com/index.php/Luup_Device_Categories)
Since then the device is working fine as a door sensor. Notice I did not do the nodeinfo and Capabilities edits like havik34 mentions. Also, for some reason when I click on Params the subcategory shows 3 (motion sensor) but it is behaving like a 1 (door sensor). I dont know if this number is what Vera polled from the sensor or what is stored in vera’s local database (in which case I dont understand why it should not persist).
The sensor does go to sleep as soon as you put the cap on it, so I had to remove the lid and then click on ‘Commands > Configure node’, similar to what havik mentions.
Overall, a little frustrating for something that supposedly should be supported out of the box by Vera by now but perhaps they know something that I dont.
