Teltonika FMM920 sensor to Thingsboard - thingsboard

Have someone manage to connect a sensor from Teltonika to Thingsboard?
I'm trying to configure a Teltonika FMM920. Got it to send data to https://gps-trace.com/en/ruhavik but i've not yet found a guide for sending data directly to Thingsboard.
What i want to do is to send Latitude and Longitude data to Thingsboard. either via TCP or MQTT.

Related

MQTT subscriber receiving data after disconnection

Good afternoon, so I have currently an MQTT session active. I am using Eclipse Mosquitto as a broker.
The publisher is a Core2 from M5Stack that has a connected sensor and this device sends the read temperature to Mosquitto which through Prometheus plots the information in software grafana.
So the problem here is that the Core2 sometimes runs out of battery, but grafana keeps plotting data on a loop of the last read value, which is the last value the Core2 sent before disconnecting. We have connected the core2 to the wall but we want to make sure in case it disconnects it will stop plotting data in Grafana.
Any idea on what could I do?

NodeRed to Thingsboard data is inconsistent

We are facing an issue in the customer premises where the gateway which is connected to the meters send data to ThingsBoard using the Node-Red.
To simulate the functionality at the actual client premises created Node-Red nodes which sends data to ThingsBoard. But the data which is received at the ThingsBoard is inconsistent and not at the regular interval which is been set as 30 secs in the Node-Red.
What could be the issue?

Gateway: receiving data with LoRa and sending with GPRS to a server

I'm building a gateway for an IoT project. I need to receive sensor data (from an end device) with LoRa (RFM95) and send it to a Cayenne server with GPRS (SIM800C).
The PCB is almost ready but I'm stuck at the coding part. How to configure it to work with two different protocols?

How to fetch Geo location of MQTT client devices when subscribing to a topic?

I am using MQTT protocol in real time data communication application,therefore I need to retrieve the client device location data and pass it to MQTT broker. Is there any available API to track client device Geo location in MQTT environment
It really isnt' clear what you are asking in the question but I'll try to cover all the options.
The device knows it's own location and you want to publish this information on a topic. Assuming the device has a GPS receiver (or some other way to determine it's own location e.g. data from a cellular network) then it's simply a case of building a message with a payload including the location data in what ever format you want
You are trying to determine the location of the client purely from it's connection to the broker. The broker will know the client's IP address so in theory it could use a IP Geolocation API to give an estimate of the devices location. There are no standard brokers with this capability so you would have to build your own. Also in most cellular environments the devices sit behind NAT gateways so you would only be able to locate the gateway not the end device.

How do I send and receive network MIDI data in iOS?

How do I send and receive network MIDI data in iOS? I am able to resolve the server using bonjour and apply the service to a MIDI connection, but I don't know where to go from there. The documentation seems to be lacking, and there's not much information online.
Essentially, you need to connect to the session via Bonjour as you have done, and within your iOS app:
Create a client using MIDIClientCreate
Create an input port using MIDIInputPortCreate
This takes a pointer to a C function that will be called when MIDI data is received
You need to connect it to the MIDINetworkSession's defaultSession using MIDIPortConnectSource - connect it to the sourceEndpoint
Create an output port using MIDIOutputPortCreate
You can send data to the network session using MIDISend - send the packets to to the MIDINetworkSession defaultSession's destinationEndpoint
I wrote a few blog posts about this a while back, see here for source code etc.
Part 1
Part 2
Part 3

Resources