lyuzashi / mqtt-smarthome-system Goto Github PK

Wrap MIDI interface into a module which will occasionally/on trigger search for new matching devices and gracefully handle disconnects.

It should be able to detach and reconnect to devices when unplugged or plugged in and when config changes to specify new devices/config.

MQTT messages are all sent as strings.

Sensible assumptions could be made in this order

1. "true" or "false" – boolean
2. "0" or "1" for */on topic – boolean
3. anything for */text topic – string
4. numerical – integer
5. anything else – string

Particular topics could have overriding rules for special cases.

Write a function to handle all these for unmarshalling a message.

Compose configuration into MQTT topics.

Requires handling of arrays and tool to rebuild config object in memory.

Discover tree structure by subscribing to a * topic and getting all messages under it?

e.g.

interfaces:
  lattice:
    modes:
      lighting:
        zones:
         - name: lounge

interfaces/lattice/modes/lighting/zones/0/name : lounge

Interfaces should only be concerned with moving data in and out of MQTT messages.

Any translation can be handled by logic.

HAP would be a system-based protocol

If a device is offline and it's status is requested, the callback awaiting a response appears to prevent any other communication with other devices

Provide interface for devices via PiGPIO.

• Discover nodes via mDNS
• Handle like pins in current GPIO module
• Expand support for
  • bit bang serial devices
  • 1-wire LEDs
  • SPI (stretch)

Rebuild local GPIO to connect via PiGPIO too.

Rather than the current setup which limits hue API calls to one in-flight at a time, use throttling to allow many requests up to a certain rate to be sent.

https://developers.meethue.com/develop/application-design-guidance/hue-system-performance/

The available system throughput (from the hue API) is thus restricted by the number of ZigBee messages per second that can be handled by the system, which is approximately 25 ZigBee messages/s

Configuration for scenes which may have names or be part of a sequence.

Sequencing provides time stamp sets of scenes and start from 0 when triggered

Simple web-based displays can stream in data

Provide authentication scheme for accessing MQTT topics

Simple IoT devices can provide a username:password and will have limited access to particular topics.

Access control can be described in #17

Every device should belong to an universal graph including protocol specific interfaces and generic attribute language.

This could be the presence of a device by MAC address on the IP network, a ZigBee lightbulb with all attributes and multiple protocol support or a local input device.

Provide some way to generate or template these so new devices can be added easily. A config screen?

As each message arrives, store it as "last state" which will enable handling controls such as rotary knobs and determining velocity

Simple discover/attach loop to find network devices and attach them via USB/IP when a remote computer is publishing an advertisement.

Provide status of banks and key presses over MQTT.
This can be used to display an interface for controlling in different modes, e.g. Lighting bank selected, show master brightness, channel names and modifier hints

While running long transitions, it should be possible to calculate the current state by extrapolating the less granular changes observed.

These should then have the capability to be overrode, such as turning off lights when leaving during a sunset event