Using local node red to get TTN lorawan data through ubidots

 This is kind of cloud data to local data storage.

I have a Lorawan node sending data to TTN. I have it presented on Ubidots . which provide a very good presentation of data and management of device and data.

Ubidots also provide 2 nodes in node red, one to put data to Ubidots, one to receive data from ubidots.

ubidots_out is to send data to ubidots using MQTT

ubidots_in is to receive data from ubidots using MQTT

Getting data to/from Ubidots has a great example:
I have 2 shorts of data on Ubidots, one is direct data integration from TTN, one my local zigbee sensor data uploaded to ubidots using node:ubidots_out.
To receive the 2nd type of data correctly with ubidots in, you will need to add device label in your message payload when using ubitdots out to up load your data.
Othe wise, you can still view the data on the dashboard, but won't be able to down load it.

The 2nd tricky thing is the format returned from unbidots in node, it's not like the my zigbee2mqtt format.There are layers, and each value has it's own sentence.
So need some work to be able to put these data into influxDB.
(the device is the API label of your device on ubidots)




I'm not so familiar with Json manipulation, I tried several errors to redo the message out form ubidots node with a function block:
data and label get correct info from payload, but....

getting close, but still not right, this one will only register humility in influxDB

Finally this one is right..


so with the cofiguration of ubidots node and function, I can get data in my influxDB. But since each value has one msg, so it took a line in database. I think we can do some thing with it in function.

below is the nodes and import code.




[{"id":"948b347c.c35558","type":"ubidots_in","z":"82b75844.2fd748","tier":"business","name":"TTN sensor01 Ubidots in","token":"BBFF-dwBg3A5w4Xi7cHH4Bz27BZ45iB39rM","device_label":"002a9876b6e00ebf","tls_checkbox_in":true,"custom_topic_checkbox":false,"label_variable_1":"temperature","label_variable_2":"humidity","label_variable_3":"lux","label_variable_4":"voltage","label_variable_5":"pressure","label_variable_6":"","label_variable_7":"","label_variable_8":"","label_variable_9":"","label_variable_10":"","checkbox_variable_1_last_value":true,"checkbox_variable_2_last_value":true,"checkbox_variable_3_last_value":true,"checkbox_variable_4_last_value":true,"checkbox_variable_5_last_value":true,"checkbox_variable_6_last_value":true,"checkbox_variable_7_last_value":true,"checkbox_variable_8_last_value":true,"checkbox_variable_9_last_value":true,"checkbox_variable_10_last_value":true,"x":430,"y":140,"wires":[["9fdf9557.29a3a8","7afa6f60.a2847","3e6900c2.d2fb4"]]},{"id":"3e6900c2.d2fb4","type":"function","z":"82b75844.2fd748","name":"function","func":"\nvar payload = msg.payload;\nvar label = Object.keys(payload)[0];\nvar data = payload[label].value;\nvar o={};\no[label]=data;\nmsg.payload=o;\n\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","x":440,"y":260,"wires":[["1d978560.83e4bb","8c2e62bc.0b8dc"]]},{"id":"8c2e62bc.0b8dc","type":"influxdb out","z":"82b75844.2fd748","influxdb":"3118462c.ca816a","name":"testinfluxDB","measurement":"testing","precision":"","retentionPolicy":"","x":670,"y":280,"wires":[]},{"id":"1d978560.83e4bb","type":"debug","z":"82b75844.2fd748","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":670,"y":220,"wires":[]},{"id":"3118462c.ca816a","type":"influxdb","hostname":"192.168.0.35","port":"8086","protocol":"http","database":"lorawansensor01","name":"TTN sensor01 to influx","usetls":false,"tls":""}]



留言

張貼留言

這個網誌中的熱門文章

Heltec ESP32+OLED+Lora, hardware testing

圖片
you can easily find some good boards from china, but most of them lack of accurate document... Hrere is an example; https://hackaday.io/project/26991-esp32-board-wifi-lora-32 the board looks good with lora and a 128x64 OLED, but the IIC and reset connection is important, since pin can be muxing easily, so every board could be different. pinMode(16,OUTPUT);  digitalWrite(16, LOW); // set GPIO16 low to reset OLED  delay(50);  digitalWrite(16, HIGH); // while OLED is running, must set GPIO16 to high  and, if needed, edit your Wire.begin() to Wire.begin(4,15); (4 = SDA 15 SCL)  i tested it with the Adafruit SSD1306 and the Acrobotics SSD1306 Librarys  both work.  Display size is 128x64 There are discussions on these boards on TＴＮ as a LORA node..or maybee single ch gateway? Heltec has a git :  https://github.com/Heltec-Aaron-Lee And there is another copy call TTGO https://de.aliexpress.com/item/TTGO-LORA32-868-915-Mhz-SX1276-ESP32-Oled-display-Bluetooth-WIFI
閱讀完整內容

micro SD card for ESP32, on lolin32 with OLED and heltec 32 lora oled

圖片
I have purchased 2 micro SD card holder for my esp project. First I would like to test with heltec esp32 lora oled module. this module uses: sck=05 MISO=19 MOSI=27 SS(lora)=18, then I assigned 21 for sd SS and there is a lib in esp32-arduino, which use SS default at 5 I took the example and use SD.begin(21), but I alway get the error: entry 0x40078a9c Card Mount Failed But I do saw once that it read out the sd card type and volume. Not sure it's the issue of lora sd card swithing, or it just can't work. The other esp32 card I have is an wemos esp32 oled, it did not leave me too much pins, I need to find out how to connect sd to it. But I have wemos D1 mini esp8266 on hand, and connect it as:  * The WeMos Micro SD Shield uses:  * D5, D6, D7, D8, 3V3 and G  *  * The shield uses SPI bus pins:  * D5 = CLK  * D6 = MISO  * D7 = MOSI  * D8 = CS It's not working with the example in the arduino IDE 1.8.5, which marked SD(esp8266), but it w
閱讀完整內容

AIS0. understanding AIS NMEA 0183: How it's coded

For my boat tracking system, I found out that using AIS format seems to be a good idea, at least I don't have to worry about how to present boat data, since there are already plenty things for do this on mobile phone or PC. Here is what I read: http://catb.org/gpsd/AIVDM.html Looking into AIS NMEA0183, it has much more application then I think. Such as MOB device, epir, aid to navigation device...etc, all are included. it use the first few char to indicate the function: Table 1. AIS talker IDs !AB NMEA 4.0 Base AIS station !AD MMEA 4.0 Dependent AIS Base Station !AI Mobile AIS station !AN NMEA 4.0 Aid to Navigation AIS station !AR NMEA 4.0 AIS Receiving Station !AS NMEA 4.0 Limited Base Station !AT NMEA 4.0 AIS Transmitting Station !AX NMEA 4.0 Repeater AIS station !BS Base AIS station (deprecated in NMEA 4.0) !SA NMEA 4.0 Physical Shore AIS Station It can also be used between device on boat for message communication, AIVDO The
閱讀完整內容