The routes listed have a time to live, so in order to get the current states, refresh that page while sending a command from the zen driver page...
I sent a refresh command and then immediately refreshed the Child and Route page. It still does not show up there, but the Zigbee Logs do show the thermostat. That is why I asked it that indicated that it is connected directly to the Hubitat C4 instead of through one of the repeaters.
did the command actually execute on the thermostat?
I repeated the experiment, this time changing the cooling point. I saw it change quickly before I could even change to the tab for the Child and Route info. It still does not show up there.
I changed it a second time and looked again. Refreshing the Child and Route info still does not show the Zen thermostat, but I see it in the Logs and Zigbee Logs.
despite whatever the child and route info page says or doesn't say, if the device is responding to driver commands "quickly", there's nothing else that needs to be done.
Last you reported it was taking 5 seconds to report commands, now its "quickly", so it seems whatever route the thermostat has now is better than the last one it was using.
1 Like
Agreed. It also seems to be following the schedule and the away/home settings in the Thermostat Scheduler that was not consistently happening before. I'll have to see if it continues to behave though before I can consider the problem resolved.
Is there a resource for interpreting the log entries? Here is an example from the Zigbee Logs:
Zen Thermostat 19-06-24 21:08:33.689 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:254, lastHopRssi:-79
For example, what does lastHopLqi:254, lastHopRssi:-79 mean?
From an invaluable source of Zigbee info:
Target RSSI and SNR values
Two key values presented by mapping software are RSSI (Received Signal
Strength Indication) and SNR (Signal to Noise Ratio). The RSSI and SNR
reported for each AP in the wireless network tell you how strong the signal
from each AP is, usually updated in real-time.
As a general rule, good target values to have for reliable wireless
connections used in a NetLinx control system are:
• An RSSI value between -55 and -78 dBm
• An SNR value greater than or equal to 18 dBm
2 Likes
Thank you! This is very helpful. A quick glance lets me know that I need to relocate my two Hubitat hubs.
I relocated both my C4 and C5 hubs. Initially, the Rssi seemed to be in the low-to-mid 70 range. However, it has also climbed as high as 85 this evening. Why? I don't have a clue. I can't explain it, nor why the thermostat would change temperatues from away to home settings properly as specified in the Thermostat Scheduler, but then will switch the cooling setpoint to the away temperature again even though we are still both at home.
To say that it is frustrating would be an understatement. I just sent a message to support to ask why this is happening and how to fix it.
@mike.maxwell I had sent a support request but used a different email address. I received the automated reply but did not hear back. I just sent a support request using the email address I used for registration, so hopefully, I will hear back soon.
Here is the situation again. This morning, the thermostat changed (properly) from my nighttime settings to the daytime settings. Eight seconds later, the cooling setpoint changed back to the nighttime cooling setpoint but the heating setpoint stayed at the daytime setting. This is getting extremely frustrating! I changed thermostats because of this issue with the CT101 Radio Thermostat, thinking it was the Z-Wave that was the issue. Given that the Zen Thermostat is Zigbee tells me that it is not the thermostat that is the problem. Something is off in the Thermostat Scheduler or how the Hubitat sends that commands to change and receives confirmation that it is done. I don't have the skills needed nor the tools needed to figure this out.
Here is what I sent this morning:
Why is my thermostat not following the Thermostat Scheduler rules? Why is it changing from my daytime temperature for cooling back to my nighttime temperature? Here is an excerpt from my log:
|coolingSetpoint|74.0|°F|Zen Thermostat coolingSetpoint was set to 74.0°F|DEVICE||2019-06-28 07:30:11.576 EDT|
|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-06-28 07:30:03.830 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-06-28 07:30:03.829 EDT|
|heatingSetpoint|70.0|°F|Zen Thermostat heatingSetpoint was set to 70.0°F|DEVICE||2019-06-28 07:30:02.320 EDT|
It changed properly from 74F to 76F, but then 8 seconds later, switched back to the 74F setting.
Parent child parameters EzspGetParentChildParametersResponse [childCount=1, parentEui64=0000000000000000, parentNodeId=65535]
Child Data No information for Child 0
Neighbor Table Entry
[MBR CF Dimmer, 00B5], LQI:254, age:3, inCost:1, outCost:2
[LR CF Dimmer, 7315], LQI:254, age:3, inCost:1, outCost:1
[Iris MBR V2 Outlet, 9F91], LQI:255, age:3, inCost:1, outCost:1
[Iris LR V2 Outlet, D36F], LQI:255, age:3, inCost:1, outCost:1
Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [Stephen's Smart Fob, 74CB] via [Iris LR V2 Outlet, D36F]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Iris MBR V2 Outlet, 9F91] via [Iris MBR V2 Outlet, 9F91]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bosch Kitchen Motion, 2726] via [LR CF Dimmer, 7315]
status:Active, age:64, routeRecordState:0, concentratorType:None, [LR CF Dimmer, 7315] via [Iris MBR V2 Outlet, 9F91]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kitchen Light, 1E3A] via [LR CF Dimmer, 7315]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bosch CR Motion, 5E3B] via [Iris MBR V2 Outlet, 9F91]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bosch Sewing Room Motion, 871B] via [MBR CF Dimmer, 00B5]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bosch LR Motion, 9ACF] via [LR CF Dimmer, 7315]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bosch MBR Motion, BBA7] via [MBR CF Dimmer, 00B5]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Iris LR Keypad, EB53] via [Iris MBR V2 Outlet, 9F91]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Iris Kitchen Door, AA7D] via [Iris LR V2 Outlet, D36F]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Zen Thermostat, BF93] via [Iris MBR V2 Outlet, 9F91]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Panic Button-MBR, FDC0] via [LR CF Dimmer, 7315]
status:Unused
status:Unused
status:Unused
Zigbee Log entries:
Zen Thermostat2019-06-28 11:11:02.750 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.547 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.344 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-69
Zen Thermostat2019-06-28 11:11:02.241 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.136 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.134 profileId:0x104, clusterId:0x1, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.019 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-69
Zen Thermostat2019-06-28 11:11:02.017 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:02.009 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:01.895 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:01.879 profileId:0x104, clusterId:0x202, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:01.776 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:01.773 profileId:0x104, clusterId:0x201, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Zen Thermostat2019-06-28 11:11:01.657 profileId:0x104, clusterId:0x1, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-68
Does the clusterid: 0x1 mixed in with the clusterid: 0x201 have anything to do with this? I have moved my Hubitat C4 to different locations to try to get the best Rssi possible. I have seen the signal strength change also from the values listed above to values in the -80-85 range, even without moving anything. I can't figure out why it changes. My WiFi is set to channel 1 with a 20MHz limit set in the router. The C4 Hubitat is set to Zigbee channel 20 and the C5 hub is set to Zigbee channel 25.
I changed from the CT101 Radio Thermostat because of this issue, thinking it was the Z-Wave that was the problem and since I have many more Zigbee devices, that this would help. Apparently, I was mistaken. Is this a problem with the C4 Hubitat's radio dongle? Is it a problem with the Thermostat Scheduler app? I need this to work without me babysitting it and refreshing the thermostat when it misbehaves. When we travel, that is not possible.
Respectfully,
Stephen
Please post a screen shot of thermostat settings (open the app, post screen shot)
Close the app, then from the apps page, select the gear in the info column, post a screen shot of that as well.
1 Like
Four screenshots attached. The thermostat device page is the first, but I had to take 3 to get all of the app page.
I also need a screen shot of the first page of thermostat scheduler, not the actual thermostat.
If possible a higher resolution image would be helpfull
what I'm trying to do here is run some tests using the exact configuration you have, given you had the exact same results with two different thermostats, it would appear that the thermostat(s) aren't the issue, but I'm not ruling that out just yet...
Thanks. I appreciate it.
Could you please add one more screenshot? The "Device Details" section of your thermostat (click the gear icon next to your thermostat on the "Devices" page, and then scroll down on that page to locate "Device Details" section).
ok, thanks, as an FYI both bobby and I weren't able to replicate this issue using a virtual thermostat, and bobby tested it with his Nest and in all three cases things worked as expected.
My Zen is in production right now, but tomorrow I'll pull it into dev and get to testing with the actual device on Monday.
Also, on your Zen, did you set any of the advanced configuration settings?, or did you just do the basic configuration, I ask as Auto mode only works if its enabled in the Advanced param section, and so far I've found it to be a bit funky...
1 Like
I followed the online Zen setup guide but did not go into the advanced settings since I thought that Hubitat's Thermostat Scheduler would be handling those things.
Here is something interesting:
At 17:32:06, the cooling setpoint is in the log as 76. At 19:31:21 the temperature is 78.1. This is while we were away so the cooling setpoint should have been set to 80, which is may have been given the temperature. At 20.51.10 the heating setpoint shows it being set to our home setting since that is our arrival, but the cooling setpoint shows it being set to 79.9. A second later at 20.51.11, the cooling setpoint is changed to the proper home temperature of 76.
As Alice said, "Curiouser and curiouser!"
We'll get to the bottom of this...
2 Likes
