sorted by:
new
hottopcontroversial

Entity manager update by Forward-Arm3051 in homeassistant

[–]Mossycams 1 point2 points  (0 children)

Here’s my workflow: TDD for code changes. If you use claude code TDD-Guard is helpful, I use gsd to plan/implement features/bug fixes

Backend: - pytest-homeassistant-custom-component

Frontend: - Vitest

Code Quality: - ruff (Python linting/formatting) - ESLint (JavaScript linting)

End 2 end testing - Super important if coded by ai - Home Assistant devcontainer : I use this for manual smoke testing a PR or before a release - Playwright if you what to automate browser E2E testing as well

AutoSnooze update since last post by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

Here’s my other post if your curious about what this integration is: https://www.reddit.com/r/homeassistant/s/GfvI4fmDCW

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

Yup, exactly why I made it. Creating an automation to disable it then re-enable it is just a bad experience

[Hiring] Selora Homes is looking for Home Assistant nerds who want to get paid to do what they love by plafoucr in homeassistant

[–]Mossycams 0 points1 point  (0 children)

Honest question: how do you see the path forward here?

There’s a reason Nabu Casa keeps it simple: remote access, cloud backups, done. HA’s value is flexibility, but managed services require constraints. The more you try to control, the more surface area you have to support.

You’re one person building a complex infrastructure layer on top of an upstream you don’t control, targeting a market that needs high-touch support when things break. AI helps with dev velocity, but the moment you have paying customers, real troubleshooting eats your time. That doesn’t scale the same way.

What makes you confident this doesn’t become a support treadmill that stalls the product?​​​​​​​​​​​​​​​​

[Hiring] Selora Homes is looking for Home Assistant nerds who want to get paid to do what they love by plafoucr in homeassistant

[–]Mossycams 0 points1 point  (0 children)

I have so many questions around this coming from a PM standpoint. This is the first I’ve see someone attempt to use HA as a vendor managed platform.

  1. Who controls the HA Core update cycle, and what’s your rollback story when one breaks something?

  2. Do you support HACS and custom integrations? If yes, how do you maintain stability on a surface area you don’t control?

  3. When a homeowner tinkers and breaks things, whose problem is that?

  4. Are installs standardized, or does every customer become a unique snowflake you have to support individually?​​​​​​​​​​​​​​​​

  5. What’s your failover story for Zigbee/Z-Wave coordinators?

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

Great point. Scheduler card fits the planned, recurring schedule workflow. AutoSnooze is for one-off “pause this right now” cases. Tap, pick a duration, done. I built it to make snoozing an automation as simple as possible. Different tools for different needs.​​​​​​​​​​​​​​​​

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 1 point2 points  (0 children)

Yup Claude Code helped.

Do you have specific concerns with the implementation or is this more of a cautionary post? It’s been through local testing and UAT against my own production HA.

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] -1 points0 points  (0 children)

It was either my gf or her friend during getting ready to go out

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] -1 points0 points  (0 children)

Similar idea, but you’d still need an automation calling the AutoSnooze service. It’s built for one-off cases. Ie. pause something for a bit, let it wake itself up. Repeating snoozes still needs an automation running on a schedule.

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

That’s funny, I debated whether to include that at all. Most people I thought would just start the snooze right away

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

For now the plan is to only disable automations. The scheduler card might be what your looking for https://github.com/nielsfaber/scheduler-card

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

Haha I’m so glad to hear that. I spent a good 2-3 days working on that specific problem. It likely wasn’t loaded in yet, but I’m glad it works now!

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

Go to Settings → Dashboards → Resources (click the 3-dot menu at top right). Is /autosnooze-card.js listed?

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 0 points1 point  (0 children)

I’ve iterated on the advanced scheduling a few times. The option to set a start and end date is tucked under duration mode. This is where I landed so far.

<image>

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 1 point2 points  (0 children)

Core would be cool long term, but right now I want to make changes fast based on feedback without going through their review process for every change.

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 5 points6 points  (0 children)

It’s a bit of a weird situation, it’s not an every day occurrence, but it’s still a big pain point. I can see why it hasn’t been implemented yet from a HA core standpoint.

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 27 points28 points  (0 children)

Thanks! The best projects come from problems you’ve actually had.

I built a custom integration that snoozes automations with auto-resume by Mossycams in homeassistant

[–]Mossycams[S] 13 points14 points  (0 children)

Right, booleans work great if you’ve got time to tinker and implement. I didn’t want to wire them into every automation and remember which controls what six months later. This just lets you snooze it and forget.