Thank you - I have been using NR and grafana for years then along came docker and influx 2 - got my NR stuff generally going - but influx2 no clue - buckets etc. So now I'll use you example - already put the test data in influx - and it's there I can see it but no idea how to move onto grafana (all installed of course - in docker)..
This is helpful...but if I have real data coming in via mqtt (Tasmota providing nested objects of timestamp, sensor, sensor), how do I format that data so that influx will take it? It comes in parsed as a json object, but apparently not how influx likes it. Do I need to strip the data out to a global on every message for the javascript payload to work?
Unfortunately InfluxDB works with real time data as default and assigns it's own time stamp for each message. Unfortunately you will have to split the incoming message into separate process values pushed into global or flow memory then create a new JSON message for InfluxDB. Quick question, is your remote connection from an Ardudio?
@@IOTConnectivity Remote is tasmota running on an esp32. Finally got it figured out, and you're right. I had to rebuild the message. Used a change node to delete an extra sensor (laser distance for prox detection, don't need to log that) "{ "pm2.5": msg.payload.VINDRIKTNING.'PM2.5' }"
I try not to pay for any open source software. InfluxDB have released a new version since I recorded this video. I will take a look. Thanks for the feedback, glad you enjoy the content.
Do you know a way to write values to a specific key? For example, I want to have a topic key in addition to the measurement key, and I want the topic to have a value.
very well explained. thanks you
Thank you - I have been using NR and grafana for years then along came docker and influx 2 - got my NR stuff generally going - but influx2 no clue - buckets etc. So now I'll use you example - already put the test data in influx - and it's there I can see it but no idea how to move onto grafana (all installed of course - in docker)..
How do you put a "_tag" to the data?
This is helpful...but if I have real data coming in via mqtt (Tasmota providing nested objects of timestamp, sensor, sensor), how do I format that data so that influx will take it? It comes in parsed as a json object, but apparently not how influx likes it. Do I need to strip the data out to a global on every message for the javascript payload to work?
Unfortunately InfluxDB works with real time data as default and assigns it's own time stamp for each message. Unfortunately you will have to split the incoming message into separate process values pushed into global or flow memory then create a new JSON message for InfluxDB. Quick question, is your remote connection from an Ardudio?
@@IOTConnectivity Remote is tasmota running on an esp32. Finally got it figured out, and you're right. I had to rebuild the message. Used a change node to delete an extra sensor (laser distance for prox detection, don't need to log that)
"{
"pm2.5": msg.payload.VINDRIKTNING.'PM2.5'
}"
Are you using the free version or the paid one? for me the dashboard is different. Btw its a great content
I try not to pay for any open source software. InfluxDB have released a new version since I recorded this video. I will take a look. Thanks for the feedback, glad you enjoy the content.
@@IOTConnectivity could you guide me to download the new version.
Do you know a way to write values to a specific key? For example, I want to have a topic key in addition to the measurement key, and I want the topic to have a value.
Hola, muy muy muy buen video, aprendí mucho, muchas gracias. very very very good video, thank you very much
This is great video!
Glad you think so!
Muito bom, Obrigado
that was useful thank you
Glad it was helpful!
I had this error. Someone help me please
HttpError: 405 Method Not Allowed :
405 Not Allowed
405 Not Allowed
nginx/1.24.0