What is the appropriate syntax for the window_room attribute for multiple rooms?
None. The code just checks if any binary sensor having a window_room attribute is on and returns the OFF overlay in this case.
If you need more fine-grained control over which sensors to include, you could of course introduce another attribute for all sensors to add to the hallway, e.g.:
customize:
binary_sensor.window1:
window_room: living
hallway_window: true
And then filter for all binary sensors having hallway_window=True using the filter_entities() state helper, the same way it’s done in the official open window detection example, just that you filter for another attribute which is common among all sensors to include in the hallway.
I don’t know if I’m just retarted or a glitch.
I have separate genetic thermostats and separate schedy apps for both my heating system and my cooler.
They are both set up the same except for ac_mode: true for cooler. and ac_mode: False for heater.
schedy is working fine and like I expect it too as far as schedule and following rules of input select, input boolean and then schedule_append if the thermostat is changed manually.
What I just noticed on my cooler thermostat is the COOL icon is Grey like it is OFF.
it turns blue if I click on it but when schedy changes anything it goes back to Grey but all is working like is should and cooler is running.
2020-06-03 13:19:46.995942 INFO schedy_cooling: --- Actor type is: 'thermostat'
2020-06-03 13:19:47.019536 WARNING schedy_cooling: !!! [R:living] [A:climate.cooler] Thermostat doesn't seem to support the HVAC mode heat, supported modes are: ['cool', 'off']. Please check your config!
2020-06-03 13:19:47.038073 INFO schedy_cooling: --> [R:living] [A:climate.cooler] Received value of 73.0��.
2020-06-03 13:19:47.231496 INFO schedy_cooling: *** Initialization done.
2020-06-03 13:19:47.242971 INFO schedy_heating: *** Welcome to schedy 0.8.3, running on AppDaemon 4.0.3.
@Rod_Poplarchick Schedy sets the hvac mode to heat, which is, as logs say, not supported by the cooling thermostat. You just need to tell it that the hvac mode to use in operation is cool. This is a setting of the thermostat actor type, and hence can either be set in an actor template or directly for a single actor. See here.
I’m still don’t understand what you are saying.
I set it to true and it is working
Just the switch shows off and as heat.
Where and what setting do I need to change?
@Rod_Poplarchick Climate entities in Home Assistant can be set to different HVAC modes, which, depending on the type of climate device, can be heat, cool, off, auto etc. This has nothing to do with the ac_mode setting of the generic thermostat platform you’re mentioning.
When Schedy sends a temperature to a climate entity, it also has to specify which HVAC mode to use. Now, by default, this is “heat”, as the docs I linked tell you. Your climate, however, doesn’t support the heat mode, which is expected since it’s an AC device and not a heater. Therefore you have to configure Schedy to send the mode “cool” instead, which you do by setting hvac_mode_on: cool in the actor configuration in Schedy.
thanks again for trying to help a dumb ass
I tried that after your first reply and just did it again.
I restarted HA and Appdaemon and still get the not supported error.
its working fine and adjusting the thrmostat just that the actor or generic thermostat shows off and the entity show heat
@Rod_Poplarchick Not quite in the right place. It has to be set under the actor, because it’s an option specific to the actor, not for Schedy in general.
So either add it under the specific actor, or in the default actor template if you need to set it for all actors in this Schedy instance.
actor_templates:
default:
# Here all settings to set for all actors
thank you that did the trick.
now I just need to figure out how to set my headtng schedual to be off from april to Sept.
im no programer so it takes a lot to wrap my head around some of it . I have to see the code then i understand,
To have Schedy not set any value, return Abort() from the schedule, possibly in the schedule_prepend section and restrict that rule from April to September, for instance.
EDIT: Or maybe better make it depend on an input_select that controls whether the heating or cooling instance should be active.
I have a binary_sensor that I manually control for summer then monitor it and check it in the schedules - I probably should do a prepend in schedy. I also do the same for School Holiday periods when the patterns of people in the house change (e.g. we get up later).
Indeed, conditionally returning Abort() from the prepend section is what you want to do. Just insert a rule that returns Abort() whenever the schedule should be ignored, e.g. during summer using the months constraint, or depending on the state of an input_select or whatever. There are examples in the docs on how to use Abort(). Just try it.
I don’t use it - it just might simplify things. Just one of the rules in each switch says, is the binary sensor set if so do whatever if not do the other things.
