-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch off action doesn't work on TYBAC-006 thermostat #403
Comments
Can't you use the state entity to switch on and off? |
Yes I can use the state entity but then I can't use the scheduler crard anymore |
Why not? What type is the state entity? Switch? Boolean? |
It is a switch. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Thanks to not close this issue |
If I understand the bug description correctly, your climate entity does not respond correctly to the climate.turn_off service.
What is meant by this? Services (/actions) are used in HA to interact with entities and devices. There is no alternative. |
It is not really a bug, if you prefer you can call it a feature.
|
I don't think this is possible because the thermostat in question doesn't support this at all and doesn't appear to be a "normal" thermostat. Both the state entity and the eco mode entity are of binary type and are not part of the climate entity. |
Expected behavior
When I use the switch off action in a Scheduler card it will switch of my TYBAC-006 thermsotat.
{
"child_lock": "UNLOCK",
"current_heating_setpoint": 20,
"deadzone_temperature": 1,
"eco_mode": "OFF",
"fan_mode": "low",
"linkquality": 188,
"local_temperature": 22,
"local_temperature_calibration": -2,
"manual_mode": "ON",
"max_temperature": 25,
"max_temperature_limit": 18,
"min_temperature": 10,
"min_temperature_limit": 30,
"schedule_friday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_monday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_saturday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_sunday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_thursday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_tuesday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"schedule_wednesday": "06:00/20.0 11:30/20.0 13:30/20.0 17:30/20.0",
"state": "ON",
"system_mode": "heat",
"valve": "CLOSE"
}
Actual behavior
The scheduler send the service: climate.turn_off action but does nothing on this thermostat because it expected "state": "OFF"".
Is it possible to have the choice to use state instead of service to turn on and off a climate device ?
Is it possible to add the ECO mode too ?
The text was updated successfully, but these errors were encountered: