kimmoritz / mitsubishi-hvac-controller Goto Github PK

Definition of done: admins and noone else can add and delete users

A requirements.txt file is needed for deployment.

The last sent command should get stored in a table and be visible to a logged in user.

Definition of done: A logged in user can see the last used settings.

Definition of done: a logged in user will be presented with sequentially sorted and last used (or a reasonable default set of) values as defaults in dropdowns in the settings page form.

Definition of done: the HVAC can be turned on and off in settings page, based on what the current state is.

For increased automation of the heat pump, a user needs to be able to schedule commands over the day.

DoD: commands can be scheduled via the web page.

The current requirements file assumes prior installation of pigpio. All needed libraries should be in the requirements.txt file.

Break out code for Mitsubishi and ir modules and add to requirements.txt.

Definition of done: can be installed using requirements.txt and no Mitsubishi code is left in this repository.

In order not to have to manually create tables, do some initialization after check upon startup.

Definition of done: the about route is removed.

Preferably using flask-dance.
Definition of done: a google account can sign up and ask admin for permissions to log in

A circuit schema is needed for instructions of how to set up the hardware.

Python string formatting should be changed in order to improve clarity.

DoD: Keeps track of who is admin

Definition of done: anyone can change their own password.

For production use, any or most important
sqlalchemy compatible database management systems should be available for setup.

Definition of done: a db config file or ui based input allows for specifying db to use.

Some HVAC models have a 4th fan speed. Should be added to controls.