I’ve added a remote ZXT-120 to my network, it picks up fine but there are no channels in paper ui. Can anyone help?
You usually have to wake up battery powered devices several times for the binding to fully recognize the device and its channels.
Thanks for the suggestion but I don’t think that’s worked I’ve tried waking a number of times and it has reported it is online and I can change parameters But no channels appear
The xml file shows the zwave classes I’m not sure why it is not working
Can I create a thing file for it if so how?
Thanks
Andrew
What does that mean?
Can you provide a log, or maybe some images of the attributes in PeperUI or HABmin, and the channel definition area - something that can help understand what’s happening. What device IDs does your device have?
What is a thing file?
hi Chris, thanks for joining.
it picks up fine - meaning it is discovered.
I thought I read somewhere you could make .thing files and put them in the things folder - just a workaround I hope I dont need.
here is a picture of the thing in PaperUI as you can see no channels
it is node 22 - Im sorry i dont know what log I would need?
here is the xml:
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>THERMOSTAT</genericDeviceClass>
<specificDeviceClass>THERMOSTAT_GENERAL_V2</specificDeviceClass>
</deviceClass>
<homeId>0xf41f308c</homeId>
<nodeId>22</nodeId>
<version>4</version>
<manufacturer>0x5254</manufacturer>
<deviceId>0x8377</deviceId>
<deviceType>0x102</deviceType>
<listening>false</listening>
<frequentlyListening>true</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<nodeInformationFrame>
<commandClass>BASIC</commandClass>
<commandClass>SWITCH_ALL</commandClass>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<commandClass>THERMOSTAT_MODE</commandClass>
<commandClass>THERMOSTAT_SETPOINT</commandClass>
<commandClass>THERMOSTAT_FAN_MODE</commandClass>
<commandClass>CONFIGURATION</commandClass>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<commandClass>BATTERY</commandClass>
<commandClass>VERSION</commandClass>
</nodeInformationFrame>
<supportedCommandClasses>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>CONFIGURATION</commandClass>
<configurationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>32</int>
<configurationParameter>
<index>32</index>
<size>1</size>
<value>-1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>33</int>
<configurationParameter>
<index>33</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>35</int>
<configurationParameter>
<index>35</index>
<size>4</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>37</int>
<configurationParameter>
<index>37</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>25</int>
<configurationParameter>
<index>25</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>26</int>
<configurationParameter>
<index>26</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>27</int>
<configurationParameter>
<index>27</index>
<size>2</size>
<value>11</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>28</int>
<configurationParameter>
<index>28</index>
<size>1</size>
<value>-1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</configurationCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>3.42</protocolVersion>
<applicationVersion>1.20</applicationVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>BATTERY</commandClass>
<batteryCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<batteryLevel>98</batteryLevel>
<batteryLow>false</batteryLow>
<isGetSupported>true</isGetSupported>
</batteryCommandClass>
</entry>
<entry>
<commandClass>SWITCH_ALL</commandClass>
<switchAllCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<mode>SWITCH_ALL_EXCLUDED</mode>
</switchAllCommandClass>
</entry>
<entry>
<commandClass>THERMOSTAT_FAN_MODE</commandClass>
<thermostatFanModeCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<fanModeTypes>
<fanModeType>AUTO_HIGH</fanModeType>
<fanModeType>AUTO_LOW</fanModeType>
<fanModeType>ON_HIGH</fanModeType>
<fanModeType>ON_LOW</fanModeType>
<fanModeType>UNKNOWN_5</fanModeType>
<fanModeType>UNKNOWN_4</fanModeType>
</fanModeTypes>
<isGetSupported>true</isGetSupported>
</thermostatFanModeCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>21076</deviceManufacturer>
<deviceType>258</deviceType>
<deviceId>33655</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>THERMOSTAT_SETPOINT</commandClass>
<thermostatSetpointCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<setpoints>
<entry>
<setpointType>HEATING</setpointType>
<setpoint>
<setpointType>HEATING</setpointType>
<initialised>true</initialised>
<initCount>0</initCount>
<outer-class reference="../../../.."/>
</setpoint>
</entry>
<entry>
<setpointType>COOLING</setpointType>
<setpoint>
<setpointType>COOLING</setpointType>
<initialised>true</initialised>
<initCount>0</initCount>
<outer-class reference="../../../.."/>
</setpoint>
</entry>
</setpoints>
<isGetSupported>true</isGetSupported>
</thermostatSetpointCommandClass>
</entry>
<entry>
<commandClass>THERMOSTAT_MODE</commandClass>
<thermostatModeCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<modeTypes>
<modeType>FAN_ONLY</modeType>
<modeType>HEAT</modeType>
<modeType>DRY_AIR</modeType>
<modeType>AUTO_CHANGEOVER</modeType>
<modeType>RESUME</modeType>
<modeType>COOL</modeType>
<modeType>OFF</modeType>
</modeTypes>
<isGetSupported>true</isGetSupported>
</thermostatModeCommandClass>
</entry>
<entry>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<multiLevelSensorCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<sensors>
<entry>
<multilevelSensorType>TEMPERATURE</multilevelSensorType>
<multilevelSensor>
<sensorType>TEMPERATURE</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</multiLevelSensorCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups/>
<nodeNeighbors>
<int>1</int>
<int>6</int>
<int>7</int>
<int>8</int>
<int>9</int>
<int>12</int>
<int>15</int>
<int>16</int>
<int>17</int>
<int>19</int>
</nodeNeighbors>
<lastSent>2016-12-01 09:44:27.114 UTC</lastSent>
<lastReceived>2016-12-01 09:45:28.721 UTC</lastReceived>
</node>
You have a version that is not in the database so that’s why it doesn’t work. The database will need to be updated.
I’m sure you’ve been asked millions of times how - do you have a link I can read?
Thanks
Andrew
I will update this tonight - it’s just a case of adding the IDs for your device…
ok great and then how does this apply to my install? I am running an offline version (I think)
For an offline version, you will either need to update to a complete new offline version, or manage the update manually (which may be as simple as uninstalling the binding, and adding the new binding and its dependancies into the addons folder). Really, I would suggest to use the online version as it’s much easier…
Ok I will try to work out how to do this!
After looking at this properly, it looks like it is in the database. Everything actually looks ok - why do you say there are no channels? Can you provide an image showing what’s in the channel config area in HABmin?
The previous screenshot is where the channels should appear in paperui. That’s where they are for other things
There are no channels in habmin either but will grab a screenshot
I even tried guessing what the items file and sitemap should be but that didn’t work
Thanks
Andrew
I guess then I’d check the logs to see if there’s any errors and maybe grab a debug log to see what’s happening…
This is has happened to me multiple times, and appears to be a recurring issue. The problem is the “AU” extension of the device name “ZXT-120AU”.
See here Zwave ZXT-120 IR extender not showing channels
This device needs to be removed from the database and it will identify as “ZXT-120” (sans the AU region extension).
Chris, is there any way to stop this happening? It’s the main reason I don’t update to newer snapshots as I’m stuck using Offline (on windows) it can be a real pain.
Hope this helps, cheers.
Liam
Sorry, but it’s absolutely nothing to do with the extension AU - the database doesn’t use this at all.
The issue is that some manufacturers use different device type/id values for different regions - this is what the database uses to correlate a device to a database entry - not the “AU” extension. When a new device, or new region, or whatever, is produced by the manufacturer, then it needs to be updated in the database.
Unfortunately, devices and their references need to be added to the database in order to get the configuration. Really, there’s no way around this. Once they are added, then it’s there for good - until the manufacturer changes the device firmware.
I’m not sure I understand this 
. Once a device type/id is added to the database, it will just about never be removed, so devices shouldn’t disappear once they are added. The only time a type/id is removed is if there’s some sort of conflict, and that’s very very rare, and I try and work out what’s going on before doing this - I think it’s only happened once or twice.
It’s probably also worth noting that the issue being discussed here doesn’t appear to be related to the database device detection as the device appears to be detected correctly from the images above -:
The problem here is that there are no channels being created - not that the device itself isn’t found…
Sorry Chris, I must’ve misunderstood the reason for the problem in our last conversation.
But this is exactly what was happening to me in the post I linked to, my device correctly identified as “ZXT-120AU” but no channels would appear. You were able to fix the issue in the database and then my device started identifying as “ZXT-120” with all channels.
Ok, thanks. It looks like for some reason this rogue device came back - I’ll remove it again. The issue here is that there are two devices with the same type/id and if the system picks up the wrong one, then it doesn’t work (I’m not sure if search order is going to be constant).
Hopefully this will fix the problem @Andrew_Pawelski is having so thanks for the reminder (and if it comes back again - please just yell at me 
).