Hi,
Did you manage to show the temperature? I also connected a DS18B20 and no luck so far.
I bought a random DS18B20.
I also had this issue. One of the DS18B20s I bought was faulty. Troubleshooting can be a pain since there are no indicators and you have to exclude and include the UBS each time you want to add a new DS18B20. I also found the triple click to include/exclude needed really quick presses. Your device shows 3 endpoints, which seems to indicate it found one temperature sensor. Here is a screen shot of mine.
1 Like
Iâve had two of these working fine for the past 6 months. I needed to add another and add a temperature sensor to an existing one. Iâve had no problem adding them but both now only show the first contact and no temperatures. What am I missing?
Did you remember to create temp and contact child devices?
I can create the two contact children but the second doesnât change even though the signal does pass through to the output terminals.
The temperatures just donât register so it wonât make the temperature children.
When I look at the device it does show the correct number of âendpointsâ.
Any ideas?
you need to exclude the device then add connect the temperature probe then add it back to you ST environment. unfortunately you canât just add a probe to an existing device it wont work (it tells you this in the manual).
Have a look in the log when you open and close the contacts (look at the parent device) and make sure you see both open and close on each input. I have a issue recently (something to do with ST) that input one only logged opens and input two only logged closes.
For the device which I was adding the temperature sensor I removed it, reset (power off, hold B button power on, wait 10 seconds, release B and power off and on) the added again. So now I have no temperatures.
I have been looking at the parent device, only the first contact changes.
Do you see any errors in Live Logging on the IDE? Or do you see anything there about the other contact sensor/temperature sensors?
The wires on the Binary sensor are really thin and a bad contact will have unusual results. I had one show 0 degrees every other report. I re-made the termination and I got consistent results again. Could be this. The other issue could be a bad sensor. Maybe try adding one at a time, remembering to exclude and include each time.
It only triggers for the first channel
f7e52b64-bb49-43bf-955d-e37e1e4e8dc9 1:00:17 PM: debug parsed 'zw device: 21, command: 2001, payload: 00 â to result: null
f7e52b64-bb49-43bf-955d-e37e1e4e8dc9 1:00:17 PM: debug BasicSet V1 BasicSet(value: 0)
f7e52b64-bb49-43bf-955d-e37e1e4e8dc9 1:00:14 PM: debug parsed 'zw device: 21, command: 2001, payload: FF â to result: null
f7e52b64-bb49-43bf-955d-e37e1e4e8dc9 1:00:14 PM: debug BasicSet V1 BasicSet(value: 255)
Nothing happens when I trip the second channel.
Iâve double checked the wiring against the one I havenât touched and everything is identical. Its unlikely to be the sensor as it would have to be 8 duff ones 2 of which were fine yesterday.
Maybe go into the settings and have a look through to see if anything is not configured/disabled/⌠Youre only getting the V1 commands and not the V3 ones (which are needed for temperature and contact 2). Strange
The working and none working modules are identical except for parameter 10 isnât the default 20s, Iâd extended it to 120.
I assume the endpoints is the total number of contact plus temperature sensors. They are correct.
Iâm still trying to figure this out. Iâve realised that I canât see anything change on the parent device. It is only the child device of the first input which changes. Anyone got any ideas?
Strange, what do you see on live logging when filtering for that device over a period of a couple of minutes?
The list event for the parent device shows nothing. The live logging only sees the one input. I know both inputs are wired correctly as the outputs are both seen by my alarm. I also assume the âendpointsâ is the total of the inputs and temperature sensors which appears correct.
Something is messed up for sure. IMO exclude again, make sure none of the related devices existed and if still there delete. Then run a Z-wave repair to make sure device 21 is gone. Then include again. Maybe even refresh the DTH for both parent and child?
Yes, if you dont see something like this in live logs then it hasnt been included with the temperature sensors detected. (the 0 degree numbers are because I have currently got the temperature sensors disconnected, but the status events still come through)
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug parsed 'zw device: 0E, command: 600D, payload: 04 04 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug temperature2 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 4, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 4, command: 5, commandClass: 49, bitAddress: false)
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug parsed 'zw device: 0E, command: 600D, payload: 03 03 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug temperature1 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:38:44: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 3, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 3, command: 5, commandClass: 49, bitAddress: false)
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug parsed 'zw device: 0E, command: 600D, payload: 04 04 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug temperature2 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 4, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 4, command: 5, commandClass: 49, bitAddress: false)
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug parsed 'zw device: 0E, command: 600D, payload: 03 03 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug temperature1 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:35:38: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 3, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 3, command: 5, commandClass: 49, bitAddress: false)
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug parsed 'zw device: 0E, command: 600D, payload: 03 03 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug temperature1 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 3, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 3, command: 5, commandClass: 49, bitAddress: false)
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug parsed 'zw device: 0E, command: 600D, payload: 04 04 31 05 01 44 00 00 00 00 ' to result: null
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug temperature2 has changed to 0.0
b259537a-a90f-4411-95ba-20b1670e2173 22:32:01: debug ZWaveEvent V3 MultiChannelCmdEncap(destinationEndPoint: 4, parameter: [1, 68, 0, 0, 0, 0], sourceEndPoint: 4, command: 5, commandClass: 49, bitAddress: false)Iâve excluded, done a z-wave repair and re-added the UBSs again. It now appears that on both parent devices they initially see the device on the events list but nothing afterwards.
I can create child devices for the contacts and Contact 1 works but contact 2 doesnât.
On the live logging the only thing I can see is V1.
How close to the hub are you when re-pairing? Perhaps it is failing on a security thing and thatâs why v3 isnât working.