You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.
a "dumb" high level application that currently simply dump the raw data
an MQTT publisher (I did not look into this but I am familiar with MQTT; I guess you publish something)
I usually like to have the library in a separate project but I am ok with the way it is know unless the dependencies for the non library stuff is not too long...
Anyway, the suggestion I wan to make is to create a "smarter" high application that abstract away the low level and spit out some high level information on screen (formated and/or JSON) and/or in a JSON file. The abstraction should actually be in the library since I suspect the MQTT stuff will definitely benefits from that as well. The benefit of having this high level application is to make the project useful for other that do not want or do not care about MQTT.
As for high level abstraction, considering that what most people are interested is to know if a peek period is pending or not I suggest this list:
1 - what is the current type of "moment", i.e
- nothing special
- morning prestart for non peek days
- morning peek time for non peek days
- afternoon prestart for non peek days
- afternoon peek time for non peek days
- morning prestart for a peek days
- morning peek time for a peek days
- afternoon prestart for a peek days
- afternoon peek time for a peek days
2 - is the next day going to be a peek day or not (the heating inertia of my home is so large that I usually need to start adjusting the previous evening...)
At this moment I do not see other high level abstracts for home automation reasons, however, I guess the hourly consumption report to JSON file would make sense (in append mode obviously, which means to use line-delimited JSON records format).
The text was updated successfully, but these errors were encountered:
As you can see I already took some items off your list.
I have tried to separate high level / low level and I suppose the lib for low level can be cloned and reused (be my guest anyone :) )
My goal right now is to sort out the winter credit stuff and I think we're getting something acceptable (not great but workable)
For the future I'd like to integrate energy consumption in my home automation system and I will likely do that around here.
I'm open to other integrations and if it becomes easier we can always split some parts in other repos.
I would like you to pitch in in the discussion @mdallaire opened as you seem to have a rather different setup than we do (if you're willing to share obviously)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As I see it, there are 3 things in this project:
I usually like to have the library in a separate project but I am ok with the way it is know unless the dependencies for the non library stuff is not too long...
Anyway, the suggestion I wan to make is to create a "smarter" high application that abstract away the low level and spit out some high level information on screen (formated and/or JSON) and/or in a JSON file. The abstraction should actually be in the library since I suspect the MQTT stuff will definitely benefits from that as well. The benefit of having this high level application is to make the project useful for other that do not want or do not care about MQTT.
As for high level abstraction, considering that what most people are interested is to know if a peek period is pending or not I suggest this list:
1 - what is the current type of "moment", i.e
- nothing special
- morning prestart for non peek days
- morning peek time for non peek days
- afternoon prestart for non peek days
- afternoon peek time for non peek days
- morning prestart for a peek days
- morning peek time for a peek days
- afternoon prestart for a peek days
- afternoon peek time for a peek days
2 - is the next day going to be a peek day or not (the heating inertia of my home is so large that I usually need to start adjusting the previous evening...)
At this moment I do not see other high level abstracts for home automation reasons, however, I guess the hourly consumption report to JSON file would make sense (in append mode obviously, which means to use line-delimited JSON records format).
The text was updated successfully, but these errors were encountered: