MV730G V2 - Is this fully supported?
There are different variations of H02 protocol, so it's not always possible to support all functionality. Sometimes there are conflicts.
Thanks for the quick reply!
Ah... right okay.
So im guessing it would be a case of working out the payloads myself and creating a custom H02 protocol that specifically supports the MV730G? I have had alook through the H02ProtocolDecoder.java and I think I understand it (not used to working with java). I just cant see anything obvious in the payloads that looks like voltage or battery level.
Do you by chance know of a tracker on the H02 protocol or any protocol infact that can do what im asking? External battery voltage, internal battery percent/level and also has ignition? Probably the easier route then diving into this rabbit hole!
Check protocol documents here:
@calpulz Did you make any progress with this? I have the same unit that I'm looking to deploy. What port did you end up needing to use?
Hello esteemed Traccar community,
I hope this message finds you well. I'm currently in the process of evaluating the MV730G 4G relay GPS tracker for a project, and had certain reservations concerning its compatibility with the Traccar platform. In pursuit of clarity, I directly reached out to the supplier.
Sofia, representing the supplier, responded:
Thank you very much for your attention on our MV730G 4G relay gps tracker. As I know, now the traccar platform is compatible with our MV730G device perfectly, please don't worry! If there has any issues, we will contact traccar platform to improve the integration, thanks!
She emphasized their commitment to ensuring that their products integrate seamlessly with Traccar. Furthermore, she highlighted their proactive approach, stating they are more than willing to engage with the Traccar team to improve integration if any issues arise.
I genuinely value Sofia's assurance. However, I wanted to solicit feedback from this community, given everyone's extensive experience with various devices and their integration with Traccar.
- Can anyone here verify Sofia's claims?
- If there are challenges with the MV730G device, what specific documentation or collaboration would be most beneficial from the supplier's side?
Sofia seemed eager to help. Ensuring the device's flawless operation with Traccar is paramount, and any insights to facilitate collaboration would be appreciated.
I look forward to hearing from this knowledgeable community.
Warm regards,
@xbmcnut @dcampos
So I never actually made any more progress on this. Things may have changed now since it was 9 months ago when I last tried.
But no it wasn't fully compatible with traccar. Not using the H02 protocol anyway which was the only protocol I could get any sort of results from.
Heartbeat payloads seemed to work, and also payloads when there was no GPS lock which were both returned in HEX. No GPS lock location used 4G for approximate location.
However the binary payloads when GPS lock was obtained wasn't being decoded by traccar.
That's as far as I got. I also reached out to the manufacturer and after learning that it doesn't report external battery voltage (even though some screenshots of the Micodus app did show external battery voltage) I gave up on it. I need to know external voltage for my use case.
@dcampos @Calpulz
I'm using Traccar as a Home Assistant add-on and I simply opened port 5013 on my router and pointed it to my HA instance and it worked. Of course, I had to message the unit with my DDNS address and port and set my APN. It's reporting LAT/LONG and shows the relays exact location along with ignition on/off status and I can control the relay by sending customs commands; 555 to turn the fuel off and 666 to turn it on again. I haven't put it in a vehicle yet so I can test the speed and/or speed alerts but I'll do that over the weekend. I've configured alerts to be sent via Telegram.
@xbmcnut So I had a similar setup, running Traccar docker on my Unraid server. I got everything working like you with my domain name, port etc.
Traccar just wouldn't decode or acknowledge the binary payloads. So while it looked like I had location and I could see the pin on the map, it was location data from 4G network not GPS.
But this may have changed. I'll have to give it another go.
Hi!!
So pretty new to all of this but ive made good progress. Purchased the MV730G V2 from AliExpress which I believe is the newest version.
Got it connected and communicating to my local Traccar server. But I have some issues with the protocol and missing functionality.
Im not sure if this device is fully supported with Traccar or if the manafacture has changed things about its protocol (I have emailed them, awaiting a reply).
I cannot seem to identify any information in the payloads about the internal battery level, or the external power voltage/level. The tracker can send an alarm for low voltage which can be configured to a set value via SMS. But im guessing this just sets a flag in the vehicle status part. Not sure if the actual voltage level is readable?
I believe the protocol is H02 as im getting date/time, location data. But I also seem to get binary data under certain situations. I think i get binary data when the tracker has GPS lock. Otherwise it returns payloads in HEX.
So heartbeat payloads look like this:
Payloads when there is no GPS lock look like this:
Binary Payloads when there is GPS lock look like this (I can identify some data from this, long, lat, device num which i have blanked, also date/time)
If anyone can shed some light on this that would be great.
Thanks!