Welcome to ovms-home-assistant Discussions!

[enoch85]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, start a new discussion by clicking the top right option "New discussion".

If you have an issue, please create a new issue. If are a developer and want to send a PR with a fix, then kudos to you! ❤️

[mlduncombe]

Got my Smart Fortwo EQ setup last night and now have lots of OVMS data in HA.

[mlduncombe]

Sensors as of 0.3.1...

[enoch85]

That's great information, thanks!

[enoch85]

@mlduncombe Now 0.6.2 is out with some added function.

Please try it out and report back. Thanks! 🙏🏼

[mlduncombe]

Hi Daniel, now running with 0.6.2.

Saturday I plan to match the entities to the data already available in the OVMS app for the Smart Fortwo and make sure all looks good. Ill then do some debug captures and report back. In particular it would be nice to get the cabin preconditioning working. For example pressing the Homelink 1 in the OVMS App for the Smartcar button triggers this

_2025-03-14 07:58:06.509 DEBUG (MainThread) [custom_components.ovms] Parsing topic: ovms/mld/WG21OFD/notify/info/hvac/enabled
2025-03-14 07:58:06.510 INFO (MainThread) [custom_components.ovms] Creating binary_sensor: Enabled
2025-03-14 07:58:06.510 INFO (MainThread) [custom_components.ovms] Adding binary sensor: ovms_WG21OFD_notify_info_hvac_enabled
2025-03-14 07:58:06.511 DEBUG (MainThread) [custom_components.ovms] Setting EntityCategory.DIAGNOSTIC for system category: ovms_WG21OFD_notify_info_hvac_enabled
2025-03-14 07:58:06.532 DEBUG (MainThread) [custom_components.ovms] Dispatching update for wg21ofd_system_ovms_WG21OFD_notify_info_hvac_enabled_65a99e54_

Did we want to start a new thread specifically for the Smart ForTwo or are you happy for it to remain here?

[enoch85]

Please create a separate issue for this. It seems like it's trying to create a sensor, while in fact should be a command.

Try using the Developer Actions in Home Assistant instead, that's what it's made for: sending commands to the car. Search for "ovms" to get the available options.

[umbjm1]

Hi Daniel,

Thanks for all your work. I'm very new to OVMS and fairly new to HA, so some of your instructions went over my head. Would you please clarify?

I have Mosquitto broker installed with the default configuration. I created /share/mosquitto/accesscontrollist with these contents:

user addons
topic readwrite #

user homeassistant
topic readwrite #
topic read homeassistant/#

user ovms_user
topic read ovms/#
topic write ovms/+/+/client/rr/command/#
topic write ovms/+/+/status

---

Is this right? Did I put "topic read homeassistant/#" in the right place?

Do I need anything else in my configuration.yaml?

And finally (I hope), if I'm using the default Mosquitto broker with HA, what do I enter for its address in the OVMS integration?

[enoch85]

You're asking good questions! I'm also fairly new to OVMS actually. :)

Regarding ACL, go easy on yourself and allow everything to begin with. As long as the traffic is local I see no harm in doing so. If you later want to "lock down" your setup, read up on how ACL works in your broker.

My own setup is like this:

1. OVMS --> EMQX external broker (on docker)
2. EMQX ---> OVMS Home Assistant over port 8883 with the ACLs described in the README.
3. I use the same user (ovms_user) on both OVMS and EMQX.

So for Mosquito I'm not 100% sure, but basically, allow the ovms_user with the ACLS that are described in README because that's the user which is talking to the integration.

If you need further assistant I will need to setup a test bench just to try it out myself with Mosquito.

[enoch85]

Reading my own instructions, this should be enough to get started:

user ovms_user
topic read ovms/#
topic write ovms/+/+/client/rr/command/#
topic write ovms/+/+/status

[umbjm1]

I should add that I'm running HAOS alone on a NUC.

Do I need to add the ovms_user to the Mosquitto broker configuration, or is the ACL enough?

[enoch85]

@umbjm1 Did you manage to set it up? :)

[umbjm1]

Sorry, I lied. I took two days off and read up more on MQTT. Also, my wife was concerned about the time I was spending on the computer. ;-) I'll be back!

[enoch85]

No worries! :)

[umbjm1]

OK, bit by bit. I have questions marked Q1-Q6.

Again, I'm keeping everything local. I've set up an HA user with username bpoc27. My OVMS username and vehicle ID are the same. Both have the same password so I can't confuse them.

Your screenshot vs. the text above it at https://github.com/enoch85/ovms-home-assistant?tab=readme-ov-file#ovms-configuration is hard to understand, because you list out all the ports.

Here's mine. Port 1883 seems to be the default:

If I go to the terminal and type:
➜ ~ mosquitto_sub -h 127.0.0.1 -v -t "ovms/#"
I get:
ovms/bpoc27/bpoc27/status online

Q1: So the basic connection is working, correct?

I can also go to the OVMS status page and see:
OVMS V3 MQTT login successful

Q2: I get the same messages with the TLS box in the V3 config checked or unchecked. Since I'm staying local, Do I need TLS?

If I delete the OVMS integration and re-add, using
a) either the IP or localhost for the Broker Host
b) port 1883 (to match my OVMS config)
c) Verify SSL/TLS unchecked
d) username bpoc27
e) pw same as for the HA user bpoc27
f) QoS level 1

Then I submit and am presented with:

Q3: Is this correct up to this point?

When I submit that, I get:

Found 2 topics.
Sample topics:
• ovms/bpoc27/bpoc27/status
• ovms/client/rr/command/8fcda5f8
•
Potential vehicle IDs:
• bpoc27

If I click submit, I get Vehicle Config and enter my vehicle ID, also bpoc27.

I submit that, and I get:
Success!
Created configuration for OVMS - bpoc27.
We found the following devices:
OVMS - bpoc27
OVMS Module (Open Vehicles)

After I click Finish, I only have:
OVMS - bpoc27
1 device and 1 entity

I still see it connected, both in the terminal and on the OVMS status page. I can stop and start V3 there, still connected.

Q4: So where do ACL and listening/publishing entries go for my built-in Mosquitto broker? That's where I'm hung up.

Q5: In the MQTT settings, I see "Publish a packet" and "Listen to a topic." Do those need entries?

Q6: You give an "Example Mosquitto ACL Configuration," but I have no idea as to the directory and file in which those entries should reside.

Thanks for your patience.

[enoch85]

Q1: Remove 'ovms' from the topic prefix, it will then be the default.

You should get more than only the status topic.

Q2: Port 1883 are not secure, so unchecking TLS in OVMS are totally fine, and correct in your case. I'd use the IP-adress, not localhost. Make sure the IP is static.

Q3: From what you are describing it seems correct yes. But you should get more than 1 topic.

Q4: please show me your config of the ACLs you set in the broker.

Q5: Don't know, I'm not using a local broker. Maybe @andlo can help you here?

Q6: You need to login via SSH (there's an Add On for that) then look in the docs where the config file is. Maybe you can change it directly in extra parameters in the GUI? Again, I think @andlo can help you here.

[umbjm1]

Q1 & 3: Done. Now I have 171 entities, but none of them have status.

Q4-6: I don't know where to put the ACL. I have always had SSH and will try to set up directories/files as described here:
https://github.com/home-assistant/addons/blob/master/mosquitto/DOCS.md

I understand that you aren't using a local broker, but I suspect that many potential users would be in my situation. Providing local instructions might get more people to try your integration.

Finally, is @andlo here, or only at the HA forum? I could use his help.

Thanks!

[enoch85]

171 entities sounds about right! Do you get any values for those entities? Otherwise, go for a drive or something, and then see if it updates. :)

The ACL seems to be mentioned here: https://github.com/home-assistant/addons/blob/master/mosquitto/DOCS.md#access-control-lists-acls

[andlo]

Finally, is @andlo here, or only at the HA forum? I could use his help.

Yes I am here :) but bever enough time to have fun :)

I du use local MQTT as I have other integrations using MWTT, and didnt think that were an issue setting this great integration up.

[umbjm1]

...and that appears to have done it! The entity statuses appear to have been a red herring, as I see what is going on when I click on them.

Thanks!

[enoch85]

Please check here: https://github.com/enoch85/ovms-home-assistant?tab=readme-ov-file#services

[umbjm1]

Thanks.

[umbjm1]

Update: I haven't done anything with the integration, as since I've installed it the OVMS module drops the Wi-Fi connection and crashes constantly. To be systematic, I will wipe everything, reinstall, and use OVMS without the integration (assuming it works) for a week or so before trying the integration again. The crashes are so frequent that I can't finish saving all of my settings using the web interface.

[enoch85]

Hmm, strange. For me it worked straight out of the box, without any issues at all.

[umbjm1]

Not sure. For a while I thought it was hardware as yesterday I was unable to start it at all. With nothing left to lose, I pulled the box and did a hard reset using the switch on the PCB. It's been on for 20 hours straight, so I'm relieved.

I suspect that the problem may have been something I changed in the V3 settings.

[mlduncombe]

Might the OBD connector been slightly loose? Causing power to come and go. On mine, over time, the OBD connector works loose.

…

On Thu, 27 Mar 2025, 13:52 umbjm1, ***@***.***> wrote: Not sure. For a while I thought it was hardware, but with nothing to lose I pulled the box and did a hard reset using the switch on the PCB. It's been on for 20 hours straight, so I'm relieved. I suspect that the problem may have been something I changed in the V3 settings. — Reply to this email directly, view it on GitHub <#67 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNRNE6NPD2GICWRZXT4O5L2WP7BRAVCNFSM6AAAAABYTQU7OOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRUGEZTMMQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[umbjm1]

Good guess but unlikely, because I was disconnecting/reconnecting multiple times.

Today's hypothesis is that either my 12V battery needs to be replaced or that OVMS isn't measuring its voltage correctly. I've tweaked the correction in the web interface.

[enoch85]

@wayne-love You recently made some changes to Leaf, @umbjm1 are struggling with it. Maybe you have some advice?

@umbjm1 Which Leaf are you using?

[umbjm1]

I have a 2015 Leaf S, so there's no TCU to disconnect.

My OVMS has been stable for 2 days. I was thinking of trying your integration again, but instead using EQMX running on my desktop Mac. Is your EQMX bridged to another MQTT server?

[enoch85]

My setup is like this:

Send:
OVMS ---> EMQX (external broker)
Fetch:
HA (this integration) <--- EMQX

Benefits are many, automatically parsing topics being one of them, improved units handling being another.

Using an external EMQX also adds TLS, and other security benefits - like segregation of networks and such.

[enoch85]

Oh, and my uptime is 25 days.

[umbjm1]

Thanks. I think I'll keep them separate for now for easier troubleshooting.

[umbjm1]

I'm taking some time away from this, as the bridge I had set up is no longer working today. Thanks again. My OVMS is staying connected, though.