michszaf
(Michszaf)
January 31, 2021, 8:21pm
1
Hello,
Maybe any of you had and issue with Aeon Labs Minimote after moving from OH2.5 to 3?
Im trying to make it work but after im including it successfully with all values in place it does not sending scene numbers at all.
With OH2.5 was perfectly working with no issues configured as follow in Items:
Number MiniRemote "Channel [%d]" {channel="zwave:device:1d7f3dab43:node18:scene_number"}
I had rules created for changing values.
JustinG
(JustinG)
January 31, 2021, 8:35pm
2
As always with a battery op z-wave device make sure you’ve actually woken it up over and over again, just to make sure, but there are several of us just discovering similar problems in other devices so this may be part of a larger pattern.
Platform information:
Hardware: Intel NUC
OS: openSUSE 15.2
Java Runtime Environment: zulu11.43.55-ca-jdk11.0.9.1-linux.x86_64
openHAB version: openHAB 3.1.0 - Build #2165
Z-Wave Controller: Aeotec Z-Stick Gen5 (ZW90)
Z-Wave Device: Aeotec Door/Window Sensor 7 (ZWA008)
Dear Community,
i was able to include the device successfully. Name of the device is show correct so far as i can understand it. I created items for door/window and battery information. These information are not updated on …
and
I’ve been banging my head on this problem for the better part of a couple weeks now and can’t get anywhere. I’m going to try and keep this concise but the description is going to sound weird.
tl;dr
OH3 zwave only sometimes gets the id of aeotec nanomotes, does not create xml files for the devices, and does not receive any communication from them even if they are successfully id’d and (I think) initialized.
Full Story:
I migrated from my OH2 native install to OH3 on docker. I copied my secu…
michszaf
(Michszaf)
February 14, 2021, 3:09pm
3
i have new symptoms, as i can see XML. But it still does not registering values of the scenes.
I was trying 100 of times to remove thing, rescan zwave and by waking up adding the devices.
from time to time xml is updated (new timestamp)
JustinG
(JustinG)
February 14, 2021, 3:36pm
4
If the binding has produced the xml file then it should be able to communicate with the device at this point. Check the devices lifeline association group.
If that is not set to controller then the controller will not know that it is supposed to be processing the packet from the remote. Many of the devices that the binding has been having trouble adding recently wind up not having this association group properly set. But if you’ve reached the stage where there is an xml file then the binding should now be able to set the group and you should be good to go.
If there is an xml file it is possible that exact device identifier is not in the database. Posting the xml could help us check.
JustinG
(JustinG)
February 14, 2021, 6:51pm
6
If it was working with his previous 2.5 installation, then that shouldn’t be the problem should it? Even with the minor updating issue recently, it’s not likely the database has regressed is it?
chris
(Chris Jackson)
February 14, 2021, 6:56pm
7
While it’s true that it can communicate, it does not mean that it can identify the device.
What version of 2.5 - it ran for a long time.
It’s not “likely”, but it does happen for a few reasons. Really though we’re just speculating - it would be MUCH easier to understand what is happening if logs or the XML, or the device properties or something like this was provided.
michszaf
(Michszaf)
February 14, 2021, 7:08pm
8
It was identified as: DSA03202 Minimote 4 button remote control
zwave:device:1d7f3dab43:node18
Here is XML:
<node>
<homeId>0xec514085</homeId>
<nodeId>18</nodeId>
<version>3</version>
<manufacturer>0x86</manufacturer>
<deviceId>0x3</deviceId>
<deviceType>0x1</deviceType>
<listening>false</listening>
<frequentlyListening>false</frequentlyListening>
<routing>false</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>1000</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_COMMAND_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_MARK</commandClass>
<commandClass>COMMAND_CLASS_SCENE_ACTIVATION</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map"/>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
<deviceClass>
<basicDeviceClass>BASIC_TYPE_CONTROLLER</basicDeviceClass>
<genericDeviceClass>GENERIC_TYPE_GENERIC_CONTROLLER</genericDeviceClass>
<specificDeviceClass>SPECIFIC_TYPE_PORTABLE_REMOTE_CONTROLLER</specificDeviceClass>
</deviceClass>
<endpointId>0</endpointId>
<secureCommandClasses/>
<supportedCommandClasses class="concurrent-hash-map">
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<maxGroups>0</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_WAKE_UP</commandClass>
<COMMAND__CLASS__WAKE__UP>
<version>0</version>
<instances>0</instances>
<control>false</control>
<versionSupported>0</versionSupported>
<targetNodeId>0</targetNodeId>
<interval>0</interval>
<minInterval>0</minInterval>
<maxInterval>2147483647</maxInterval>
<defaultInterval>0</defaultInterval>
<intervalStep>0</intervalStep>
<isGetSupported>false</isGetSupported>
</COMMAND__CLASS__WAKE__UP>
</entry>
<entry>
<commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
<COMMAND__CLASS__NO__OPERATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__NO__OPERATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SCENE_ACTIVATION</commandClass>
<COMMAND__CLASS__SCENE__ACTIVATION>
<version>1</version>
<instances>1</instances>
<control>true</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__SCENE__ACTIVATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<COMMAND__CLASS__MANUFACTURER__SPECIFIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>134</deviceManufacturer>
<deviceType>1</deviceType>
<deviceId>3</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>1</version>
<instances>1</instances>
<control>true</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<libraryType>LIB_CONTROLLER</libraryType>
<protocolVersion>2.78</protocolVersion>
<applicationVersion>1.17</applicationVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>241</int>
<configurationParameter>
<index>241</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>242</int>
<configurationParameter>
<index>242</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>243</int>
<configurationParameter>
<index>243</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>244</int>
<configurationParameter>
<index>244</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>245</int>
<configurationParameter>
<index>245</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>246</int>
<configurationParameter>
<index>246</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>247</int>
<configurationParameter>
<index>247</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>248</int>
<configurationParameter>
<index>248</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>250</int>
<configurationParameter>
<index>250</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>true</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</COMMAND__CLASS__CONFIGURATION>
</entry>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors/>
<lastReceived>2021-02-14 15:12:38.308 UTC</lastReceived>
</node>
Im still fighting with logs as getting: Error executing command: Unable to set level for logger when changing to DEBUG
chris
(Chris Jackson)
February 15, 2021, 9:54am
9
So it’s fully discovered, and communicating, and the device is in the database, so there’s no problem there. The device is reasonably simple from a definition perspective, so I’d suggest to get a debug log to see what is happening - hopefully it will show if something is being received. If not, then check the associations.
JustinG
(JustinG)
February 15, 2021, 4:59pm
10
As much for my own learning as solving the original question, aren’t the device’s available association groups usually listed in the xml even if they don’t have any associations currently setup?
michszaf
(Michszaf)
March 13, 2021, 12:04pm
11
sorry for late reply, busy period
Im not able to win with an error:
log:set DEBUG org.openhab.binding.zwave
[Fatal Error] :1:1: Premature end of file.
Error executing command: Unable to set level for logger
any idea?