bjhiltbrand / drone_mobile_home_assistant Goto Github PK

Reported in Home Assistant Logs:

Temperature sensor (<class 'custom_components.drone_mobile.sensor.CarSensor'>) does not inherit SensorEntity, this will be unsupported in Home Assistant Core 2022.7. Please report it to the custom component author.

Looks like I'll be looking to pull my Viper Smart Start out and put in a Drone Mobile. I can't for the life of me find a component to get Viper into Home Assistant. I have had it on ST and Hubitat as other people built it out. Their api is undocumented and not easy with refresh tokens etc. So not sure if anyone is willing to assist or not....but with this....I just don't want to spend the money lol.

after an upgrade to HA 2022.7 I an unable to see sensor data. I haven't dug into it yet, but posting incase someone already has.

I'm curious about this integration. It requires my username/password. Where are these credentials stored and is it safe to use?

Firstly, it works great as is, I got it plugged into HA with ease, thank you. But is there any way to force a refresh of the car without interacting with the drone mobile application? When I configured this, it showed the location of my vehicle at a place I was at like 3 weeks ago (the last time I opened the app to remote start).

as stated, my device tracker for vehicle is reading unknown, as well as temp and a few other sensors.

lock/unlock/panic/start works.

I removed integration, and relaoded re added signed in, same thing.

Hello

I know this project isn't maintained but I at least wanted to put this here as a note- seems this integration has finally stopped working for me- I was getting lots of invalid auth errors- I tried to remove and re-add the integration but I get the error above- and this error in the logs:

403 Client Error: Forbidden for url: https://cognito-idp.us-east-1.amazonaws.com/

Not sure if dronemobile changed their api access or maybe it's just a standalone issue for my HA Instance

Hey bud! Thanks again for taking this and making it better than the hackneyed cobble script i had for this. ;-)
I have been have some occasional difficulties with the remote start switch. It likes to stay 'on'.
I was thinking since remote start/stop are simply pushing a momentary switch (a button) electronically, and if you send a either remote_start or remote_stop via postman, regardless of state, it just 'pushes the button' ( sorry for the malformed sentence grammar/punctuation is not my forte.) maybe the start/stop switch should just be a button? I already need a refresh + check engine status + switch-toggle in my start script. /shrug just a thought.

Also, I found an interesting api call the other day when I was poking around bc the script stopped working for a couple days.

/api/v1/alert/event?from_date=2023-01-23T14:14:07Z&alert_type=remote_start_event&alert_type=remote_start_fail&limit=3

and

api/v1/alert/event?limit=30&offset=0

possibly a short-lived websocket subscription for events?

The first appears to only show when a rm_start is initiated from the browser

the latter pops up when you navigate to the alerts menu.

I wonder if this can be used to lessen the amount of refreshes?