Some notifications via app and Telegram not working

Walter Spada5 days ago

Hello, I currently am using Traccar 6.9.1 and h02, gt06 but mostly devices with Huabao protocol. (at least the ones which I found this issue)

I have made custom commands to enable and disable alarms.
I have made custom commands to send notifications type programming to the devices. (SMS, app, call)
I can send the enable and disable notifications custom command and they will enable or disable.
I can send the notification type programming custom command and they will change. (device report via SMS shows the correct way enabled for them after any change using custom command from the app)

But some notifications will never reach it's destination.

There's programmed notifications for entering/leaving geofences, for overspeed and for battery loss/cut alarm which will reach user on any programmed means. (Telegram and/or traccar manager app)

But there's notifications or alarm situations like vibration and engine start/stop that will not reach the user except via SMS.

ALL notifications have -SMS, app, call- option, I can use 1, 2 or the 3 of them, and only for this last ones traccar will not send app notification (that would also be sent to telegram)

API key for notifications is not, because some reach telegram and some are sent via the app.
API for telegram bot is not, because some reach telegram without issue.
Notifications are linked to the devices and to the user/s.
Device/s are linked to the user/s.

I think it might be something between the device alarm notification sent to traccar and if/how traccar will receive and interpret/decode the notification.

I searched the log and there's something being sent from the device to traccar, but I can't decipher what it is because there's no translation from traccar (for speed and position it will show the decoded message right below the original, but not for these.) and trying to decode using a tool I receive a "bin hex can't be converted to text)

¿Is there anything I can do to solve/diagnose this?
¿is me missing something or might be something missing in the protocol support that I should get from manufacturer?

Anton Tananaev5 days ago

First thing you should check is whether you're receiving the value (in position) and if the event is generated (not notification).

Walter Spada4 days ago

Hello and thanks for your answer.

On log file there's something (event?) generated, a position that's been filtered by static filters and several other lines that I cannot decode.

At the time I received the alarm notification via SMS, this was generated in the traccar log. Nothing else before or after from this device since it was static and the alarm condition stopped.

2025-10-10 17:59:27  INFO: [devconnid: huabao < DEVICE.IP] 7e00020000DEVICEMFGRID033cfe7e
2025-10-10 17:59:27  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID0000033c0002007a7e
2025-10-10 17:59:40  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID033d000100000000000e02142b500359836c0000000000002510110459370104000ffb5f30011f31010c5708000000000000000082020083b07e
2025-10-10 17:59:40  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID0000033d0200007b7e
2025-10-10 17:59:42  INFO: [devconnid: huabao < DEVICE.IP] 7e0200004bDEVICEMFGRID033e000000000000000c02142b500359836c0000000000002510110459380104000ffb5f30011f310100570800000000000000009f133734382c30312c37642c3061616230312c3331820200837a7e
2025-10-10 17:59:42  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID0000033e020000787e
2025-10-10 17:59:43  INFO: Position filtered by Static filters from device: DEVICEMFGRID
2025-10-10 17:59:44  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID033f000000000000000e02142ae803598438002c0037009e2510110459430104000ffb5f30011f3101085708000000000000000082020083ac7e
2025-10-10 17:59:44  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID0000033f020000797e
2025-10-10 17:59:45  INFO: Position filtered by Static filters from device: DEVICEMFGRID
2025-10-10 17:59:46  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID0340000000000000000e02142af603598422002c004a00862510110459440104000ffb5f30011f31010a5708000000000000000082020083b77e
2025-10-10 17:59:46  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID00000340020000067e
2025-10-10 17:59:47  INFO: Event id: DEVICEMFGRID, time: 2025-10-10 17:46:12, type: deviceStopped, notifications: 0
2025-10-10 17:59:47  INFO: [devconnid] id: DEVICEMFGRID, time: 2025-10-10 17:59:43, lat: -WW.xxxxx, lon: -YY.xxxxx, speed: 3.0, course: 158.0
2025-10-10 17:59:48  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID0341000000000000000e02142b0003598401002b006f006a2510110459450104000ffb5f30011f31010a5708000000000000000082020083ad7e
2025-10-10 17:59:48  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID00000341020000077e
2025-10-10 17:59:49  INFO: [devconnid] id: DEVICEMFGRID, time: 2025-10-10 17:59:44, lat: -WW.xxxxx, lon: -YY.xxxxx, speed: 4.0, course: 134.0
2025-10-10 17:59:50  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID0342000000000000000e02142afe035983f2002a002501452510110459460104000ffb5f30011f31010a5708000000000000000082020081c17e
2025-10-10 17:59:50  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID00000342020000047e
2025-10-10 17:59:51  INFO: [devconnid] id: DEVICEMFGRID, time: 2025-10-10 17:59:45, lat: -WW.xxxxx, lon: -YY.xxxxx, speed: 6.0, course: 106.0
2025-10-10 17:59:52  INFO: [devconnid: huabao < DEVICE.IP] 7e02000036DEVICEMFGRID0343000000000000000e02142afa0359840b0026000001452510110459490104000ffb5f30011f31010957080000000000000000820200811f7e
2025-10-10 17:59:52  INFO: [devconnid: huabao > DEVICE.IP] 7e80010005DEVICEMFGRID00000343020000057e
2025-10-10 17:59:53  INFO: [devconnid] id: DEVICEMFGRID, time: 2025-10-10 17:59:46, lat: -WW.xxxxx, lon: -YY.xxxxx, speed: 2.0, course: 325.0
Anton Tananaev4 days ago

Looks like you configured a filter that's filtering a lot of your data.

Walter Spada4 days ago

That's not the raw log, I just replaced the identifiers for the device, it's IP and remove any data from other devices. Otherwise that would be a very long text and expose my devices.
I tought there's info. enough to see that events are being made/triggered.

I just deleted notifications and made them again, tested and they were sent.
If now they all work (will have to wait until some other alarm condition to be triggered) then the issue comes from older versions of traccar because in the past some times I lost notifications randomly and had to delete and recreate them in order for them to keep working. This has not being happening for some time so I tought it was corrected and forgot about it.

Walter Spada3 days ago

Nothing changed. Still missing app notifications for certain alarms.