All communication between devices and modules is done with security in mind. Authentication and encryption are at the heart of StreamBlocks. Most importantly, the “split” architecture of StreamBlocks, whereby a server can be installed locally, can ensure isolation of the control environment from the internet, while providing an application interface to the status data. In order to avoid the dangers of “standard” and therefore backdoor access, no devices have default ids, authentication states, tokens and when generated are done with a cryptographic hash function. System passwords are enforced with 2 step identification and QR codes.
In addition to websockets, the system includes an MQTT server, local Tuya capability, Bluetooth device connectivity, Modbus device connectivity, and numerous others. StreamBlocks can also connect to third party communication devices.
Standard tools such as MQTT explorer can be used to debug communications to devices as shown in the display to the right, which in this case is looking at temperature and humidity data collected from a bluetooth device.
Other tools such as NodeRed can be used to test visually REST communications as shown below.
