-
Notifications
You must be signed in to change notification settings - Fork 45
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
Heating actuator #340
Comments
Hmmm seems one of your heating actuators shows different data to the other. It should not have created the climate and number entities for any of your heating actuators as you do not have floor temp sensors. I have fixed that for the next update. Thanks for the help. The attributes have to be on an entity not a device. Maybe we should create a sensor entity for the heating actuator. Will put it on the todo list. |
No problem for French screenshots! I think this is now fixed in the dev branch, if you could try for me. Thx |
Thank you Mark, |
The issue is fixed by the version 3.2.3beta3 |
Will close for now. |
As I installed the 3.2.3beta , the integration create climate.wiser_heatingactuator_salle_salon_floor_temp and number.wiser_heatingactuator_salle_salon_floor_temp_offset for one heating actuator but not for the others
Very good idea to create an device heatingactuator! for me it should be nice to migrate the attributes temperature, target_temperature, output_type from "Wiser heatingactuator xxx signal" to the device.
config_entry-wiser-d2b5e58746bb2e3c81e153fe19a017cf.json.txt
The text was updated successfully, but these errors were encountered: