Yes you are reading those settings correctly. Bear in mind though that even when a reading is set to SmartThings, WebCore will only see an event if it changes. I had my sensor setup for every 30 seconds and now it is set for every 5 mins. There is no point sending lots of updates with no new information. It just adds to the Z-wave traffic.
First thing is to Check the temp reading is correct. then look at the frequency you want it updated.
The device handler receives it every interval (see screenshot in the logs for temperature1, not temperature2 which is highlighted but actually oscillates a bit), but you cant update the file given no update is needed. You could modify the handler if you wanted with a timestamp and that way see the updates are still coming through.
ah, cheers. sounds like the solution is a modified handler then, but itās beyond me Iām afraid. Is this something anyone would be interested in doing, or am I the only one who will get any use out of it?
cheers all!
For a quick fix, add this line to about 407 in the device handler - just before this line log.debug "{tempendpoint} has changed to {tempprocessed}"
if (tempprocessed.toString() == device.currentValue("${tempendpoint}")) {tempprocessed = (tempprocessed + 0.1).round(1)}
It will basically lose you a bit of accuracy but will ensure the readings update every interval, by adding 0.1 degrees to the temperature if it exactly matches the previous reading. The next reading it would revert back assuming the temperature had still not changed.
thank you very much !
worked ! ta
Any ideas why this happens? The delayās seem a little unpredictable. 3, 14, 3, 7 min gaps with my current settings. Entirely possible Iām missing something obvious : p
Hereās the settings for the DTH:
P11 is set to 200 (approx 3.5 mins).
Iām not trying to be anal, Iām just trying to understand - sorry about the agitating questions!
Essentially Iām attempting to understand so that I can disable the central heating to certain areas if thereās a fault (for whatever reason) with one of the probes. Cheers!
Canāt see your logs, just the device history which is quite different.
However I also do think this performance is fine, sensors donāt normally just stop responding unless the wires/sensors break - which is very rare, and using this as a failure detection isnāt going to get called on very often.
thanks cjcharles.
Not being ignorant, so thought Iād say ācheersā, but Iāve got nothing interesting to add to this for now = p
Iām currently almost finished testing a potentially messy ādiagnosticā, involving a periodic timer and some simulated switches. All in webcoreā¦
I meant to look at the device history properly you need to look at live logging to see whether the 200s interval is being properly managed, since I would expect the modification above to totally fix things
Iām stuck prepping for new baby (any day!), so time is limited. Havenāt had a chance to check on this properly, but Iāll have a play at some point and report back.
fix is working brilliantly though, cheers !
Hi @cjcharles
Apologies if this is a stupid question - I am in the process of migrating from Zipato to ST so still getting to grips with things.
I am using the V3 hub and new app and I have a bunch of these universal sensors and not managed to get them to work yet. I pulled the latest code from your github and created a device handler - then added the device as a generic Z-wave device, then swapped to your DTH in the IDE. the app looks like this:
Am I doing something wrong here?
Thanks
You should use the classic app to setup the main device and create the child devices. Then it should show correctly in the new app.
Smartthings have only just provided a little bit of guidance on getting things working in the new app, at least I think they have! So Iāll need to look at that at some point!
Thanks Simon!
Just gave that a try - used the new app to add the device, the classic app to add two child devices, then back to the new app, wake the device, and the sensor is reporting. I am not getting anything from the temperature sensor though. I tried clicking Add Temperature Child in the classic app but it did not seem to do anythingā¦
Should I have used the classic app to add the device?
That shouldnāt matter, but you do need to have the temp sensor connected when you pair to Smartthings.
Do you see the temperature in the parent device of the classic app?
The sensor is connected as just moving the device over from my Zipatile.
I dont see a temperature in the classic app. There does not appear to be a child device for temp showing in the IDE either. I will try deleting it and re-adding
You should see it on the temp field on the parent device, if you canāt see it there it wonāt create any children devices.
If not then you may need to look at the live logging to see what might be going onā¦
Hi,
I created the child devices using classic app, but second contact keep being disconnected (with new app).
I used the various DTH versions from this thread and I tried both with parameter 14 enabled and disabled.
Any help would be highly appreciated.
Thanks
Hi,
Iāve switched over to this DTH from an earlier DTH (PukkaHQs) that didnāt seem to play well with the new Smartthings app.
Iāve got the DTH installed and created the child devices via the old app, and everything seems to be workingā¦but the Temperature Sensor type seems to have both humidity and temperature readings.
Humidity is null because there are no readings, but the tiles in Smartthings seem to display the humidity as 0% rather than the temperature, which is useless.
Iāve tried changing the type to various others, like āTemperature Measurement Capabilityā which appear correct in the API but these donāt seem to play well with the tile in Smartthings on the phone (Android) - I just get āChecking statusā¦ā.
What am I doing wrong? Is there a better type?
