Can you set logging to need help on the zone?
Just did enable, and here's the initial logs:
app:2002019-09-11 11:15:27.599 pm infoDone init
app:2002019-09-11 11:15:27.598 pm infozoneEvaluate: --EXIT
app:2002019-09-11 11:15:27.582 pm debugzoneEvaluate: HVAC Zone 3 Master Bedroom
Mode: IDLE
Setpoint: null
Temp: 76.7
Vent 3 Master Closet: null
Vent 3 Master Window: null
Vent 3 Family Bathroom: null
app:2002019-09-11 11:15:27.581 pm debugzoneEvaluate: ventmode: IDLE
app:2002019-09-11 11:15:27.580 pm infoRunning zoneEvaluate
app:2002019-09-11 11:15:27.565 pm debugGetting Vent Vent 3 Family Bathroom
app:2002019-09-11 11:15:27.550 pm debugGetting Vent Vent 3 Master Window
app:2002019-09-11 11:15:27.533 pm debugGetting Vent Vent 3 Master Closet
app:2002019-09-11 11:15:27.527 pm debugGetting All Vent Opening
app:2002019-09-11 11:15:27.496 pm debugGetting House Thermostat State and evaluating zone
app:2002019-09-11 11:15:27.491 pm debugGetting current Zone Temperature
app:2002019-09-11 11:15:27.488 pm debugGetting Thermostat Cooling Setpoint
app:2002019-09-11 11:15:27.483 pm debugGetting Thermostat Heating Setpoint
app:2002019-09-11 11:15:27.474 pm debugGetting local virtual Thermostat thermostatMode
app:2002019-09-11 11:15:27.465 pm debugSubscribe to Tstat
app:2002019-09-11 11:15:27.453 pm debugSubscribe to vents
app:2002019-09-11 11:15:27.440 pm debugSubscribe to tempSensor
app:2002019-09-11 11:15:27.432 pm infoInit
app:2002019-09-11 11:15:11.092 pm infoYou are using the current version of this app
app:2002019-09-11 11:15:01.255 pm infozoneEvaluate: --EXIT
I have a virtual thermostat configured for this zone which also uses the official ecobee sensor
Current States
- coolingSetpoint : 69.0
- heatingSetpoint : 66.0
- supportedThermostatFanModes : [auto, circulate, on]
- supportedThermostatModes : auto
- temperature : 69
- thermostatFanMode : auto
- thermostatMode : auto
- thermostatOperatingState : idle
- thermostatSetpoint : 66.0
Do your vent device pages show a level? Also, do a move from the device page and see if the log picks it up.
vent device doesn't show a level, and the setLevel command box is blank.
Ok, put 10 in the set level and hit the button. That should show move it and put in a level.
I hit the config button (before seeing your request) and it did pick up the log:
dev:2392019-09-11 11:27:37.083 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object (parse)
dev:2392019-09-11 11:27:37.034 pm infoVent 3 Master Closet battery is 100%
dev:2392019-09-11 11:27:35.990 pm infoVent 3 Master Closet is on
ok, put 10 in setLevel:
dev:2392019-09-11 11:29:06.586 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object (parse)
dev:2392019-09-11 11:27:37.083 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object (parse)
dev:2392019-09-11 11:27:37.034 pm infoVent 3 Master Closet battery is 100%
dev:2392019-09-11 11:27:35.990 pm infoVent 3 Master Closet is on
Oh, that is a device error! Dev:239... Keenect isn’t throwing that error.
I’ve had this happen before. I did a exclusion of the vent and re included it. Changed out the batteries at the same time.
Ugh, all 18 vents. brb
All? Ok, there is a bigger issue here... turn on logging on the vent.
I forgot about this too!
switched to the vent that's right next to me...put 10 in the setLevel box after saving Enable debug logging and got the following:
dev:2452019-09-11 11:36:19.238 pm warndescription logging is: true
dev:2452019-09-11 11:36:19.237 pm warndebug logging is: true
dev:2452019-09-11 11:36:19.235 pm infoupdated...
dev:2452019-09-11 11:34:58.404 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object (parse)
I initially had all vents hooked up to the keen hub for a day, then unplugged the hub, and starting pairing them with HE -- pushing the black button on the vent 5 times to initiate the pairing sequence. HE sees them, and paired all 18 with no issues.
Change the vent device type to a generic zigbee dimmer. Chang the level. Change type back to keen vent. See keen vent issue post.
Just saw that in your referenced thread:
That worked. The level reported while a generic zigbee, and then continued to report it when changed back to keen smart vent. That's a weird one. Thanks for your assistance tonight.
No problem, have fun fixing that 18 times!
@npalmcsr in my tile image above, do you know what the SetPoint is referencing? I'm guessing that it's either the heatSetPoint or the coolSetPoint, baesd on what the hvac system current mode is?
That is correct, it will get populated when your system either heats or cools. Then it will use the virtual thermostat hot or cold setpoint.
I've set up a RM-4 that will set my virtual tstats if humidity is high
Humidity of Ecobee Thermostat, thSensor BR Bridget, thSensor BR Sammy, thSensor BR Ellie(82, 70.17, 54.24, ?) any is > 60 TRUE
set Mode: cool --> Cool: 67 --> Fan: on
Works (these vents on HE rock, so cool -- makes my one zone whole house HVAC into a system that will, er, IS keeping the whole house even rather than having cold rooms -- yay).
Q: I guess this might be a RM and vTstat question, but once my rule becomes FALSE, will the default values repopulate the virtual thermostats? Or will I need to put an ELSE statement in my rule saying to load the default vars into each virtual tstat? (Do you know if there's a way to say "default settings" or would I need to copy all the default settings into the RM to reset them programmatically?
Thanks.
