questions about smarteye WEB SDK/API

arie

Dear …
We have a problem while trying to logon using the API’s {user logon} endpoint. So we have a question now.

Q1: Which documentation page correctly describes the login logic:

https://smarteye.besovideo.com/doc/bvcspapi/index.html
with password_encrypted = SHA256({username}_{password}) like “SHA256:6848d6405bf34bf9b2d82ed8822c756807632d3eaefedec90ac33cb32ac83671”

or

https://smarteye.besovideo.com/bvdoc/

with password_encrypted = SHA256( SHA256({username}_{password})_{timestamp} ) like “SHA256_T:ebc145ec6decbc3e7842f1fbc2bd6d0cf65e76f1dc3b7e21ebfd01a5c5a8c65a”

?

Even when I try both(!), I still get StatusCode=200(OK) but the JSON shows me an error like

{
    "code": 14
    , "msg ": "Password Error. remaining count:0"
    , "data":
        {"token": "_v0uoRImxxkTcwWnZ8_IYrw"
        , "timeout": 0
        , "appID": 0
        , "remaining": 0
        , "locking": 0
        , "change_password": false
        }
}

? What can be wrong here?

This is my C# code:

besovideo

pls enable GPS access always, while by default it's only in APP use, and it's not considered as in use while screen is OFF.
so pls make it always here.

arie

GPS problem bodycam:

We request the location of the bodycam every minute via the API with: {GET "pu/gpsdata/<puid>"}
This API command works well.
Only what we noticed is that the GPS position was very poor.
Until we discovered that the GPS position is perfect when the bodycam screen is on.
The same also applies to the besovideo VMS website.
There you will see that location only works good when the bodycam screen is on. (see video on WeChat from last Thursday)

This all has to do with the software on the bodycam in my opinion.
It seems like the GPS goes to sleep or something similar when the screen is off.

I hope you can fix this in the software. This is very important for our business case.

If this can be resolved, I promise that we will start with an order for 100 body cameras and also several IP cams.

If you need to adjust the MCP software for this, please let me know because we would like to have a few simple things adjusted in the BA280 MCP software.

--For example, never use the blue/red emergency lights for an SOS alarm

--Start recording when you create an SOS alarm.

--And slightly extend the time you can press the SOS button. Now to make an SOS you only have to press it briefly. If you press a little too long (for example 2 seconds), it will not sound an alarm. Users are used to having to press our other buttons for 2 to 3 seconds.

--And if possible, the MobileTrack logo instead of the Smarteye logo when starting the camera.

coldflame

there is a calling sequence to obtain correct position on map per our talk in wechat.
any further problem, let's go on here.

arie

IBeli post on2024-12-16 08:31
Is the response location always not good？
There has a config on device to control the interval t ...

Hi we have set the interval time on 5 seconds (also tried 30 and 60 seconds)
(See picture 1)
We check the location in MCP (in Map) and that location is correct. (see picture 2)

But when we ask for the location it is the location from 60km away.
This morning i did a car drive for 60km (from home to work address)
On the device in MCP i can always see the good location.
We ask the API for the GPS latitude and longitude every minute but it is still at my home address.

So it seems that the bodycam has a good location but the MCP app does not send that location to the server.
What can we do for that? The location is very important for us!

IBeli

arie post on2024-12-16 02:13
Hi,

We have a problem with the GPS position from the bodycams.

Is the response location always not good？
There has a config on device to control the interval time of device post gps location.

arie

IBeli post on2024-12-13 17:59
Now thoes apis is not exist.
We can add those apis, if you pay for that.
You must know:

Hi,

We have a problem with the GPS position from the bodycams.
The bodycams have a good GPS position.
We can see that in the MCP app and in android.
But when we ask for the GPS position with "{pu/gpsdata/{puid}} endpoint" than the location is not good and not the same latitude and longitude as the real location.
What can we do about this?

IBeli

arie post on2024-12-13 04:40
Hi question about the API:

Is it possible todo the following for you guys?

Now thoes apis is not exist.
We can add those apis, if you pay for that.
You must know:
Get Battery lever of a list of pu, server will send to each of those pu, wait for every pu response, It will make the Get be slow.
Gpsdata request also.

arie

Hi question about the API:

Is it possible todo the following for you guys?

Put the {battery level} into the result of the {pu/list} endpoint instead of the {pu/power/battery/{puid}} SINCE that (a) takes additional request and (b) ONLY 1 per device as we need for ALL devices AT ONCE!
Same for the {pu/gpsdata/{puid}} which gives us the location. We need to get ALL of this AT ONCE, please!
So, if we have 10 cameras we need to make 1 request to get all the information instead of 1 + 10x + 10x = 21x !
This takes more time and uses a lot of resources as we need to get it each MINUTE!

IBeli

arie post on2024-12-10 19:46

There has two questions.
1.Content Security Policy made the worker couldn’t be constructed
2.wss can’t connect to xxxxx：9702

Could you provide a todesk or other  Remote Desktop