Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home Assistant showing all sensors as unavailable #182

Closed
evilpig opened this issue Apr 26, 2024 · 6 comments
Closed

Home Assistant showing all sensors as unavailable #182

evilpig opened this issue Apr 26, 2024 · 6 comments
Assignees
Labels
question Further information is requested

Comments

@evilpig
Copy link

evilpig commented Apr 26, 2024

This has been going on for a few weeks, was working great but now I have to reload the onstar2mqtt docker container and then all the sensors will show up, but then shortly after all sensors say unavailable and stay that way until I reload the container again.

I can still start my car from HA and the connection is working. My logs on the container show the plugin is grabbing my car info correctly, and my other MQTT plugins are working fine. Not sure where the disconnect is here.

image

image

As soon as I restart the container:
image

My HA MQTT integration diagnostics shows the data is there.
image

Also shows unavailable as of a couple days ago which was an hour or so after I rebooted it the last time.

image

Appreciate any insight or help with this. Was working so well prior to this!

@BigThunderSR
Copy link
Owner

Are you able to use my add-on instead of running your own Docker container? Nothing obvious is coming to mind right now on what the issue may be, so trying to isolate the issue to your specific Docker environment by having you try and use my add-on instead.

@evilpig
Copy link
Author

evilpig commented Apr 26, 2024

I'm using Home Assistant also in another Docker container which doesn't support add-ons, sadly. But it's strange I haven't really messed around or changed anything it just stopped working properly I've been too busy to even mess around with anything.

I rebooted onstar2mqtt when I posted this and it still seems to be working. So fingers crossed it fixed itself this time? Too early to say I'll update if it goes back to unavailable.

I have 3 containers relevant to this:
Home Assistant
Mosquito
Onstar2mqtt

(And Govee2mqtt for my lights which is working fine so I know it's not a mqtt connection issue)

@BigThunderSR
Copy link
Owner

It's possible that you have more than one of those containers running at the same time. I've seen behaviors like what you are seeing when more than one instance of the application is running at the same time. Are you able to confirm that there is absolutely only one instance of onstar2mqtt currently running in your network?

@BigThunderSR BigThunderSR added the question Further information is requested label Apr 26, 2024
@evilpig
Copy link
Author

evilpig commented May 8, 2024

Sorry for the delay, only one of each container running and still only works upon a reboot of your plugin for a short period of time.

@BigThunderSR
Copy link
Owner

BigThunderSR commented May 9, 2024

Sorry, I'm out of ideas on this one since I cannot replicate the issue. I'm hoping one of the many folks who are currently using this can share their thoughts.

Do you know at which version the issue started?

@BigThunderSR
Copy link
Owner

Closing per samrum/OnStarJS#233 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants