I believe it should be coming as an event
attribute.
it should but 90% i doesnt
i ve been testing it for the last 24 hours
i do receive the hex data flawlessly showing the results
but almost all my devices doesnt show the event attribute
and the few that does , will show sometimes but most of the times will not show anything
i even thout i might not be fast enough to see the attribute and tries copyattirbute in the server fo the event attribute
thank you
It probably means that your devices also reported different event type after reporting the correct one.
I figured what is the issue
When the device sense a command received it will send a reply. But the position containing the reply is being filtered by my server filter most of the times.
Is there a way to not filter the some sort of attribute so i can consistently receive the reply?
There is a way to skip filtering by an attribute presence, but not value.
is this correct
yes i only want to make my server stop skipping positions that contain event or alarm attributes
is this the way
<entry key='filter.skipAttributes.enable'>true</entry>
<entry key='filter.skipAttributes'>event,alarm</entry>
so basicaly i am working with tk 103 and tk 303 devices that use gps103 protocol
my issue is that the feedback after sending a command (engine stop , resume or arm disarm alarm) arent working , sometimes i receive the attribute event with either kt (for resume ) jt (for stop) and lt for arm , but this isnt working all the times , sometimes i receive them sometimes no , even thou in the log i alwayse receive the feed back
exemple of log
i realy need the feedback as a tracability for the user to see if his device is cuting relay or not