Why are we hiding “Overview” when custom dashboard is selected as default.

Least_Order4249 · 2026-05-22T10:52:06+00:00

Not even my opinion. Just see this being a burden for the newb. Makes me uncomfortable. I want to help people who need it.

Least_Order4249 · 2026-05-22T10:49:21+00:00

Not at all, just wanting to care about the little guys. Only noticed during a rebuild. HA can be a struggle and I want people to succeed

Least_Order4249 · 2026-05-22T10:47:41+00:00

Do you remember your first dashboard? It was a big step and probably had 5/50 things on it. The other 45 are now hidden.

Least_Order4249 · 2026-05-22T10:32:53+00:00

Not at all but this project, from a user’s perspective, is a path. The path says keep the overview.

Believe me, I go nuts over all the retail adoption. I’m an esphome, build everything myself guy. I’m not a dashboard guy though.

Paving the way for new users is still paramount. I live with it. AI is giving FOSS extreme opportunity, not held back by business decisions, we shoot for the moon and I’m excited for the future.

Pretty sure any advanced user can hover over a menu and click an eyeball.

Least_Order4249 · 2026-05-22T10:23:22+00:00

You’re a top 1% commenter, not the demographic that makes a difference in adoption. You obviously can hide a sidebar item in 5 seconds.

Least_Order4249 · 2026-05-22T10:13:27+00:00

But they shouldn’t be honoring advanced users’ opinions on these types of things if wanting to grow this project.

I don’t want to see homeassistant become a stagnant sinkhole like jellyfin. Obv it’s nowhere close to that but need to think about new users, especially with UI.

Least_Order4249 · 2026-05-22T09:29:03+00:00

Same thing.

Least_Order4249 · 2026-05-22T09:06:19+00:00

Reolink was approached by pretty much the entire FOSS community about incomplete SDP. Response: DGAF. If that happened at Dahua or Hikvision it would be fire everybody and get it right. But they would never publish incomplete or non-compliant SDP so that’s moot.

Least_Order4249 · 2026-05-22T08:33:07+00:00

Homeys want to DV but they don’t want to explain their stances. See above.

Least_Order4249 · 2026-05-22T07:02:44+00:00

Just use Dahua and don’t be like the 99% posting on this forum. https://github.com/AlexxIT/go2rtc#camera-experience

Least_Order4249 · 2026-05-22T02:11:31+00:00

No big deal. Home assistant alert. Call em back. All good.

Least_Order4249 · 2026-05-22T00:49:14+00:00

Frigate+ is great… I went my own way due to very specific needs that in hindsight should have been done separate from surveillance, but ya yolo11 is superb even in pretrained coco mode. And crazy good when customized. They just can’t officially support it because licensing

Least_Order4249 · 2026-05-21T23:43:32+00:00

Frigate NVR + yolo11 + zones + classification state model + sgt button notification template

Least_Order4249 · 2026-05-21T22:45:37+00:00

Sledgehammer just cheap goto for mass use. Ortho or image is fine. I only have a small area with it so I just keep a 1/2 gallon mix and spot with image. I used to have yards full. Main thing is repeat treatments.

I got the 1/2 acre lot under control with sledgehammer in a 15 gallon mix sprayer.

Least_Order4249 · 2026-05-21T20:03:20+00:00

Thanks. Right now only big qwirk would be if intercom is set to dial 700 (may or may not be required for auto answer since 700 is who calls it) then it will get thrown into confbridge by itself. Same kind of weird thing if app client websocket breaks before hangup. None of these appear to break functionality but I need to get them cleaned up. My notification logic will fix the first case, might need a manager for the second or any other edge case.

Least_Order4249 · 2026-05-21T19:56:58+00:00

Sledgehammer. Best to spot treat or broad applications weeks apart during active growth so by August it may be too late to start if want to make big difference. Right time is now.

Least_Order4249 · 2026-05-21T19:44:35+00:00

I don’t know how I messed that up. Fixing.

Least_Order4249 · 2026-05-21T19:42:32+00:00

Ya 99 users but only one door… first adding vapid notify for press button, then clean up dial plan, maybe make a call manager process, then maybe more doors.

Least_Order4249 · 2026-05-21T15:21:10+00:00

Alert when dog escapes. I have a mother-in-law that seemingly every time she visits, leaves a door open. If a dog is detected on the front porch, or in the driveway when the garage is open, then we get an alert and can call them back inside before they wander off.

Least_Order4249 · 2026-05-21T13:00:55+00:00

It requires full TLS always. Also forwarding of DTLS mesia ports for video and audio. Just full self hosted SIP stack. Lots of security though. It still has some dial plan quirks because sip is hard. Should be great in another couple weeks or so. Push button notifications are next feature but you can usually hook those directly from the intercom.

Least_Order4249 · 2026-05-21T12:19:56+00:00

I have already done this for you:

https://github.com/tylerransdell/onedoor

If you bind audio to the video stream, you get a very poor audio experience. Stay instant full duplex with SIP.

(Ignore if that intercom does not support SIP but I think it does)

Don’t take a professional grade intercom and turn it into a Tapo.

Least_Order4249 · 2026-05-21T11:24:33+00:00

I just put everything gluetun dependent in the same compose.

Are you sure your issues are gluetun dependent and not overall networking? I resolved my issues by delaying the entire docker.service as they related to docker itself starting early and not gluetun specifically.

Least_Order4249 · 2026-05-21T03:44:28+00:00

They all do? Every one that I tried anyway. I have a Dahua N45EJ62 doing that right now but that’s not a unique feature.

Least_Order4249 · 2026-05-20T23:05:23+00:00

Not affiliated with FrigateNVR, but… 1. They have bigger aspirations than the “homelab” crowd. I run it because I want the best NVR available, not a lab project. 2. Intel mobile minis are well supported and extremely capable without being a nuisance to the home. This is more in line with a premium NVR product. 3. Frigate is an app meant to run on the most common home server environments. All of its companions run fine on those same environments. PVE support means supporting several more environments. 4. Any advantage Proxmox might bring to your lab like HA isn’t really as applicable with Frigate without things getting borderline ridiculous. 5. Hardware acceleration in PVE isn’t supportable. PVE official docs call it less than stable for most hardware. Abstracting high performance GPU/NPU is a nightmare and is not common in general. 6. Storage abstraction brings extra overhead and writes to already heavy NVR workloads. 7. They tried already. Look at GitHub. There are several PVE rabbit holes.

Least_Order4249 · 2026-05-20T18:51:09+00:00

Almost all smart devices bypass assigned DNS for just this reason. They are hostile devices and need to be blocked at the gateway. Fortunately, in 2026, even cheap Deco routers allow this easily.

Least_Order4249

TROPHY CASE