Stuck on installing fleet-managment

Sebastian · July 9, 2025, 1:58pm

Hi,

I’m new to openremote. I have followed the “Create your own Fleet Management System” turtorial.
The teltonika device is a fmc234.
Wireshark shows me, that the device and the broker do a encryption handshake and then application data is sent.
When I set the third part of the topic to anything else that teltonika, there appears a error message in the log. So I am optimistic that the device is sending data properly.
I have added an asset and entered the parameter data from the “Teltonika Data Sending Parameter ID Parser” script.
But still I can`t see anything in openremote and I have ran out of ideas.
Somebody has an idea what else I could do?

cheers
Sebastian

Sebastian · July 10, 2025, 2:27pm

The log from the manager container ist full of these messages:

2025-07-10 16:16:49.635  INFO    [Thread-2 (ActiveMQ-serve..7fd)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-10 16:16:53.887  INFO    [Thread-5 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

2025-07-10 16:17:50.480  INFO    [Thread-2 (ActiveMQ-serve..7fd)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-10 16:17:53.001  INFO    [Thread-0 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

2025-07-10 16:20:01.564  INFO    [Thread-2 (ActiveMQ-serve..7fd)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-10 16:20:04.644  INFO    [Thread-1 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

panos · July 11, 2025, 12:17pm

Hey @Sebastian ,

The logs you have attached show that device 002 is subscribing and unsubscribing from the command topic of OpenRemote. This indicates some sort of misconfiguration there. Are you sure that you have followed the instructions correctly? The fact that there are logs of connection and disconnection to the MQTT broker indicate that the device does connect correctly to the MQTT broker, so it’s not an issue with SSL. Are you sure you have selected the Codec MQTT option in the Teltonika configuration?

It’d be great if you could send all log messages sent from the TeltonikaMQTTHandler, since they may tell us more about what exactly is happening when the device connects to OpenRemote.

Looking forward to your reply!

Sebastian · July 11, 2025, 9:31pm

Hi Panos,
thank you for your answer.

I can’t find an output from TeltonikaMQTTHandler.
The Log from the web ui only shows:

11.07.2025 22:18:35	INFO	API	UserAssetProvisioningMQTTHandler	Adding publish consumer for topic 'provisioning/+/request': handler=UserAssetProvisioningMQTTHandler
11.07.2025 22:18:35	INFO	API	DefaultMQTTHandler	Adding publish consumer for topic '+/+/writeattributevalue/#': handler=DefaultMQTTHandler

The log from docker only shows the connect/disconnect messages.
Are there more places to look at?

The device settings are like this:
System->Data Protcol->Codec Jason
GPRS->Server Settings->Protocol->MQTT
GPRS->Server Settings->TLS Encryption->TLS/DTLS
GPRS->MQTT Settings->AWS IoT Custom
GPRS->MQTT Settings->Data Topic-> master/002/teltonika/%imei%/data/
GPRS->MQTT Settings->Commands Topic-> master/002/teltonika/%imei%/commands

panos · July 11, 2025, 10:18pm

Hey @Sebastian ,

I can see that the data MQTT topic on the configuration ends with “data/”. You should remove that backslash. Hopefully that will start the data coming in and you’ll see the tracker on the asset tree.

Let me know if that helps!

Sebastian · July 11, 2025, 10:41pm

That was mistake number one

Now the docker log says:

2025-07-12 00:38:46.570  INFO    [Thread-0 (ActiveMQ-serve..7fd)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-12 00:38:47.115  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 00:38:47.115  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:47.115  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 00:38:47.115  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:49.305  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 00:38:49.305  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:49.305  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 00:38:49.305  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:49.725  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 00:38:49.725  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:49.725  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 00:38:49.726  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:50.005  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 00:38:50.006  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:50.006  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 00:38:50.006  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 00:38:50.553  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 00:38:50.553  SEVERE  [Thread-2 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 00:38:50.553  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 00:38:50.554  WARNING [Thread-2 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 00:38:52.535  INFO    [Thread-1 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

panos · July 11, 2025, 10:56pm

Hey @Sebastian ,

First step of the way! This sounds like the Teltonika AVL ID parameters script you used in your Teltonika Device Configuration asset wasn’t parsed correctly. Can you compare the FMC003 and your device’s parameter list, and ensure that the keys line up? What seems weird is that AVL ID 01 shouldn’t exist, it should just be 1.

Let me know what you see!

panos · July 11, 2025, 11:20pm

@Sebastian , another thing that could be useful would be to subscribe to exactly the same MQTT data topic of the device with an MQTT client like MQTTX. This will show you the exact data being sent by the device to OpenRemote. You can use that to determine why parameter 01 is not being read correctly, by matching it from the output of the parser script you add to the Teltonika device configuration.

Sebastian · July 12, 2025, 11:59am

Hey Panos,

I have started docker in the morning and the manager container kept on restarting.
After some testing and reinstalling i figured out that it happend after i pasted the result result of the Parameter ID Parser script into the “Teltonika parameter data” field and restarted.
I repeated to whole thing twice with the same result.

2025-07-12 13:27:57.221  WARNING [main                          ] emote.manager.mqtt.MQTTBrokerService.API : MQTT custom handler threw an exception whilst starting: handler=TeltonikaMQTTHandler

java.util.NoSuchElementException: No value present

	at java.base/java.util.Optional.get(Optional.java:143)

	at telematics.teltonika.TeltonikaConfiguration.lambda$new$0(TeltonikaConfiguration.java:107)

	at java.base/java.util.stream.Collectors.lambda$toMap$68(Collectors.java:1673)

	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)

	at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(AbstractList.java:720)

	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)

	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)

	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)

	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)

	at telematics.teltonika.TeltonikaConfiguration.<init>(TeltonikaConfiguration.java:106)

	at telematics.teltonika.helpers.TeltonikaConfigurationFactory.getConfig(TeltonikaConfigurationFactory.java:73)

	at telematics.teltonika.helpers.TeltonikaConfigurationFactory.createConfiguration(TeltonikaConfigurationFactory.java:28)

	at telematics.teltonika.TeltonikaMQTTHandler.start(TeltonikaMQTTHandler.java:119)

	at org.openremote.manager.mqtt.MQTTBrokerService.start(MQTTBrokerService.java:274)

	at org.openremote.container.Container.start(Container.java:167)

	at org.openremote.container.Container.startBackground(Container.java:211)

	at org.openremote.manager.Main.main(Main.java:31)

2025-07-12 13:27:57.222  SEVERE  [main                          ] org.openremote.container.Container       : >>> Runtime container startup failed

java.util.NoSuchElementException: No value present

	at java.base/java.util.Optional.get(Optional.java:143)

	at telematics.teltonika.TeltonikaConfiguration.lambda$new$0(TeltonikaConfiguration.java:107)

	at java.base/java.util.stream.Collectors.lambda$toMap$68(Collectors.java:1673)

	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)

	at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(AbstractList.java:720)

	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)

	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)

	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)

	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)

	at telematics.teltonika.TeltonikaConfiguration.<init>(TeltonikaConfiguration.java:106)

	at telematics.teltonika.helpers.TeltonikaConfigurationFactory.getConfig(TeltonikaConfigurationFactory.java:73)

	at telematics.teltonika.helpers.TeltonikaConfigurationFactory.createConfiguration(TeltonikaConfigurationFactory.java:28)

	at telematics.teltonika.TeltonikaMQTTHandler.start(TeltonikaMQTTHandler.java:119)

	at org.openremote.manager.mqtt.MQTTBrokerService.start(MQTTBrokerService.java:274)

	at org.openremote.container.Container.start(Container.java:167)

	at org.openremote.container.Container.startBackground(Container.java:211)

	at org.openremote.manager.Main.main(Main.java:31)

The parameter list looks similar to the the FMC003 to me. But with other values.
Is the “Teletonika paramter data” field the right place to paste it?

parameter list

panos · July 12, 2025, 12:16pm

Good morning @Sebastian ,

The error is caused because the Model Number attribute of the Teltonika Model Configuration Asset is not set when updating the Teltonika Parameter Data field. Please update that first and then update the parameter data.

The parameter data you attached looks correct, I pasted it into Json Grid Viewer Online - All-in-One Solution and the table seemed to be correct.

Hope this helps!

Sebastian · July 12, 2025, 3:06pm

Thank you Panos

It looks much better now. After i entered the notes, model and parameter data in the right order, the parameter map was filled automatically.
MQTTX shows messages like
{"state":{"reported":{"ts":1752327771000,"pr":0,"latlng":"??.921800,?.091858","alt":39,"ang":0,"sat":7,"sp":0,"evt":0,"239":1,"240":0,"21":4,"200":0,"69":1,"250":1,"181":64,"182":43,"66":14438,"67":0,"68":0,"10800":0,"72":260}}}
id72 = 26°C, yepp pretty warm in here
I have added a car asset, chose the FMC234 as parent and entered the model and imei number.
Is this the moment when it should appear on the map?

panos · July 12, 2025, 3:13pm

Hey @Sebastian ,

Happy to hear the parameter map was parsed correctly. Thing is, at this point, if the actual data was being transmitted correctly to OpenRemote, this is the point that you would actually see a Vehicle asset being created automatically with all of the car’s data. You don’t need to create one yourself, it will be created automatically by OpenRemote.

Can you see any relevant Docker logs about the device connecting/disconnecting from the MQTT broker? Maybe when turning the device off and on?

Sebastian · July 12, 2025, 3:23pm

Yes there are some errors.

2025-07-12 16:26:40.117  INFO    [Thread-2 (ActiveMQ-serve..939)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-12 16:26:40.586  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:26:40.586  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 16:26:40.586  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:26:40.586  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 16:26:41.427  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:26:41.427  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 16:26:41.427  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:26:41.427  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 16:26:41.746  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:26:41.746  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 011C0001C80110F00F805F37E155AA9BBA2A0AE28B00550D01000E020C081C0001C50110D60B805F37E155AA81B62A0AE28B00550D01000E020BEA not found in finalParams

2025-07-12 16:26:41.746  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:26:41.746  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 011C0001C80110F00F805F37E155AA9BBA2A0AE28B00550D01000E020C081C0001C50110D60B805F37E155AA81B62A0AE28B00550D01000E020BEA not found in finalParams

2025-07-12 16:26:43.725  INFO    [Thread-1 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

2025-07-12 16:27:39.394  INFO    [Thread-4 (ActiveMQ-serve..939)] atics.teltonika.TeltonikaMQTTHandler.API : CONNECT: Device 002 connected to topic master/002/teltonika/123456789054321/commands.

2025-07-12 16:27:40.283  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:27:40.284  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 16:27:40.284  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:27:40.284  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 0 not found in finalParams

2025-07-12 16:27:41.288  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:27:41.288  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 16:27:41.289  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:27:41.289  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 01 not found in finalParams

2025-07-12 16:27:41.595  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : Failed to payload.state.GetAttributes

2025-07-12 16:27:41.596  SEVERE  [Thread-8 (ActiveMQ-clien..ads)] elematics.teltonika.TeltonikaDataPayload : java.lang.IllegalArgumentException: Key 011C0001C60110F00F805F37E155AA9BBA2A0AE28B00550D01000E020C08 not found in finalParams

2025-07-12 16:27:41.596  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : Could not parse Teltonika device Payload.

2025-07-12 16:27:41.596  WARNING [Thread-8 (ActiveMQ-clien..ads)] atics.teltonika.TeltonikaMQTTHandler.API : java.lang.IllegalArgumentException: Key 011C0001C60110F00F805F37E155AA9BBA2A0AE28B00550D01000E020C08 not found in finalParams

2025-07-12 16:27:42.835  INFO    [Thread-2 (activemq-netty..ads)] atics.teltonika.TeltonikaMQTTHandler.API : DISCONNECT: Device 002 disconnected from topic master/002/teltonika/123456789054321/commands.

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327771000,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":7,"sp":0,"evt":0,"239":1,"240":0,"21":4,"200":0,"69":1,"250":1,"181":64,"182":43,"66":14438,"67":0,"68":0,"10800":0,"72":260}}}
2025-07-12 15:43:37:239

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327779011,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":7,"sp":0,"evt":10828,"10828":"01"}}}
2025-07-12 15:43:38:316

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327779021,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":7,"sp":0,"evt":10829,"10829":"011C0001C40110F00F805F37E155AA9BBA2A0AE28B00550D01000E020BFE1C0001C50110D60B805F37E155AA81B62A0AE28B00550D01000E020BEA"}}}
2025-07-12 15:43:38:619

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327831000,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":8,"sp":0,"evt":0,"239":1,"240":0,"21":4,"200":0,"69":1,"250":1,"181":27,"182":15,"66":14437,"67":0,"68":0,"10800":2902,"72":260}}}
2025-07-12 15:44:38:336

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327839011,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":8,"sp":0,"evt":10828,"10828":"01"}}}
2025-07-12 15:44:39:607

Topic: master/002/teltonika/123456789054321/dataQoS: 0

{"state":{"reported":{"ts":1752327839021,"pr":0,"latlng":"$$.021800,$.091858","alt":39,"ang":0,"sat":7,"sp":0,"evt":10829,"10829":"011C0001CA0110F00F805F37E155AA9BBA2A0AE28B00550D01000E020C081C0001C50110D60B805F37E155AA81B62A0AE28B00550D01000E020BEA"}}}

panos · July 12, 2025, 3:45pm

Hey @Sebastian ,

The logs and payloads you sent over were very helpful.

Parameter with AVL ID 10829 is the one that is causing the issue. The parameter 10829 is a parameter that is not included in the Teltonika wiki page for the FMC234, it apparently is an EYE Proximity mode parameter. The Python script you ran uses the Wiki page of the device you submitted to retrieve the AVL ID parameter data. Disabling that AVL ID from being sent, or manually editing the Teltonika configuration parameter data you add to the Teltonika model configuration to include it, would probably solve the issue.

You can read more about the parameter here. Apparently, the parameter contains the data of an EYE beacon when it is currently between the RSSI proximity boundaries you have set in your configuration. Maybe this will help you with adding the parameter to your FMC234 parameter data.

The weird issue is why for this particular case, the code I’ve written tries to parse the start of the 10829 parameter ID’s value as a key itself. I’ll try to figure that one out.

Please test one of those options out and let me know.

panos · July 12, 2025, 4:04pm

@Sebastian actually, I think this is happening for all EYE parameters, as (part of) the value they send is actually being used as a key to look up the parameter data.

The parameters that can be read from the payload are only the ones that are included in that JSON you input, meaning the AVL IDs on the wiki page of the device you’re reading them for.

Sebastian · July 13, 2025, 7:04pm

Hello Panos,

disabling the EYE sensor scan helped. It appeared in openremote, finally
There are many possible AVL’s that might appear when the eye function is turned on.
Since they are binary coded and I don’t need the sensor right now, I won’t add them to the parameter data.
If you have any future plans to add eye sensor support and need some data for testing, let me know.
Now I will try to get familiar with openremote.

Thank you for your help and your patience!

cheers
Sebastian

panos · July 14, 2025, 2:58pm

Hey @Sebastian ,

Happy to hear that you got it working! I’d love to hear from you if you have any feedback after testing

Have fun with OpenRemote!