@apella12 Success! I followed the instructions above, adding the “feature:install …” step. “Remove device from controller” did not remove the sensor Thing - I did a “Delete Thing”. I scanned and added the sensor - it appears as the original node and all existing channels/items/links are already there. The tilt test was successful - I could see the Binary Sensor/Door State (Deprecated) change as expected. I am going to repeat the procedure for the second sensor and then update the instructions above.
I left Parameter 2 as 0x00 - is there any point changing it to 255 and testing again? I have sent an email to Ecolink Support for the detailed TILT-WAVE2 sensor to see if that helps clarify how the v2 tilt sensor should be defineed in the device database.
Should cut myself off from responding late at night. Anyway “Delete thing” is correct to pick up the new XML. “remove device from controller” will never really work for a battery device.
For the sake of science I would be interested in the Debug log from that test for comparison. I’m puzzled by why ECO would have a that parameter. I still have a remote hope it will send a notification instead and a test would put that to rest.
Anyway you have a working zwave binding that can be used until we get the DB figured out.
That it does. Thanks for that. It is an odd parameter since it appears to have no effect with either the current binding XML (that does not work either way) or the one I modified to use the Sensor binary (that works either way)
@chris I finally got through to someone at Ecolink. The tiltzwave2 is based on the 300-series Z-Wave chip, while the tiltzwave25 uses the 500-series chip. I was told this explains the differences in the command classes.
My Ecolink contact could not find a tiltzwave2 manual that listed the command classes and configuration parameters described in the tiltzwave25 manual but was able to provide the attached summary. I hope this helps clarify the tiltzwave2 sensor operation. Please let me know if you need additional information. Garage Door Tilt Sensor Zwave 300 series.pdf (415.2 KB)
Not really. You talk about hardware versions here.
In any case, we need to know how to tell the devices apart - normally the device will report different application versions if the software is different - in fact this is a requirement for them to do this. This is what we need to know - so that we can create two different database entries for the two different firmware versions.
@chris OpenHAB reports that the tiltzwave2 sensor as manufacturerId=014A and manufacturerRef=0001:0003, which is already described at https://www.opensmarthouse.org/zwavedatabase/139. My contact at Ecolink did not say that there were two versions of this device. The change to using the ALARM class for the door state was introduced with 2.5 version of the sensor described at https://www.opensmarthouse.org/zwavedatabase/581.
@mhilbush thought database update 1373 from 2020/08/09 introduced changes to the tiltzwave2 database definition that prevented OpenHAB from properly reporting the data sensor state.
So do I understand then that there are actually two different devices?
If so it seems we already have two versions in the database? But this thread (if I understand correctly) is about two different tilt-zwave2 responses. If there is only 1 version, then why are there two different responses?
Or is it that the database incorrectly identifies the 2 and 2.5 versions? I think a clear understanding of the different versions is still needed.
Last March (15 months ago) I posted in this thread:
The database is wrong. It references (and seems to rely on) the “Updated Manual” Tilt-ZWave-Plus-Manual-R1-04-021816kgs.pdf which is not for this device. The manual is for product type 4 (see bottom page 4). This discussion is about is product type 1, not product type 4.
I speculate that at some point TILTZWAVE2 (product type 1) was erroneously updated to reflect the characteristics from the manual for TILT-ZWAVE2.5-ECO (product type 4).
I posted this again 10 days ago in this thread. If this is not the answer to the question that keeps getting asked over and over again, sorry about that, but don’t worry; this will be my last post here. Just trying to help.
@chris, You replied directly to my previous posts, so I’m not sure that’s the problem. This really is my last post here because as I described above I have switched to Home Assistant. I was just trying to help out here, but I want to be clear that you should not be waiting for me to update the database, just like I explained over a year ago. Thanks for all the fish.
Without going back and re-reading everything I can’t really say why you didn’t just update the database then, or what else was outstanding. Sorry for any confusion.
[edit] looking above, you didn’t reply to my message (you wrote a new message in the thread without replying to me) so I didn’t get notified. As this was 1 week before I moved from the UK to New Zealand I was quite busy at the time - again, apologies for missing this response.
Ok, but someone needs to update the database if it’s wrong. There are 1300 or more entries and I personally can’t maintain them all - I just don’t have the bandwidth - again - sorry but this is a community and it does rely on others helping out and not just expecting me (or “someone else”) to do everything.
I don’t have this device, or the bandwidth to try and work out what versions exist, so it’s really appreciated when others can chip in
I normally don’t like messing with devices I do not have, but I can make the adjustments in the DB to match the XML I provided above. It is basically a copy of the window/door 2. This was in the Documentation for both the PIR and Window/Door eco2advanced-zwave-configuration-v2.pdf (108.2 KB)
It appears Eco used the same software for three devices. As it was tested by @nh905 and works for him I’m okay with it. However if @nh905 or @chips wants to make the changes, I will defer.
Without the device from the person that modified the entry we can’t compare devices and create a new DB entry. If the changes flush out a problem we can deal with it then because we will have an XML for comparison at that point.
I have both version 2 and 2.5 of the Ecolink Tilt Zwave sensors. I’m working on a new application and would like to get the 2 older ones working. This will be my third Openhab installation but have not done much debugging of bindings or zwave. I can troubleshoot and test if someone can guide me.
This (the 2.0 issue; 2.5 work fine- I have a pair of them) should be fixed in OH 3.3. I think @nh905 was going to write a summary once he had a chance to test.
@bjrootes it looks like the official 3.3.0 release is now available. It should contain the correct definition for the v2 Tilt Zwave sensors but I need to uninstall the modified Z-Wave binding with the changes provided by Bob Eckhoff, upgrade, install the official Z-Wave bionding, and retest to make sure. I will try to get this done by the end of the week.
@apella12@chris@chips I am finally back home and just successfully upgraded to OpenHAB 3.3.0 using the following procedure:
shut down OpenHAB
backed up my existing system
deleted the modified Z-Wave binding /usr/share/openhab/addons/org.openhab.binding.zwave-3.2.0.jar
ran openhabian-config to update the operating system and OpenHAB
started OpenHAB and waited for it to initialize (Z-Wave devices showed as Uninitialized)
installed the official 3.3.0 Z-Wave binding
The Z-Wave bridge and all devices initialized without any errors, including the Tilt-zwave2 devices. All rules associated with the Z-Wave devices appear to be working.
Bob and Chris, thanks for all of your efforts to get this problem resolved.
- again, apologies for missing this response.