Hi all
i installed the ZTS-100 to replace old thermostat controller. i paired it with vera lite and everything went smoothly, leave everything as default. Recently, i notice that, vera lite didn’t pick up thermostat mode or current temperature correctly. so i wonder if what else that can be done to fix this issue.
i also attaches couple pics to show how thermostat has been setup
anyone?
You posted this less than 24 hours ago. To expect an answer in that time frame is considered rude. Most of the sensor members on this forum will ignore topics with the topic owner bumping the topic in that 24 hour time frame.
What have you tried? Have you tried polling it?
yes. it would update info after manual poll.but that isn’t a fix… showing these info on the vera’s UI5 isn’t important, the thing that i concern the most is automation scene. luup code didn’t work correctly because values that vera pass in are not updated.
i have scene for thermostat that would turn on/ shut off thermostat base on current temperature trigger. for example
turn off thermostat if current temperature hits 23. but when zts-100 shows current temperature at 24 and heat still runs . I check vera, it says current temperature is 20
@Garrttwp: i didn’t know this would be consider rude and i am sorry about that. beside when i bump the thread, it is more than 24hrs.
thank you
My apologize as TapaTalk showed the wrong time on your first post as being 22 hours prior to you bumping the thread.
If a manual poll works reliably, then Zwave communication is probably okay. Did you change the polling interval to blank? My battery-powered thermostats were automatically set at 1080 seconds (that’s 18 minutes!), and the C-wire powered to 60 seconds. Have you tried setting a poll interval, in case the default isn’t working properly? If it’s still a problem, you could create a scene to poll the thermostat on a regular schedule.
it would update info after manual poll.but that isn't a fix.. showing these info on the vera's UI5 isn't important, the thing that i concern the most is automation scene. luup code didn't work correctly because values that vera pass in are not updated.Are you saying that luup values are different than what is displayed in UI5?
First of all, thank you for your help!
Its poll interval was set to 60 ( because I wired it,) before I remove and left it as blank( blank is default to Vera) . However, the info that showed on UI5 didn’t match with what showed on thermostat itself. After manual poll they fix. So I wonder if there is anything else I need do like modify device properties like sensor ( timeout and sensitive). I already look at zits-100 manual on parameter section and don’t really how to use it.
What I say about Luup variable , mean because Vera didn’t have corrective value → Luup code executed wrongly-> scene didn’t run as it suppose to
Ps: if I run Vera from day to day without restart or reload. Would it ever cause any problem to Vera ( mess up Luup code or overload something 
for whatever it would be)
I just noticed that your screen capture shows no neighbors. If that is correct, it might be the cause of your problem. Try Update Neighbor Nodes to see what happens (Device Settings [Wrench] → Device Options tab). If there are still no neighbors, you might need to move Vera closer or add a routing z-wave device in between.
Oh. That’s weird! I have sensor and light switch (z wave type) near it. I dunno what cause this. I would follow your advice once I home and report back.
Thank you so muh again
PS: i update neighbour nodes and here is new screenshot
there few number of node listed as neighbour for thermostat. i also set poll interval back to 60 second and will test for couple day. i will report back after a few day.
Report: so far so good ! vera keep update latest info from thermostat. well, at least that what i see on UI5
but weird thing happen when i run luup for thermostat.
i have a scene with just a luup like this to test out thermostat. and current temperature shows on thermostat is 22.
intentionality, when the scene runs. i should change mode from off to Cool, however, it fails to do so, instead it change current mode to Heat. so i wonder what happen here.
local THERMOSTAT = 4 – The thermostat device numberSES_SID
local StartHeat = 10
local StartCool = 18
local HVACO_SID = “urn:upnp-org:serviceId:HVAC_UserOperatingMode1”
local HVAC_Temp_SID = “urn:upnp-org:serviceId:TemperatureSensor1”
local HVAC_HEAT_SID = “urn:upnp-org:serviceId:TemperatureSetpoint1_Heat”
local HVAC_COOL_SID = “urn:upnp-org:serviceId:TemperatureSetpoint1_Cool”
local current_temp = luup.variable_get( HVAC_Temp_SID, “CurrentTemperature”, THERMOSTAT) or “0”
local status = luup.variable_get(HVACO_SID, “ModeStatus”, THERMOSTAT) or “Off”
if ( current_temp > “StartCool”) then
luup.call_action( HVACO_SID, “SetModeTarget”, {NewModeTarget = “CoolOn”}, THERMOSTAT)
luup.call_action( HVAC_COOL_SID, “SetCurrentSetpoint”, {NewCurrentSetpoint = “20”}, THERMOSTAT)
elseif ( current_temp < “StartHeat”) then
luup.call_action( HVACO_SID, “SetModeTarget”, {NewModeTarget = “HeatOn”}, THERMOSTAT)
luup.call_action( HVAC_HEAT_SID, “SetCurrentSetpoint”, {NewCurrentSetpoint = “24”}, THERMOSTAT)
end
hi all
after a month of try, apparently the vera lite didn’t show thermostat’s temperature correctively. today, i went home, it was so cool. i look at my thermostat it say 12.3 but on UI5 , it says 21!!! could anyone help me to fix this problem, it is winter now!!
on the first picture, UI5’s sceenshot, it shows thermostat’s temperature is 21 HOWEVER the 3_1 sensor which is next to it(it is 1.5m apart), says 12 . it is unacceptable
on the second picture, it is the picture of the real thermostat say 12C.
currently, i have a scene to control this thermostat, but the scene didn’t run as it suppose to because thermostat on UI5 didn’t update its temperature corrective
thank you!
Is there a Z-wave communication problem with the thermostat? Can you poll it successfully? Was there an internal schedule set that might have reduced the temperature?
i don’t think there is some kinda schedule that set to reduce temperature in my zts 100.
i can poll it manually and successfully. every time i do a manual poll, vera got latest statue and temperature of the thermostat.
i dunno if there is z war communication problem or not! i do a stress test and result says ok, average is 200ms
It sounds like Z-wave communication was working when you tested it. However, since UI5 updated to what the thermostat was showing when you polled it, it suggests that maybe there was a problem when they where showing different temperatures. Routine polling wasn’t turned off was it? [Settings: Poll this node at most once every ___].
The picture of your display shows a 1 and 2 (surrounded by squares). I believe this means that the thermostat is calling for 2nd stage heat; so it knows that your temperature is too low. Perhaps there was a power outage that day?
Has this happened again?
I try a few routine poll:
Blank (default) but problem still exists
Set to 60 but problem still the same
Now I set to 300! Testing it this poll routine atm
For [1] is cool set to
[2] is heat set to
[quote=“long, post:16, topic:177672”]Now I set to 300! Testing it this poll routine atm
For [1] is cool set to
[2] is heat set to[/quote]
I’m sorry, but I don’t understand what you are saying. Perhaps you should contact Remotec Tech Support. I found them to be very helpful.
alright., i will contact them thank you
@long - I don’t know how to do LUUP code yet, but I am experiencing the same issue you are having at a more basic level. Have you tried just doing a simple scene using the Advanced tab? In the attached screen shots, you can see that for this scene I switch on both the lamp and the heater (and switch off both 5 minutes later). The trigger for this scene is when the ambient temperature < 70 (fahrenheit).
The scene was only triggered two times:
The scene did not activate even after waiting for over twice the “Poll this node at most once every” period.
The scene did not activate when I did a manual POLL.
Keep me posted on what Remotec has to say. I also have a few tickets open with Vera but they have not replied to any of them yet (one is for this, and the other is for a similar one but this time for the Aeotec 4-in-1 Multi Sensor). It seems temperature triggers are very hard to use!
I’m having similar issues with polling the thermostat. Occasionally, and for no apparent reason, Vera does not poll the temperature. When I go into UI5 and manually poll it, there’s no problem (I see the temperature immediately adjust 2-5 degrees). After following tips in this thread, I’ve adjusted the default poll values from 1080s to 60s and most recently to 30s (see screenshot below).
[url=http://i.imgur.com/AsVjHMM.png]http://i.imgur.com/AsVjHMM.png[/url]
There’s absolutely no issue regarding connectivity as far as I can tell. The Vera is so close to the thermostat that even without any help from the mesh network, it should be able to directly communicate with the it (opposite side of same room…maybe 15ft away).
The only thing I can think of is that the parameter that I’m adjusting is “poll this node at most once every 30 seconds” suggest that the minimum poll interval is 30s rather than “poll the node every 30s” which, to me, would mean actually polling every 30s rather than 30s being the minimum interval. But if that’s so, then where’s this “poll every __ seconds” variable?
I’m a novice with this stuff (obviously), but it seems to me like the issue is on the Vera/Mios side of things since the poll has to be initialized on that side, and the thermostat responds every time I manually poll. Any help is greatly appreciated (might need to dumb it down though).
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules
![http://i.imgur.com/AsVjHMM.png[/url]](http://i.imgur.com/AsVjHMM.png%5B/url%5D){kind=link}