LX42-EA

Nikolai Anastasov 23 days ago
[Te14346fe] connected
2026-01-14 21:14:43  INFO: [Te14346fe: gt06 < 95.42.71.188] #BCE#\r\n
2026-01-14 21:14:46  INFO: [Te14346fe: gt06 < 95.42.71.188] f24cbb60e41603005300a50150f746450ffbc0ffcf05004ed3df4170fe2c42000900cf0070fe2c4200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008f 

the device is offline...is the port different from its predecessor fms500light...i can't understand where i'm going wrong...please help

Nikolai Anastasov 23 days ago

I have used port 5023 ....but maybe it is not the right one..how do I find out the correct port for this device ...xirgo LX42-EA

Anton Tananaev 22 days ago

Definitely not the right port. Do you hsve the protocol documentation?

Nikolai Anastasov 22 days ago
Anton Tananaev 22 days ago

That seems like the IOTM protocol, port 5218.

Nikolai Anastasov 22 days ago
2026-01-15 20:23:49  INFO: [Tc89dcb9f] connected
2026-01-15 20:23:50  INFO: [Tc89dcb9f: iotm < 79.100.25.170] #BCE#\r\n
2026-01-15 20:23:53  INFO: [Tc89dcb9f: iotm < 79.100.25.170] f24cbb60e41603005300a50150f746450ffbc0ffcf05004ed3df4170fe2c42000900cf0070fe2c4200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008f
2026-01-15 20:24:17  INFO: [Tbed3c921] connected
2026-01-15 20:24:18  INFO: [Tbed3c921: iotm < 79.100.25.170] #BCE#\r\n
2026-01-15 20:24:21  INFO: [Tbed3c921: iotm < 79.100.25.170] f24cbb60e41603005300a50150f746450ffbc0ffcf05004ed3df4170fe2c42000900cf0070fe2c4200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008f     

Unfortunately, I have no progress on 5218, and my provider claims that everything is OK with them.
The device is in the "no connection" status.

Nikolai Anastasov 22 days ago
2026-01-15 21:01:53  INFO: [Tf141b1e2] disconnected
2026-01-15 21:01:53  INFO: [T3a3ef2eb] connected
2026-01-15 21:01:53  INFO: [T3a3ef2eb: gps103 < 87.236.176.248] f9beb4d976657273696f6e000000000056000000785b642d801101000000000000000000a139696900000000000000000000000000000000000000000000ffff7f000001208d000000000000000000000000000000000000ffff7f000001208d0000000000000000000000000000
2026-01-15 21:01:56  INFO: [T3a3ef2eb] disconnected
2026-01-15 21:02:08  INFO: [T7374a695] connected
2026-01-15 21:02:11  INFO: [T7374a695: gps103 < 87.236.176.250] 0032d0010001002c10410004115e0004116d0004115a001814041403000724070008240f0008144000081474000800041147
2026-01-15 21:02:14  INFO: [T7374a695] disconnected
2026-01-15 21:02:26  INFO: [T5cde1517] connected
2026-01-15 21:02:29  INFO: [T5cde1517: gps103 < 87.236.176.228] 48454c464400000000000000ffffff7fffffff7f0000000000000000240000006f70632e7463703a2f2f6c6f63616c686f73743a343834302f5541446973636f76657279
2026-01-15 21:02:32  INFO: [T5cde1517] disconnected
2026-01-15 21:02:44  INFO: [Tf8d72a73] connected
2026-01-15 21:02:47  INFO: [Tf8d72a73: gps103 < 185.247.137.229] fb01
2026-01-15 21:02:50  INFO: [Tf8d72a73] disconnected
2026-01-15 21:03:02  INFO: [Tbfcda521] connected
2026-01-15 21:03:05  INFO: [Tbfcda521: gps103 < 87.236.176.252] 40000d00010000000000000000005104c0a83801000000000a0000003c000000c800000000000000000000000000000000000000000000000000000000000000
2026-01-15 21:03:08  INFO: [Tbfcda521] disconnected
2026-01-15 21:03:20  INFO: [T486fdbe5] connected
2026-01-15 21:03:23  INFO: [T486fdbe5: gps103 < 87.236.176.227] 101200044d5154540502003c0511000000000000
2026-01-15 21:03:26  INFO: [T486fdbe5] disconnected
2026-01-15 21:03:27  INFO: [T73392648] connected
2026-01-15 21:03:27  INFO: [T73392648: gps103 < 87.236.176.227] 100c00044d5154540402003c0000
2026-01-15 21:03:30  INFO: [T73392648] disconnected
2026-01-15 21:03:30  INFO: [T0ae4bf02] connected
2026-01-15 21:03:30  INFO: [T0ae4bf02: gps103 < 87.236.176.227] 103200064d51497364700302003c002461333863633538392d373634372d346134382d383938312d326163663737383661373634
2026-01-15 21:03:33  INFO: [T0ae4bf02] disconnected
2026-01-15 21:03:45  INFO: [Tf9963369] connected
2026-01-15 21:03:48  INFO: [Tf9963369: gps103 < 87.236.176.250] 434f4e4e4543540a6163636570742d76657273696f6e3a312e302c312e312c322e300a0a00
2026-01-15 21:03:48  WARN: [Tf9963369] error - Range [21, 24) out of bounds for length 8 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2026-01-15 21:03:48  WARN: [Tf9963369] error - Range [21, 24) out of bounds for length 1 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2026-01-15 21:03:48  INFO: [Tf9963369] disconnected   

now this is happening

Anton Tananaev 22 days ago

That's a different port, so completely unrelated.

Nikolai Anastasov 22 days ago

What do you advise me to do, the device is the same, the port is 5218... where should I look for the problem?

Anton Tananaev 22 days ago

From what I can tell, it's not working because your device is not using the protocol you provided. So you need to figure out whether they provided wrong document or there's some device misconfiguration or maybe something else.

Nikolai Anastasov 22 days ago

thanks, I will contact xirgo again and write when I have new information

Nikolai Anastasov 21 days ago

"Forwarded your device to our telemetry platform for testing. Unit started to send data which was saved to flash drive:
Unit is sending data via standard BCE protocol as your other devices, so configuration from telemetry server side should be the same as it is for FMS500 units. I would suggest you to check with telemetry server providers."

They say the problem is us.

Nikolai Anastasov 16 days ago

the device connected on port 5218
in the settings I had to write the address of my server in the MQTT BROKER ADDRESS field
thanks for your help

Anton Tananaev 16 days ago

So it worked? Why didn't it work before?

Nikolai Anastasov 16 days ago

The problem was that xirgo don't know what they are selling....we have 800 of their devices of the fm500light and fms500light model and now for the new replacement LX42-EA they claimed that it uses the same protocol, which is not true! The problem was that I didn't set up the device to work with the MQTT broker, after I changed it like that and with the port that you told me 5218 the device connected.