Just installed 2026.11.0 I have no Marketplace

Running system:

  1. Installation method Home Assistant OS
  2. Core 2026.11.0
  3. Supervisor 2026.10.5
  4. Operating System 18.4
  5. Frontend 20260930.5

Just updated my HA from I believe Core 2026.10.3 to 2026.11.0. I was watching the Release party and they show Marketplace between apps and Dashboards.

Not my case, there is no Marketplace.

I did look in Apps and was surprised to see Get HACS there in a “Stopped” state. I thought I heard them says it was going to uninstall HACS?

I’m super new to Home Assistant, migrated from HomeSeer after 15+ years and I just don’t have the skillset (yet) to even begin to figure out what has gone wrong.

My only HACS app was working until I restarted, Hi-Link LD2410 now has a Red ! Failed setup, will retry in the Integrations tab.

Before I revert back to my VM backup, is there anything I can look at to help the community figure out what went wrong?

Have you tried clearing the browser cache?

I did find this in the logs

I’m attaching the log file, it’s not letting me. Only 16 lines just going to paste it here.

/package/admin/s6-overlay/libexec/preinit: info: container permissions: uid=0 (root), euid=0, gid=0 (root), egid=0
/package/admin/s6-overlay/libexec/preinit: info: /run permissions: uid=0 (root), gid=0 (root), perms=oxorgxgruxuwur
s6-rc-compile: warning: source /etc/s6-overlay/s6-rc.d is empty
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-cont-init successfully started
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-11-06 11:44:50.162-05:00 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ld2410 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-11-06 12:40:50.437-05:00 WARNING (MainThread) [custom_components.ld2410.api.devices.device] None (C5:B0:28:F3:04:4A): Error disconnecting: [Errno 104] Connection reset by peer; RSSI: -54
2026-11-06 13:05:17.891-05:00 WARNING (MainThread) [custom_components.ld2410.api.devices.device] None (C8:F5:E0:9D:1F:1D): Error disconnecting: [Errno 104] Connection reset by peer; RSSI: -61
2026-11-06 13:55:41.895-05:00 WARNING (MainThread) [custom_components.ld2410.api.devices.device] None (C8:F5:E0:9D:1F:1D): Error disconnecting: [Errno 104] Connection reset by peer; RSSI: -85

And note that 11:44 AM is when I restarted after upgrade. Never saw anything like this prior to update.

For this part, that is there purely for the original HACS install. You can remove it.

For the missing Marketplace, try clearing your browser/app cache as others suggested.

What about my integration. You think there is any hope of getting that working?

Clear your browser cache and reload the page

Just reverted back and integration is working again. I was wrong, upgraded from 2026.10.4 to 2026.11.0. I think I’ll sit this one out until the next release. Thanks

Did you try anything suggested here?

I didn’t, I had reverted back before I saw the browser cache suggestion. I did take a backup of the problem child I swing back to it and give it a try. The whole family was screaming at me, nothing was working :wink:

Nothing was working is more likely to be a problem caused by this:

Can’t you just stop to post this link in all topics even if they are 100% unrelated?
the OP never followed advice to clear browser cache and reload the page, hence he never saw marketplace in the settings… unrelated to changes in entity names
And HA failed to connect to a LD2410 ( presence sensor?, custom integration, bluetooth?), not related to any changes in entity names. Without marketplace of course there is no easy way to check for updates

I understand that, however in the OP’s last post they said they had WAF problems because things were failing after the update. The most likely cause (in this release) is the naming change, and in that post there are tools to help with that.

I am certain the marketplace problem solution was given, however marketplace or caching problems are not the likely cause of that last plea for help.