I have two units in my house and have been using two TH6320ZW2003 model t-stats with Thermostat Controller. They are on different firmware and I found one to be VERY chatty any time the fan was running (with heat, cool or just fan on).
FW 01--04--09--00 Date 2204 = chatty
FW 01--04--05--00 Date 2135 = less chatty
This would cause me to get spammy device alerts and general delays or dropped Z-Wave traffic
Since the firmware cannot be changed, I decided to track down a TH6320ZW2007 and it came with
FW 03-01-00-00 Date 2404
I am using the advanced driver from HPM.
Cooling cycle with TC disabled looks to be around 11 events and very little traffic in the Z-Wave logs:
TC settings:
I changed the fan mode to circulate and then the events start repeating over and over:
Why does TC keep setting the SetCoolingSetpoint over and over?
That goes on over and over until the fan is no longer running. Several times a min while the Z-Wave logs just roll
This causes delays or failures of other Z-Wave traffic since there is so much traffic just with the t-stat.
I have deleted my TC app in the past and rebuilt it from scratch.
Any other ideas? It seems pretty easy to point the finger at the Thermostat Controller app at this point.
Why are you even using Thermostat Controller? It appears that you are trying to use it to control the thermostat without using any other sensors. That's not the intended use at all.
Does that prevent it from working correctly though? I am trying to keep it simple at this point for troubleshooting. Once stable, I will be adding other temp sensors to be averaged.
Can't tell from what you've posted what is going on. Please show the app logs.
Also, it would be helpful if you explained in detail what you are wanting to accomplish.
I am wanting to have the thermostat controlled by the thermostat controller app with 4 temp sensors being used. The t-stat, two ZigBee temp sensors and a Z-Wave temp sensor. When having it all configured before, the t-stat wave traffic was overwhelming the Z-Wave network and the temp sensor updates were not getting back to the hub and cooling ended up running for 2.5 hours until I got back home and manually changed the temp. So I removed the other temp sensors for now.
Here are some logs while the system was idle:
Here the temp rose enough to call for cooling:
Then it just repeats:
I suspect this is the problem. Your driver is posting temperature events that represent no change of value. which should not be happening. Please switch to the built-in driver and see what happens. It's hard to see what's happening beyond the fact that the thermostat keeps reporting temperature values when it should not, and that TC responds accordingly. That's the apparent source of all of the unwanted Z-Wave traffic.
1 Like
@thebearmay Is there anything you can do in your driver to help with this. I much prefer all the options that your driver provides over the built-in Honeywell T6 driver.
@bravenel Which of the 3 System options do you want me to test with? The Honeywell T6 Pro Z-Wave Thermostat driver, the Generic Z-Wave Thermostat driver or the Generic Z-Wave Plus Thermostat driver?
Make sure this value is greater than zero.
2 Likes
Mine was set to zero. I set it to 1 and am still seeing a LOT of events. What is the scale there and range of values? On the actual T-stat I have reporting set to .5 F & 2% for humidity in the Z-Wave settings. Based on the reporting neither of the values are changing that much, so why does it keep reporting?
App logs from TC:
Device logs from T-stat with your driver:
Device events from t-stat:
Device logs filtered to just errors during a cooling cycle:
1 = 1°
I'll look into the errors, but a couple of observations -
- Judging by your event log it looks like your humidity reporting delta is set to zero, consider bumping it up a few percent
- Your battery reporting is excessive (every 4 seconds) - at a quick glance I don't see this as being controlled by the driver so may need to adjust on the device.
1 Like
In your driver I had humidity set to report on 2 and also on the T-stat directly. I do not see any ISU code for battery reporting at all. It only reports the battery value in the logs when the unit is running and the events are showing temp and humidity reports.
Hmmm... Do you have the thermostat on battery only or do you have it on both battery and red wire 24v?
Both battery and 24V. It reports powerSource as mains and that will change to battery if I remove it from the mount or the power goes out.
When you paired it did you pair it with the batteries in or out?
I am not sure now. It does show up as a Z-Wave repeater.
I changed the driver to the system Honeywell T6 driver and it is on a cooling cycle right now. It looks like it is honoring the temp and humidity settings and no battery reports are showing
Device logs:
Device events:
I only asked as I paired without batteries to ensure it was a repeater then inserted batteries. I've always used @thebearmay's driver on both my 500 version and current 700 version and not had the battery reporting issue in the logs. It only starts reporting battery when mains are disconnected.
Mine looks like that as well
Using the system Honeywell T6 driver or the Generic Z-Wave Plus driver does not show the battery reporting and events are WAY down. N Hallway is running your driver on my less chatty T6 firmware. S Hallway is running the Generic Z-Wave Plus driver.
I would prefer your driver for reporting the fan operation state and allowing me to change the backlighting at least.
Do you think removing and adding back with no batteries installed would have any effect like Rick mentioned?
It's definitely worth a shot.
No joy. I excluded, removed the batteries, included, replaced the batteries and when the fan or compressor is running I get overwhelming battery reports and a few errors.
