search

bwssytems / domuslink

web-based frontend for Heyu
http://domus.link.co.pt/
1 stars 1 forks source link

monitoring status #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
With some devices I do not wish to have an on/off toggle provided. Such
devices that I would like to monitor without being able to turn on/off
would be a garage door n/o contact wired to a powerflash, dusk sensors on
ms14a's, ds10a door/window sensors.

Original issue reported on code.google.com by brandtda...@gmail.com on 6 Mar 2010 at 6:04

GoogleCodeExporter commented 9 years ago 
Just like with robotics, you have your sensors, actuators, and processor unit. 
One
should not want to toggle the sensors, only the actuators.

Original comment by brandtda...@gmail.com on 8 Mar 2010 at 7:50

GoogleCodeExporter commented 9 years ago 
As we add different types of modules through development this would be an item 
that
would be covered. As I would like to have a remote definition that fits your 
idea of
an actuator. It has on/off as separate buttons, but no state.
So, this feature would be a request for a monitor icon with no actionable items.

Original comment by bwsamuels@gmail.com on 8 Mar 2010 at 9:21

GoogleCodeExporter commented 9 years ago 
That is correct a sensor could be monitored but not toggled. An actuator could 
be
monitored and toggled.

Original comment by brandtda...@gmail.com on 8 Mar 2010 at 9:41

GoogleCodeExporter commented 9 years ago 
A motion sensor would not necessarily have to be monitored because they are 
triggered
very quickly, however the dusk sensors would be nice to monitor as well as any
contact closures, or flood sensors, etc...

Original comment by brandtda...@gmail.com on 11 Mar 2010 at 8:02

GoogleCodeExporter commented 9 years ago 
The sensor that is async could display the last time it was triggered. I think 
that
may be available through heyu.

Original comment by bwsamuels@gmail.com on 12 Mar 2010 at 3:28

GoogleCodeExporter commented 9 years ago 
After creating the "other" type for V1.1 I have a better idea on how this can be
handled. I thing we need to add an addition to the alias of the type of module
independent of the subtype (lights, appliances, irrigation, shutter or other).

Original comment by bwsamuels@gmail.com on 30 Mar 2010 at 1:31

GoogleCodeExporter commented 9 years ago 
I have seen a few discussions on the users group looking for separating the 
type and the module actions. i.e.: have a "Light" but only has on/off, no 
dimming.

Original comment by bwsamuels@gmail.com on 19 Jan 2011 at 1:37

GoogleCodeExporter commented 9 years ago 
I have implemented a status type module that does not have any controls, but 
shows state of on/off

Original comment by bwsamuels@gmail.com on 21 Feb 2011 at 1:53

GoogleCodeExporter commented 9 years ago 
I have implemented a status type module that does not have any controls, but 
shows state of on/off

Original comment by bwsamuels@gmail.com on 21 Feb 2011 at 1:53

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r834.

Original comment by bwsamuels@gmail.com on 23 Feb 2011 at 3:58