MQTT sensor data

[happytm]

I would like to use sensor data via MQTT instead of serial. Is it possible? I am working on low power IOT home automation network. The code I wrote send 5 sensor values and their respective sensor types from multiple devices on network via MQTT messages. These devices can also receive MQTT commands by publishing with topic command///. My repo is linked below:

https://github.com/happytm/BatteryNode

Right now I am using ESP Dash android app to monitor and control my network but your software could be better because it can make automation logic possible with rules.

Thank you.

[danionescu0]

Hi there From the quest i don't understand if you're asking about implementing MQTT in my home automation repository or in your BatteryNode one? Which one are you asking ? :)

…

On Sat, Dec 21, 2019 at 3:09 AM happytm ***@***.***> wrote: I would like to use sensor data via MQTT instead of serial. Is it possible? I am working on low power IOT home automation network. The code I wrote send 5 sensor values and their respective sensor types from multiple devices on network via MQTT messages. These devices can also receive MQTT commands by publishing with topic command///. My repo is linked below: https://github.com/happytm/BatteryNode Thank you. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#23?email_source=notifications&email_token=ABDFS3V7HCT44SVNXPKHMSDQZVUGNA5CNFSM4J6EWIK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICDAGPQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDFS3VGZPPMAUG5PEKPH6LQZVUGNANCNFSM4J6EWIKQ> .

[happytm]

Sorry I was not clear enough. I wanted to use your front end to display data on web.Data will be collected by my battery nodes and published as MQTT messages. I wanted to see if you can implement my ProbeReceiver.ino sketch in your code and display all sensor data it collects from all battery node devices on network . Each BatteryNode devices send data to one gateway and gateway has MQTT broker built in which publishes data in following format for example data received from a BatteryNode with Device ID = 36:

Serial debug messages on Gateway device where it receive data from all Battery node devices:
Command sent to device no. 36 = 'command/36/06/16/26/36/46/

################ Person 1 arrived ######################
Received Topic 'Sensordata/Person1/Home
Received Topic 'Sensordata/Signal/-48
Received Topic 'Sensordata/Person1/in/Livingroom
Received Topic 'SensorData/36/6/2.90
Received Topic 'SensorData/36/16/20
Received Topic 'SensorData/36/26/50
Received Topic 'SensorData/36/36/596
Received Topic 'SensorData/36/46/37
Received Topic 'DeviceStatus/36/DeviceMode/0
Received Topic 'DeviceStatus/36/DeviceIP/36
Received Topic 'DeviceStatus/36/WiFiChannel/7
Received Topic 'DeviceStatus/36/SleepTime/1
Received Topic 'DeviceStatus/36/UpTime/127

6,16,26,36,46 in above messages are predefined sensor types to identify what kind of sensors they are for example 6 = voltage, 16 = temperature , 26 = humidity, 36 = pressure, 46 = light intensity etc.

Signal Strength of remote sensor: -23
Received Topic 'Sensordata/Signal/-23

Serial debug messages from BatteryNode device no. 36:

Sensor Type values sent to controller: 24:06:10:1A:24:2E
Device status values sent to controller: 24:00:24:07:01:8B
Sensors values sent to controller: 24:93:38:25:19:59
Message received from Controller: 24:06:10:1A:24:2E (This message is received from gateway).

I hope this clears the confusion.

Thanks.

[danionescu0]

I think i get it: your devices would emit to some MQTT topics, my project would listen to that topic and record the metrics then display it. In order to achieve this, the messages would need to be in some format like you said: Topic: 'SensorData/sensor_id/sensor_type/value' a concrete example: 'SensorData/36/46/1000'. Then i would record in my backend that sensor_id 36 that is of type "pressure" has recorded a value of 1000 at the present time In this way you would be using my project as a "data store" and visualisation tool. Am i getting it right? An alternative to this is checking out MQTT cloud platforms like: http://www.cloudino.io/ Please tell me your thoughts on this:)

…

On Mon, Dec 23, 2019 at 10:40 PM happytm ***@***.***> wrote: Sorry I was not clear enough. I wanted to use your front end to display data on web.Data will be collected by my battery nodes and published as MQTT messages. I wanted to see if you can implement my ProbeReceiver.ino sketch in your code and display all sensor data it collects from all battery node devices on network . Each BatteryNode devices send data to one gateway and gateway has MQTT broker built in which publishes data in following format of data received from a BatteryNode with Device ID = 36: Serial debug messages on Gateway device where it receive data from all Battery node devices: Command sent to device no. 36 = 'command/36/06/16/26/36/46/ ################ Person 1 arrived ###################### Received Topic 'Sensordata/Person1/Home Received Topic 'Sensordata/Signal/-48 Received Topic 'Sensordata/Person1/in/Livingroom Received Topic 'SensorData/36/6/2.90 Received Topic 'SensorData/36/16/20 Received Topic 'SensorData/36/26/50 Received Topic 'SensorData/36/36/596 Received Topic 'SensorData/36/46/37 Received Topic 'DeviceStatus/36/DeviceMode/0 Received Topic 'DeviceStatus/36/DeviceIP/36 Received Topic 'DeviceStatus/36/WiFiChannel/7 Received Topic 'DeviceStatus/36/SleepTime/1 Received Topic 'DeviceStatus/36/UpTime/127 6,16,26,36,46 in above messages are predefined sensor types to identify what kind of sensors they are for example 6 = voltage, 16 = temperature , 26 = humidity, 36 = pressure, 46 = light intensity etc. Signal Strength of remote sensor: -23 Received Topic 'Sensordata/Signal/-23 Serial debug messages from BatteryNode device no. 36: Sensor Type values sent to controller: 24:06:10:1A:24:2E Device status values sent to controller: 24:00:24:07:01:8B Sensors values sent to controller: 24:93:38:25:19:59 Message received from Controller: 24:00:00:00:00:00 (This message is received from gateway). I hope this clears the confusion. Thanks. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#23?email_source=notifications&email_token=ABDFS3WPXIBS2IYGVCTYSLTQ2EO4RA5CNFSM4J6EWIK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHR4VEQ#issuecomment-568576658>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDFS3UTPLK26TIXQNEBJ3LQ2EO4RANCNFSM4J6EWIKQ> .

[happytm]

In this way you would be using my project as a "data store" and
visualisation tool. Am i getting it right?

Yes that's how I wanted to use it.

An alternative to this is checking out MQTT cloud platforms like:
http://www.cloudino.io/

The reason I chose to implement MQTT broker on gateway device itself was to have truly local standalone sensor network without using third party cloud. I can still connect, display data and control all devices on my network by using android app like MQTT dash without using cloud MQTT broker.

I need your help to implement your web front end.

Thank you.

[danionescu0]

Hey, i've just implemented something that could be useful for you in my other repo: https://github.com/danionescu0/docker-flask-mongodb-example Please check it out and give me your feedback. Look at MQTT + Grafana integration

…

On Tue, Dec 24, 2019 at 9:48 PM happytm ***@***.***> wrote: In this way you would be using my project as a "data store" and visualisation tool. Am i getting it right? Yes that's how I wanted to use it. An alternative to this is checking out MQTT cloud platforms like: http://www.cloudino.io/ The reason I chose to implement MQTT broker on gateway device itself was to have truly local standalone sensor network without using third party cloud. I can still connect, display data and control all devices on my network by using android app like MQTT dash without using cloud MQTT broker. I need your help to implement your web front end. Thank you. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#23?email_source=notifications&email_token=ABDFS3QG2XVQTJOIIE32JX3Q2JRRPA5CNFSM4J6EWIK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTSHHI#issuecomment-568796061>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDFS3UJW6DISXBJSJ5MELTQ2JRRPANCNFSM4J6EWIKQ> .