Startline: no way to know - is car moving

ildar170975 commented 1 year ago

The problem

Currently there is no way to know if a car is moving or not. At least I do not have a corresponding sensor for Starline S96. According to official Starline API, it is possible to retrieve and process a corresponding data. Also, this flag is available in web site.

What version of Home Assistant Core has the issue?

2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Starline

Link to integration documentation on our website

https://www.home-assistant.io/integrations/starline/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @anonym-tsk, mind taking a look at this issue as it has been labeled with an integration (starline) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `starline` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign starline` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

starline documentation starline source _{^{(message by IssueLinks)}}

Anonym-tsk commented 1 year ago

Which method of starline api provides this information?

ildar170975 commented 1 year ago

Cannot tell anything about a particular method, I am a user, not a programmer here. In a mobile client (and in a web client as well) a user can see:

a “moving” flag - it is displayed as a working engine on a picture (probably this is not exactly a “car is moving” signal, it is an “engine on” signal);
a current speed (shown on a map).

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 year ago

up

issue-triage-workflows[bot] commented 11 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 11 months ago

Up. If the Startline service allows to get this info (which I do not know for sure - but I can see a speed in the Starline web interface) - then this info should be provided by the Starline integration as well.

rvalitov commented 9 months ago

Engine status already available in this integration. Regarding the vehicle speed - it's useless because data update via API is very slow and the speed will be very inaccurate.

Anonym-tsk commented 9 months ago

Where you want to have speed information? Additional sensor? Attribute in device_tracker?

ildar170975 commented 9 months ago

@Anonym-tsk

Where you want to have speed information?

Suggest to create a separate sensor with device_class: speed which is initially disabled.

@rvalitov

Engine status already available in this integration

It does not reflect "moving or not" as I noticed.

Regarding the vehicle speed - it's useless because data update via API is very slow and the speed will be very inaccurate.

I see on Starlink web interface when looking on a card that speed is changing - it seems to be updated as frequent as a geoposition (I could be wrong).

rvalitov commented 9 months ago

I see on Starlink web interface when looking on a card that speed is changing - it seems to be updated as frequent as a geoposition (I could be wrong).

True, the information is updated frequently at Starline part (web & app). I mean that according to the manual the Starline integration communicates with Starline servers via the API which has a serious rate limiting. As far as I understand, HA will get this speed information every 5 minutes or 3 hours. However, I don't know if HA during the API call will receive speed as a single value or as an array - a smooth list of speed values since last API call. If it's an array - then it's OK. If it's a single value, then it will be very inaccurate and I don't see any practical usage of this. Perhaps, @Anonym-tsk can comment how it could really work.

Regarding checking the status of car moving or not, I would check if GPS location of the car changed or not since last API call. A custom binary sensor in HA would work, I guess. But anyway the main problem here is that all the data does not update in real time and has quite a delay because of API communication rate limiting...

ildar170975 commented 9 months ago

@rvalitov

Regarding checking the status of car moving or not, I would check if GPS location of the car changed or not since last API call.

This is what I do currently ))

If it's an array - then it's OK

Even this approach is not useful for users (if historical data are presented as an array). Such data cannot be explicitly used to build graphs.

issue-triage-workflows[bot] commented 6 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 6 months ago

up

Grifindorec commented 4 months ago

Hello @Anonym-tsk I think we can get this state from topic "run". Can u add it to sensor?

issue-triage-workflows[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 month ago

Up

home-assistant / core