nello_one_without_cloud | nello.io / sclak.com - Remove cloud constraint

Nello will automatically subscribe to the following topics:. The nello backend uses two different nello device identifiers. The first one is being used to connect to the MQTT broker (as a client id): First id: format Pt######## (10 digits). The second one is being used as a MQTT topic identifier for a specific device: Second id: format X##### (6 digits). After the subscription process is done, nello and the cloud system exchange different kind of base64 encoded messages with QoS 1. Assumption: nello was already connected to the backend. (see 3.3. Uncertainties: wifi ssid transmission). 1. Topic: map Nello device -> Nello Backend (MQTT Broker) /nello_one/{second deviceid}/map/JA...oMf0=\n This message (length: 32 byte - exluding ''\n') is always the same for a single device. 2. Topic: test Nello Backend (MQTT Broker) -> Nello device /nello_one/{second deviceid}/test/Iu....O...\n This message varies in its content. Only the length (48 byte, exluding ''\n') seems to be always the same. 3. Topic: n_online Nello device -> Nello Backend (MQTT Broker) /nello_one/{second deviceid}/n_online/81...=\n This message varies in its content. Only the length (32 byte, exluding ''\n') seems to be always the same. 4. Topic: BE_ACK Nello Backend (MQTT Broker) -> Nello device /nello_one/{second deviceid}/BE_ACK/Qg...=\n This message varies in its content. Only the length (32 byte, exluding ''\n') seems to be always the same. Afterwards the connection is fully established, nello blinks like it is used to be, etc etc etc.. Door unlock command sequence Nello Backend (MQTT Broker) -> Nello device /nello_one/{second deviceid}/door/ZJ...=\n This message varies in its content. Only the length (32 byte, exluding ''\n') seems to be always the same. Nello device -> Nello Backend (MQTT Broker) /nello_one/{second deviceid}/n_ACK/ZE...=\n This message varies in its content. Only the length (32 byte, exluding ''\n') seems to be always the same.