Vancouver Hack Space

User Tools

Site Tools

You are here: start » infrastructure » smartspace
infrastructure:smartspace

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
infrastructure:smartspace [2019/04/07 02:14] – Added config and devices and removed services tyisiinfrastructure:smartspace [2024/05/19 23:34] (current) – Added test topic tyisi
Line 5: Line 5:
 SmartSpace consists of three components: SmartSpace consists of three components:
   * SpaceBus, a Mosquitto-based MQTT broker service that will allow users/devices/services to pass messages. SpaceBus features a controlled part for protected use (such as phone notifications) and an open part for general use   * SpaceBus, a Mosquitto-based MQTT broker service that will allow users/devices/services to pass messages. SpaceBus features a controlled part for protected use (such as phone notifications) and an open part for general use
-  * SmartSpace services, a variety of services that can connect to the SpaceBus, including Node-Red, Grafana, Influxdb, SIP monitoring and URL monitoring+  * SmartSpace services, a variety of services that can connect to the SpaceBus, including Sergeant, Node-Red, Grafana, Influxdb, SIP monitoring and URL monitoring
   * SmartSpace devices, devices around the space that either act as consumers or publishers on the SpaceBus. Example: visual phone notification aids or automatic sign control based on [[hacks:isvhsopen]]   * SmartSpace devices, devices around the space that either act as consumers or publishers on the SpaceBus. Example: visual phone notification aids or automatic sign control based on [[hacks:isvhsopen]]
  
Line 23: Line 23:
  
 ==== SpaceBus ==== ==== SpaceBus ====
 +
 +=== Use ===
 +
 +For now, read only access is available on spacebus.vanhack.ca on port 1883
 +
 +=== Topics ===
  
 SpaceBus uses the following patterns/naming conventions: SpaceBus uses the following patterns/naming conventions:
  
-^ Type ^ Topic Naming ^ Purpose ^ +Controlled: 
-| Config | /config/ //device// | Push configurations to devices | +^ Type ^ Topic Naming ^ Purpose ^ Read Access ^ Write Access ^ 
-| Devices | /devices/ //device// / //key// | Push/update specific device settings or values | +| Config | / config / //device// | Push configurations to devices | VHS Restricted | VHS Restricted | 
-| Events | /events/ //category// / //name// | Topic for single event reporting | +| Devices | / devices / //device// / //key// | Push/update specific device settings or values | VHS Restricted | VHS Restricted | 
-| Status | /status/ //category// / //key// | Topic for general status reporting. |+| Events | / events / //category// / //name// | Topic for single event reporting | Public | VHS Restricted | 
 +| Status | / status / //category// / //key// | Topic for general status reporting. | Public | VHS Restricted | 
 +| Projects | / projects / //project// / //key// / | Topic for project specific things | Public | Project Restricted | 
 +| Tests | / test / //anything// | Topic for testing | Public | Public |
  
 Special categories: Special categories:
infrastructure/smartspace.1554603290.txt.gz · Last modified: 2019/04/07 02:14 by tyisi
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki