Just started using HA after abandoning Vera. I’m learning the vocabulary, the architecture and the best practices. Very steep learning curve, indeed.
I have successfully got z-wave (beta) up and running. Now I’m getting into automations. My first task is the thermostat. I have a z-wave Trane thermostat but I want to have a day, night and away temperature schedule. The way I had this working on Vera was to have virtual switches (home/away) and variables (Heat SP, Cool SP for each of the three states) The actual heat/cool is part of the thermostat as is fan control.
So I find an integration called sensor which looks like it would work as a variable and another called binary sensor which would work as a virtual switch. I also read about templates but it seems they get their data from other entities or from command line calls.
I suspect that I could make this work with sensor/binary sensor but I want to know it this is best practice? I come up with many questions.
Are sensor/binary sensor efficient (memory, speed etc.)?
Can these sensors be persistent across reboots?
Is there a better choice for persistent, UI (including Alexa) entered data?
If I do use sensor/binary sensor, is there a way to group my sensors as they are clearly related (single display in Lovelace ideal)?
Should I be writing this in Python (it is quite a simple automation)?
Is the climate integration more appropriate?
Note that I also need home/away for completely unrelated automations. Also, I will have other automations that have similar requirements (e.g. intensity of dimmer being configurable for a day/night intensity).
I have checked the forums and looked at docs but did not find my answers. If there is docs (or a forum post) to answer my questions, please just point me there.