2026.10 Beta week

Configuration
1

A general reminder: Beta week is not designed to fully overhaul a new feature, but to identify bugs that may be introduced with the update.

If you have an issue, please let us know here! However, the developers and product team are very active in the #beta channel of our Discord server during Beta - it’s good to hop in there if you can. To ensure things are addressed in a timely manner, be sure to also submit issues on GitHub in their proper space:

Here are this month’s Beta notes! This release has some excellent changes, and broke records for merged PRs in a monthly release (well over 2k :exploding_head:). Coming with this release are more backward-incompatible changes than we normally have - highly suggest you review them before you update so you’re prepared for anything that may impact you directly.

Here are my cliff notes for this month’s release, in order of my excitement:

  • After we moved to OpenStreetMap last release, we’ve decided to upgrade the look and feel of it to fit into Home Assistant better. The new map includes improved zoom, redesigned markers, an overview on the Map dashboard, and a better zone editor.

  • I never knew I needed to adopt the Trigger by option in my automations, this release we made it easier to use in the automation editor. And of course, we worked to make sure we didn’t break anything you’ve already set in YAML.

  • The profile page is looking a bit tidier - a neat addition with this change is that every user, admin or not, can now edit their own profile - household members can update their profile to reflect their own personality without needing to have an admin help out.

  • From the other noteworthy changes, I’m excited to see that the Home dashboard now also supports the active alerts we implemented in the Security dashboard last month, the Energy dashboard shows the discharge of each battery separately, automation traces have been updated to match the automation editor, and timers are much easier to control from your dashboards. :tada: There is a nice selection of other items there, so be sure to check out the full list to see if something there piques your own interest.

  • New integrations this month include Axle Energy, Bitvis Power Hub, Gree Infrared, INDI Allsky, KACO Modbus, my-PV, OSRAM Infrared, Persang Infrared, SolarEdge Modbus, Sunsynk, Theben Conexa Smart Meter Gateway, Threema, Vitesy, Willow, and Zonneplan. It’s awesome seeing so many new infrared and Modbus integrations being added every month. Great job to all the contributors who made it into Core this release! :clap:

    • We also have 7 new virtual integrations: Austroflamm, EcoSpar, HAAS+SOHN, HETA, O General, Onida Infrared, and Steinway & Lyngdorf.

  • Noteworthy improvements to existing integrations is an extensive list this release. :scream: Several OHF project integrations have been improved along with so many others, too many to list here actually, so click the link to see which integrations received notable improvements.

  • We had 25 integrations achieve new quality scale levels, and I believe this is the most we’ve had on the list since we started the quality scale! 10 reached Platinum, 4 reached Gold, 7 reached Silver, and 4 reached Bronze. Absolutely stellar work getting these integrations rated, devs! :partying_face:

  • We have three new integrations now available to set up from the UI: Discogs, Rejseplanen, and Volkszaehler.

  • We say farewell to a short list of integrations with APIs that simply are no longer available: Dublin Bus, Etherscan, Melnor RainCloud, Orange and Rockland Utility (ORU), Sigfox, SolarEdge Local, Travis-CI, and Zestimate.

  • I put the link to the backward-incompatible changes front and center in this post because I feel it’s important for y’all to check them out, so if you didn’t click the link then please read up on these changes now - there are some fairly popular integrations in the list this release.

We were busy over on the Developer blog during September:

The build is available now - happy testing, friends! :tada:

3

YES! That is the kind of releases we need.

4

Making MQTT.Publish an admin action is something I dont understand. I have various dashboard buttons that - in the end - cause an MQTT Publish…
What is the supposed workaround for this?

5

How do I know if this impacts me? I do have MQTT in use, but that’s about all I know.

6

Is there a reason you didn’t make an MQTT button? It’s ultimately the same thing and doesn’t use the publish action.

7

This only affects the mqtt.publish action, it also means this will only affect scripts that are called where the source of the context is from the UI. I.e. You make a script that uses mqtt.publish and place it on a dashboard, non-admin users will not be able to execute that script.

For all intents and purposes, this effects template entity actions, button helpers, and scripts that have mqtt.publish when called from the UI without an admin account.

Anything else should not be affected. This admin change was rolled out to zwave last release for a few actions.

There are ways around the restriction as well, depending on the use case. If this affects a large number of users, other options may be added in the future. However a arch discussion would need to be created and approved.

If anyone needs work arounds to get past the auth, please create support threads.

8

Thank you. I’m going to assume I don’t use that service. I read it in the release notes too. I’m guessing if I used it I would know. Haha. The joys of being a home assistant user who understands almost zero how it works. Everything it does feel magical to me :slight_smile:

9

Petro,

Now that were starting to see scripts that cannot be called fromnthe dashboard (or VPE, - script from the conversation pipe…) because the user context is non admin. Do you know if there are plans currently to expose something like… .is_admin in the context user object to the script engine.

Reason..

If you’re going to block you should give me a probe to guard and fail closed… Especially in security.

Its currently not available. It’s suddenly rather important, I’ve already hit possible uses three times this week. I can get user or null and derive user ID. But not admin status.

10

Please use the beta before making comments. Thanks

11

a. I didnt know about MQTT-Buttons
b. The scripts are doing stuff and then calling the MQTT publish, so I asume a MTT Button wouldnt help (gonna google that asap)

12

Why is MQTT.publish considered an Admin action anyway?

13

I would assume (I don’t really know) that users shouldn’t be able to wipe out topic data, which this would allow you to do.

14

That’s exactly how I’d interpret it if I were reviewing it. Follows same rules I’m using in my stuff. Non elevated users should not mutate machine state without elevation.

15

Where is the Marketplace thing in settings? I don’t see it anywhere

16

What are you referring to with ‘Marketplace’?

17

That’s not in beta.

18

Original thread here… If I’m understanding OP’s initial comment in that thread (big if! :sweat_smile:), it sounds like they maybe somehow stumbled on a reference to it in the UI… Is there any chance a wee bit of that beta code bled through somewhere/somehow?

19

I see it, slated for next month I guess as it only just got merged yesterday.

20

unlikely, no idea where they even saw marketplace outside frencks reddit post or github. It’s just not in HA outside the dev stream.