kmbulebu / nicknack Goto Github PK

Allow everything to be configured.

Method, headers, body, etc.

Hostname, port, XBMC name, whatever is available.

A provider should be able to provide a list of values that may be used in an AttributeFilter's operand. The list of values could be static (0,1,2,3,etc), or could be dynamic (e.g. A list of discovered devices).

Attributes currently hold a Map of names and Unit classes, but the Unit class doesn't actually store the value. It only stores metadata for the value. Where do we store the value?

Impacts Event, AttributeFilter, and Operator.

Errors can be handled like any other event. Then an user can decide how they would like an error to be handled, whether via notification (email, etc) or otherwise.

Providers should be able to validate user entered attributes.

Users will want a way to do one-shot runs of Actions. Give them a way to do it.

Create an enabled flag in config that is enforced by the system.

Add UI to save actions outside of a plan. Bookmarked or saved actions. Useful for manual interactions (e.g. turn off all lights)

Consider implementing composite actions as part of this.

Units should be configurable by providers. Create a type of unit per html5 input type. Let provider configure range and step, for example, on a number unit.

Users need to be able to configure providers via the REST api (and in turn the UI). Currently, users have to edit configuration XML files for providers that require it.

Of course, the risk is a never-ending loop could be created by a bad rule.

Should provide a list of installed providers, and give links to their associated event definitions and action definitions.

Many will prefer to view event definitions by provider, so this will support that use case.

As a user I would like to check the status of a state before performing an action.

Example: As a user I would like to close my garage door at 10pm if it is open.

1. Enhance providers to report state only when requested from NickNack. Same as events and actions, state will have no correlation or dependency with events or actions.
2. Enhance Plans to allow the addition of states as criteria.
3. Enhance the Web UI to allow the addition of states as criteria.

Separate calls to manage each attribute filter has no benefit and only complicates the client. Embed them in the event filter to simplify.

Give the user feedback, such as, this event filter matches X events over the last N days.