Home Assistant 2025.10: Vehicle Status Card Visual Editor Bug
Hey folks! 👋 I've got a bit of a head-scratcher with my Home Assistant setup, and I figured I'd share it with you all. It seems like the visual editor for the Vehicle Status Card isn't playing nice with Home Assistant 2025.10. Specifically, I'm getting an error that says, "Visual editor not supported," along with a funky message about deleting a property. Let's dive into the details, shall we?
The Nitty-Gritty: What's Happening 🧐
So, here's the deal: I'm trying to add a new Vehicle Status Card to my Home Assistant dashboard. But when I try to edit it using the visual editor, I'm met with this error message at the bottom of the panel: "Visual editor not supported. Cannot delete property 'button_layout' of #
I've attached a screenshot that shows you exactly what I'm seeing. It's pretty straightforward – the visual editor just isn't working. I'm stuck trying to configure the card using YAML, which isn't the end of the world, but the visual editor is so much more convenient. It makes life easier, you know? 😉
This issue is happening on Home Assistant 2025.10.2. I haven't made any manual changes to my dashboard config. The visual editor was working for me back on 2025.06, but I hadn't needed to update anything since then. Now that I've updated the integration and am trying to add a new Vehicle Status Card, it's a no-go. The problem occurs whether I'm trying to edit a brand-new card or an existing one. That means that this error isn't limited to just one specific card; it's a general issue. I am running Home Assistant on a Raspberry Pi 4b with 8GB of RAM. My environment is a Chrome browser Version 141.0.7390.77 (Official Build) (arm64) on a MacBook Pro Tahoe.
Impact of the Bug
This bug impacts the user experience because it prevents users from easily configuring the Vehicle Status Card through the visual editor. The visual editor offers a more user-friendly and intuitive way to set up the card, especially for those who are not as comfortable with YAML. This can be a barrier for new users or those who prefer a visual interface. Users are forced to rely on YAML configuration, which can be more time-consuming and error-prone. This issue therefore reduces the ease of use and the overall accessibility of the Vehicle Status Card, potentially leading to frustration among users and a diminished user experience.
Digging Deeper: The Details 🕵️♂️
Let's get into the specifics. I'm running Home Assistant 2025.10.2. I've checked my dashboard config, and there haven't been any other manual changes. The visual editor for this card was working just fine back on 2025.06, but since then, I hadn't touched anything. Now, after updating the integration and trying to add a fresh Vehicle Status Card, I'm hitting this wall. It's not just a problem with new cards; existing ones are also affected. This is a bit of a bummer, because the visual editor makes it super simple to customize the card to your liking.
The version of the Vehicle Status Card I'm using is v1.17.0. My environment is as follows: Chrome browser Version 141.0.7390.77 (Official Build) (arm64) on a MacBook Pro Tahoe, and Home Assistant running on a Raspberry Pi 4b 8GB. I've attached a screenshot of the error message to help you all visualize what I am seeing when I attempt to edit the card. It clearly shows the "Visual editor not supported" error and the "Cannot delete property 'button_layout' of #
Troubleshooting Steps Taken
I have tried a couple of initial troubleshooting steps, such as refreshing the browser, clearing the cache, and restarting Home Assistant. Unfortunately, none of these actions resolved the issue. The error persisted across multiple attempts and after the restarts. These are common troubleshooting steps and are often the first thing people try when encountering such issues. The fact that these actions did not work suggests that the problem is not a temporary glitch or a simple caching issue, and might point to a deeper problem within the integration or Home Assistant itself. I am now reaching out to the community to see if anyone else has experienced this issue and if there are any known workarounds or solutions. I'm hoping that someone might have encountered a similar situation and can provide some guidance or insight into how to fix the error.
The Big Question: What's the Root Cause? 🤔
So, what's causing this problem? I'm not entirely sure, but here are a few potential culprits:
- Compatibility Issues: It's possible that there's a compatibility issue between the Vehicle Status Card (v1.17.0) and Home Assistant 2025.10.2. Maybe there have been changes in the Home Assistant core that the card hasn't fully caught up with. This can happen, especially when new versions of Home Assistant introduce breaking changes or modifications to the way integrations interact. The "Cannot delete property 'button_layout' of #
- Integration Bugs: There might be a bug within the Vehicle Status Card integration itself. Maybe the visual editor code has a glitch that's causing it to fail in this specific version of Home Assistant. If this is the case, the developer of the integration would need to address the bug by updating the code. It is even possible that there may have been an update to a related library that this card depends on, which may have introduced a new conflict. The developer could have to make changes to make it work.
- Dashboard Configuration Problems: I've checked my dashboard config, but there's always a chance that a slight configuration error could be causing the issue. Although I haven't made any manual changes, a minor conflict could still be present. It is also possible that a more recent Home Assistant update has changed the way the dashboard elements are rendered. This could then, in turn, cause a conflict with the way the Vehicle Status Card is trying to interact with the visual editor.
What Can We Do? 💡
So, what are the next steps? Here are a few things we can try:
- Check for Updates: Make sure the Vehicle Status Card integration is up-to-date. The developer may have already released an update to fix this issue. Check the Home Assistant integration page or the card's GitHub repository for the latest version. Sometimes, the fix is as simple as updating to the newest release!
- YAML Workaround: In the meantime, you can use YAML to configure the Vehicle Status Card. It's not as convenient, but it's a workaround that'll get the job done. This is the least disruptive method. It allows you to continue using the card while waiting for a fix.
- Report the Bug: If the issue persists, report it to the Vehicle Status Card developer. They can investigate the problem and hopefully release a fix. You can report it either in the official Home Assistant forums, in the card's issue tracker on GitHub, or wherever the developer is active.
- Community Support: Ask for help from the Home Assistant community. Post in the forums or on social media and see if anyone else has encountered the same problem. They may have a solution or a temporary workaround. Getting help from other users can also help to bring this issue to the attention of the developer. Someone might already have a solution ready to go.
- Downgrade Home Assistant (if possible): If the bug is critical and you cannot wait for a fix, you can consider downgrading your Home Assistant version to 2025.06 (if you have a backup). Make sure to back up your system before downgrading and be aware of any potential security risks that might come with running an older version. It is important to note that downgrading should be considered only as a last resort. This could be useful if you depend on the visual editor for the proper functionality of the card.
Conclusion: Let's Get This Fixed! 💪
This visual editor issue is a bit of a pain, but hopefully, we can get it sorted out. I'll keep you all updated on my progress. If any of you have any insights, suggestions, or solutions, please share them in the comments below! Let's work together to fix this bug and get our Vehicle Status Cards back in working order. Thanks for reading and happy automating!
I hope that this information is valuable and useful for you. Feel free to use the steps and suggestions provided here for any help you may need. If you have any questions or feedback, please feel free to ask me. Thanks for your understanding and cooperation.