Lighting Automation/Control Software: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
Master all off from the last man switch should be all but the hall<br /> | Master all off from the last man switch should be all but the hall<br /> | ||
Switch panels should not care about current state and should just send 'toggle' state commands per zone, except for posible all off buttons<br /> | Switch panels <s>should not care about current state and should</s> just send 'toggle' state commands per zone, except for posible all off/on buttons<br /> | ||
Special function scripts form holly may want to set certain states, these will not matter about current state but would be setiing a defined on/off.<br /> | Special function scripts form holly may want to set certain states, these will not matter about current state but would be setiing a defined on/off.<br /> | ||
Control box firmware will be responsible for sending out retained STATE messages after it has switched any zone, 0 (all) zones may/may-not have state,<br /> | |||
The two big switch panels are using state to change LED's and any script on Holly can you state's as needed<br /> | |||
By using retained state MQTT messages any new client or reconnecting client subscribing to nh/li/sate/# will be feed the state of all current zone's | |||
Internally the control box firmware will have to track state of each zone it's in charge of.<br /> | Internally the control box firmware will have to track state of each zone it's in charge of.<br /> | ||
| Line 25: | Line 26: | ||
Rooms And zones<br/> | Rooms And zones<br/> | ||
if no zone listed | if no zone listed use 1<br/> | ||
Controller 1<br/> | Controller 1<br/> | ||
* Workshop | * Workshop | ||
| Line 52: | Line 53: | ||
** 1 (walk way) | ** 1 (walk way) | ||
** 2 (seating) | ** 2 (seating) | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 13:40, 17 May 2012
First thing is to establish the command protocol to use with mqtt topics and payloads.
This is based around posible commands we want to issue.
There is a total of 11 rooms and 17 zones.
The Workshop, Stuido, and Comfy Area have multiple zones.
There will be times when we want to change all zones in these rooms, also time when we might want to act on multiple rooms.
An 'All Off' button for the workshop should include the electronics bench, an 'All off' for the Stuido should include the Comfy Area?
Master all off from the last man switch should be all but the hall
Switch panels should not care about current state and should just send 'toggle' state commands per zone, except for posible all off/on buttons
Special function scripts form holly may want to set certain states, these will not matter about current state but would be setiing a defined on/off.
Control box firmware will be responsible for sending out retained STATE messages after it has switched any zone, 0 (all) zones may/may-not have state,
The two big switch panels are using state to change LED's and any script on Holly can you state's as needed
By using retained state MQTT messages any new client or reconnecting client subscribing to nh/li/sate/# will be feed the state of all current zone's
Internally the control box firmware will have to track state of each zone it's in charge of.
Posible commands
- ON
- OFF
- TOGGLE
Posible State
- ON
- OFF
Rooms And zones
if no zone listed use 1
Controller 1
- Workshop
- 0 (all)
- 1 (wood working)
- 2 (Cnc's)
- 3 (metal working
- 4 (bike)
- Electronics
- Textiles
- Toilets
Controller 2
- Kitchen
- Blue
- Storage
- Box
- Hall
- Studio
- 0 (all)
- 1 (walk way)
- 2 (middle)
- 3 (far side)
- Comfy
- 0 (all)
- 1 (walk way)
- 2 (seating)
| Topic | Description | Notes |
|---|---|---|
| nh/li/set/ROOM/ZONE | Lighting Command | ROOM is one of the pre defined rooms ZONE within a ROOM and payload is COMMAND |
| nh/li/state/ROOM/ZONE | Lighting State | Retained Topic! ROOM is one of the pre defined rooms ZONE within a ROOM and payload is Curent STATE |