Output status

[emdubeu]

The BrewBit team already knows about this one, but I thought I'd add it here, too.

Add functionality to the Model-T that displays the an output's status of either on or off on the web interface. This will provide the user the ability to immediately see what the status is of their connected devices, and the data could also be used for analytics.

[ecotony]

I'd like to add that the display on the BrewBit isn't all that clear as to what it is doing. The color change is hard to detect (at least now, maybe I'll get used to it over time). Maybe a little animation or additional graphics to differentiate?

[hebnern]

Yeah, I agree. There is not enough contrast between the colors (especially for my color blind self). I have been thinking a blinking indication might be easier to see.

[SLOBrewer]

Switching to a different icon rather than blinking would be clearest. Blinking is generally understood to indicate a problem.

[jimmy]

On the original post about web display of output status, I would like to see a line of on/off status showing the status over time, not just the current realtime status.

[emdubeu]

Jimmy, thanks for bringing this back to the original topic; status on the web interface.

[emdubeu]

Maybe something like this:

[hebnern]

Thanks for putting this together. Yeah, something like this would work for the "current status" area. I was thinking we would want to display it on the graph too so you can see how they were switched on and off over time. For that, I was thinking that we could just highlight the background to show when they are on. See here for an example:

http://dygraphs.com/gallery/#g/highlighted-region

(we'd use a less abrasive color of course :))

[emdubeu]

Yea, I like the highlighted area denoting an output was on. Could you make the highlight color red or blue to correspond with the device that was on?

[hebnern]

Yeah, thats what I was thinking too.

[SLOBrewer]

How will that work if both controlled outlets are on?

[hebnern]

They would be different colors depending on what mode they are set to (heating/cooling). If they are set to the same mode, they will always switch on and off together, so wouldn't really need to differentiate them.

[SLOBrewer]

Ah, good point. While there are two outputs the algorithm is always in heating, cooling, or hysteresis mode.

[emdubeu]

I've put together a work around for this feature request. I have a WeMo Insight switch (home automation switch) that the Model-T power cord is plugged into. Whenever the Model-T powers on an outlet, the Wemo switch logs it. I then created an IFTTT.com recipe that adds a new row to a google sheet every time the Wemo switch is turned on and off. The IFTTT.com recipe also sends me a notification on my Android device.

Good work around for now, but it would be better if the Model-T could do it all by itself.

[hebnern]

Nice workaround! This is toward the top of my TODO list, just after fixing the more serious bugs. It should be a fun one to implement. I'm travelling for work right now, but hopefully I can get to it this weekend.

[tracyj]

I like the idea of being able to see the on off cycles logged on top of the graph, but it seems this would be a feature more for debugging, and could be a little distracting in most cases. Could you add the ability to enable or disable the on/off cycles super imposed on top of the graph?

[aborunda]

I am glad I found this thread - I was just thinking that this weekend. I also like the idea of adding some form of "on/off" for the outputs, graphically the colored background works well - from a table set up maybe a true/false (1/0) output would work.