Skip to content

Clean up the responsibilities for updating properties #15

@olefriis

Description

@olefriis

Updating properties is a bit of a mess right now. It's probably not a huge problem, since we only have three properties we can write back, but it'd be nice to streamline that code a bit.

Should the new values be stored in a human-readable format (like degrees Celcius for the set-point temperature) or the thermostat's format (like raw numbers for schedule mode)?

Can't we tighten the logic for reading, updating, and writing back characteristics?

Where should the code for parsing the input to the set command be?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions