photonMasterRemote | photon Master Alarm with multiple photon Remote

photonMasterRemote is a C++ library typically used in Internet of Things (IoT), Nodejs, Arduino applications. photonMasterRemote has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

A photon Master Alarm system with any number of optional photon Remote nodes. See Wiki for lots more detail. Common source generates a master alarm node or a remote node. The master node is created by the #define PHOTON_MASTER line in parms.h. A remote node is created by commenting out the master node #define , i.e. //#define PHOTON_MASTER which will result in a #define PHOTON_REMOTE In addition, you must inclue the line #define REMOTE_SYSTEM_ID 1 The id number must be 1 or greater. The id of the master node must be 0. The master my have any number of it's own sensors defined in writeTestConfiguration. The master's representation of a remote sensor is defined with device.use set to SUB_REMOTE_THERMOMETER or SUB_REMOTE_SENSOR. The actual sensor is defined in the remote with master_idx set to the index number in the master which represents the remote sensor. Communication of the remote sensor status is done via a particle.publish string which represents the state of all of the remote sensors, such as: 3@1@T@13:12:16@TEST DOOR:2:0.000000:3@OUTSIDE TEMP:3:89.937500:0$ The @ character separates the first four data fields (sequence,remote id, alert type, and time). Data for each sensor follows, also separated by an @ character. These fields are parsed by the class Parse. Each sensor's data fields are separated by a : character. They are Name,device index in master, and sensor reading. These data fields are also parsed by class Parse. The remote node publishes 'remoteData' to the particle cloud, and the master node is subscribed to this cloud data field. The remote node performs a publish immediately upon any sensor being tripped, and also periodically as an Information update on a specified schedule, set in parms.h. This allows for immediate response to an alarm condition and periodic read on the master node of other less time-sensitive data such as a temperature probe. Upon receipt of the subscribed remoteData, the master device is update with the new sensor data, stored into the device record as dev_reading, and the current time is stored into dev_last_read. In my operational test system, the hardware for both master and remote can be identical, except for the attached sensors. The remote node may also be of any custom design, as required. It only needs to publish a properly formatted data string as 'remoteData'.