I don’t know the answer to this question.
I found an entry for EZMotion Express in the database in here (EZMotion Express by Express Controls).
Should I look further into the database, or do anything else on my side to answer this question?
Openhab recognises the device as Z-Wave Node 18: EZMotion Express Wireless 3-in-1 Sensor.
I guess this means that the device is associated with something in the database…
...
The HSM100 is the same as the EZMotion+.
The user manual can be found http://www.expresscontrols.com/pdf/EZMotion+OwnerManual.pdf
Maybe EZMotion+ is not excactly the same as EZMotion Express?
I found references of xml files that describe this (or similar) device in here.
Users of openhab reported working with this (or similar) device in here and here
I contacted the founder of Express Controls, and asked if there are 2 similar products. His reply:
Apparently EZMotion Express is a typo. There was an earlier EZMotion
and then later a slightly improved version called EZMotion+.
Both were also sold under the homeseer brand as HSM100 but
they are the same product – just a different name.
I’m not sure how other users of openhab initialize the device successfully.
@chris, is there something that can be done on your side to accommodate?
Thanks
HSM100 was developed long before the current rules on endpoints were in place.
The endpoints are only to differentiate between the sensors in the device.
Everything else should be sent without multichannel encapsulation.
Wakeup CC must be sent without multichannel encapsulation.
Wakeup applies to the device as a whole, not to the individual sensors.
this is exactly what the database modification would do - effectively to remove
the wakeup class that the device currently advertises from the 2 endpoints.
@chris Is the database modification something that I can do, or it needs to be done on your side?
If the latter, do you know when it would be done? Do I then have to download an updated version of the database? Where from?
Also, do you know if the Zway binding can potentially resolve this issue, without changes to the database?
Does it rely on the database of zwave devices that you are maintaining?
Hi @chris
Did you have a chance to get on that? (sorry for pestering)
Is there anything that I can do from my side? (I read that you sometimes give access to users to the database)
Let me know if I can help.
Thanks.
I’ll try it tonight when I get back home.
How do I get the latest biding? Does it include the updated database, or do I have to grab it separately?
Thanks
I am having trouble to reinstall the zwave binding.
In HABmin -> Configuration -> Extensions -> Bindings (http://localhost:8080/habmin/index.html#/extensions)
I unistall and then install “Z-Wave Binding”. The web page shows the right signs (the status changes:
uninstall -> install -> uninstall )
but I don’t see the binding in the openhab2
ll /opt/openhab2/runtime/karaf/system/org/eclipse/smarthome/binding/
total 40
drwxrwxrwx 10 openhab openhab 4096 May 22 2016 ./
drwxr-xr-x 13 openhab openhab 4096 May 22 2016 ../
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.digitalstrom/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.fsinternetradio/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.hue/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.lifx/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.ntp/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.sonos/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.wemo/
drwxr-xr-x 3 openhab openhab 4096 May 22 2016 org.eclipse.smarthome.binding.yahooweather/
I may have permissions problem, as I invoke openhab from the command line as root (is this ok?)
sudo /opt/openhab2/start.sh
I tried changing permissions to the binding directory, but it didn’t help:
I installed openhab2 from scratch. I followed the instructions from here to do Package Repository installation (snapshot installation). I then started openhab2 like so
sudo su -s /bin/bash -c '/usr/share/openhab2/start.sh' openhab
I now see “Paper UI” and “HAB Panel”, but not HABmin, which I used before to add bindings.
Trying to follow the instructions here to install Habmin, but the link for the latest snapshot is broken.
I added the zwave binding via PaperUI, but the HSM100 still does not show up properly.
Can someone direct me to the location of the log messages?
They used to be in /opt/openhab2 (e.g. /opt/openhab2/userdata/logs/openhab.log) for the manual installation, but for the package installation there is no /opt/openhab2, and /usr/share/openhab2 does not have a userdata directory…
That was for a very old HABmin installation on openHAB2 … a long time ago
Now we have a zwave2 binding and you correctly installed it through PaperUI. Don’t forget to delete that other stuff in your addons folder …
Thanks @sihui. So I reinstalled openhab2 from scratch (after removing all previous oh2 related files)
(did Repository installation, beta repository, openhab2-online option)
I excluded and reincluded the HSM100 device, and I’m seeing the same results as before:
no node xml file generated for the HSM100 (node 19)
a zwave device that is used for reference, initialises properly, creates the file node3.xml and responds well
@chris I tried looking at the log (node 19) using your tool, but I don’t know how to interpret the log. Can you take a look at the log file here please?
dpkg --list | grep openhab
…
ii openhab-addon-binding-zwave 1.8.3 all openHAB ZWave Binding
…
rc openhab2-offline 2.0.0~20161116033345 all openHAB Offline Distribution
ii openhab2-online 2.0.0~b5 all openHAB Online Distribution
How do I know if this is the latest version?
and what do these different numbers indicate?
0.9.0.b2
4.0.8
2.0.0.b5
@chris I checked the HSM100 device entry here.
It still specifies WAKE_UP in the command class for endpoint1, and endpoint2. I thought you were going to remove this?
I’m confused now. In the email between you and Eric (the developer of HSM100) repeated in this post, you mentioned
Thanks - this is exactly what the database modification would do - effectively to remove the wakeup class that the device currently advertises from the 2 endpoints.
