Support for new Bluetooth-enabled timers

How do I connect my Bluetooth timer (shooters global) to the practiscore 2 app?

@Sean_Phillips
Please read all of this thread that you are attached to. The situation is currently the same…

Now that Practicescore 2.0 is out, what timers work with it?

Hello Shooters_Global and euxx,

It appears that there are some frustrations on both sides of this conversation.

In the interest of the users, is there a way forward?

@euxx - Even if it has been stated, would you mind restating your requirements from Shooters Global?

@Shooters_Global - Even if it has been stated, would you mind restating your requirements from euxx?

Thank you both for indulging my efforts to move us all forward for the sake of the users.

1 Like

@Jim_Byers I already stated it in the previous messages in this thread.

You can also find Ken Nelson reply to other user’s comments on this same request on FB.

Shooters Global is saying that integration with Practicescore will happen by the end of the year.

After reading through this thread, it doesn’t look like this is going anywhere. From what I can tell, the ball is in SG’s court. Their having a nice Black Friday discount, but if it can’t integrate with Practicescore, it’s not worth it.

1 Like

Discussing something like system integration on the public forum is not a good business practice. Could you please sort technical stuff with Shooters Global in private e-mails and make it happen? I’m sure the whole community would greatly appreciate it if two great products become compatible. Thank you in advance.

1 Like

@Aleksej_Saskov this is PractiScore community support forum, I don’t think Shoothers Global is reading this. But I’ve no idea what is stopping them from contacting us and providing required materials.

This whole situation makes me sad. I’m working in an industry where we have a lot of different equipment that need to communicate with each other and with various software. Literally, thousands of different combinations. How is this stuff getting sorted? There are some so-called ā€œindustry standardsā€, when manufacturers make their communication protocols open, software developers make support for those protocols and newcomers just make sure that their new product supports, for example, the Konsberg protocol that everybody uses. Software developers do not have to do anything extra - they just have drivers for certain protocols implemented, and that’s it. You have several timers integrated with PS already. Have you considered making a communication protocol with one of those timers open? Then, when a new timer arrives it would not be your problem how to make it compatible - the timer manufacturer implements this open protocol support by itself, and that’s it.

1 Like

@Aleksej_Saskov the industry standards are great when you have resources to support and validate them.

Not being a hardware manufacturer and being a small team we don’t have bandwidth to develop, maintain AND then support something like that.

Any hardware issues in the field from 3rd party devices are being directed to us and it is simply not possible for us to provide support for any devices that we don’t have in our test lab. In the end it will be our problem to deal with. This has happen with the existing timers more than once and up to the point when manufacturer had to make significant firmware updates and even make major changes in their hardware.

I don’t know about you, but my SG Timer GO timer with the latest firmware 16 and the Practiscore 2 mobile app for Android 15 (Sony Xperia 1 V) doesn’t detect the timer. I even bought the Practiscore Log mobile app for a while, but it also didn’t detect anything, so I uninstalled it and requested a refund.

@euxx can you let me know how contact with support@shooters.global looks like today and whether you finally managed to get the Bluetooth communication API documentation or establish it in some other way so that the Practiscore 2 app finally supports SG timers?

@Mario_PL not sure what else you want us to tell you. We are not going around to chase device manufacturers and we are not making any profit out of these integrations.

It is up to the vendors to reach out and provide any necessary hardware and documentation to allow us to do the integration work. Number of device manufacturers did that.

This post already summed it up:

Update: SG reached out with some info, we provided our technical feedback and they are now working on addressing technical issues with their API. Basically following the script…

Closing this topic. We did all that we could.

To move forward with supporting any new devices, we need two key things: physical access to the devices and complete, up-to-date technical details (protocols, specifications, etc.). The last technical information we received from SG was in June 2022, and those details have become outdated due to SG firmware updates. Without updated materials, we simply don’t have what’s needed to do the work.

We are working closely with several device manufacturers and actively updating the app to support their products. We would be happy to collaborate with SG in the same way — the door is open.