1,555
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − = Ideas = − − == Message broker idea == − − Use a message broker such as [http://activemq.apache.org ActiveMQ] or RabbitMQ as the core of the system. Hef already has RabbitMQ in the space for ps1auth. This can be communicated with an an number of protocols but by far the simplest is STOMP. All messages passing through the broker should be JSON text messages well formed and documented. − − Messages from devices such as arduinos could use MQTT protocol there is even an arduino lib: http://knolleary.net/arduino-client-for-mqtt/ − Interesting article about bridging messages from a ZigBee mesh into MQTT: http://rijware.com/zigbee-and-mqtt/ − − == References == − − The thread that started this off: https://groups.google.com/forum/#!topic/pumping-station-one/ogqSHK08DAI − − === Other Links === − − https://wiki.muc.ccc.de/uberbus:start?redirect=1 − − https://wiki.muc.ccc.de/uberbus:ubd − − https://github.com/muccc/ubd − − https://wiki.muc.ccc.de/uberbus:protocols − − http://stackoverflow.com/questions/1534655/creating-a-program-to-be-broadcasted-by-avahi − − http://www.avahi.org/wiki/Examples/PythonPublishAlias Line 126:
Line 100: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
We want to make a super-easy-to-integrate-with way to handle sensors and actuators around the space.
We want to make a super-easy-to-integrate-with way to handle sensors and actuators around the space.
= Things We Want To Integrate =
= Things We Want To Integrate =
{ "target": "DustCollection", "location": "workshop", "messageType": "command", "command": "off"}
{ "target": "DustCollection", "location": "workshop", "messageType": "command", "command": "off"}
</pre>
</pre>
= Ideas =
== Message broker idea ==
Use a message broker such as [http://activemq.apache.org ActiveMQ] or RabbitMQ as the core of the system. Hef already has RabbitMQ in the space for ps1auth. This can be communicated with an an number of protocols but by far the simplest is STOMP. All messages passing through the broker should be JSON text messages well formed and documented.
Messages from devices such as arduinos could use MQTT protocol there is even an arduino lib: http://knolleary.net/arduino-client-for-mqtt/
Interesting article about bridging messages from a ZigBee mesh into MQTT: http://rijware.com/zigbee-and-mqtt/
== References ==
The thread that started this off: https://groups.google.com/forum/#!topic/pumping-station-one/ogqSHK08DAI
=== Other Links ===
https://wiki.muc.ccc.de/uberbus:start?redirect=1
https://wiki.muc.ccc.de/uberbus:ubd
https://github.com/muccc/ubd
https://wiki.muc.ccc.de/uberbus:protocols
http://stackoverflow.com/questions/1534655/creating-a-program-to-be-broadcasted-by-avahi
http://www.avahi.org/wiki/Examples/PythonPublishAlias