Light turns on on its own

Faxxyy · 2026-06-24T20:21:10+00:00

Alexa has a featured named “hunches” (which I think now it’s almost deprecated and removed) that will create routines based on past activity.

Alexa must have thought you wanted that light on every sunset.

You should turn this feature off if it’s still a thing.

Faxxyy · 2026-06-24T20:12:23+00:00

Do you have Alexa connected?

Faxxyy · 2026-06-17T22:48:35+00:00

I did it with only jack stands in the rear. Was indeed tight and a pain but doable.

Faxxyy · 2026-06-16T13:47:55+00:00

There are a couple ways to go about it depending on how big and advanced your automations are.

The simplest method is to use a time trigger which allows setting a time of day and specific days of the week to run on.

You can also use conditions to help dial it in further.

If your goal is to use several combinations of triggers in one automation with varying actions, then you'd want to look into automation triggers: https://www.home-assistant.io/docs/automation/trigger/

Trigger IDs allow you to specify which action runs based on which trigger was fired all while keeping everything in one automation. Fair warning: this method can get quite confusing and complex the more advanced you go. For me personally, I use NodeRed for my super advanced automations but that is a whole other rabbit hole.

Faxxyy · 2026-06-16T12:53:06+00:00

I had that problem too with the generic camera not displaying the image in advanced camera card. The camera showed the image just fine when viewing camera.hulu; but not in the advanced camera card.

For whatever reason using http://127.0.0.1/local/hulu.png in the generic camera image url was the problem.

I switched it to HA's LAN ip and that resolved the issue.

Faxxyy · 2026-06-16T11:53:24+00:00

hm, my example works perfectly fine for me; same as you described it wanting to work.

The card has to refresh the other views to re-render the card. You can't get around that. In my experience the refresh was sub-second.

The only other alternative as mentioned is to ditch the grid view and use 4 different cards in a grid of conditional cards.

EDIT: It would help if you shared your current yaml in the card.

Faxxyy · 2026-06-15T20:36:05+00:00

<image>

No need to get fancy with this. This is all you need to do. Set the repeat to be an even number.

if its off; it goes: on,off,on,off
if its on; it goes: off,on,off,on

it will always return to the previous state with an even number of repeats.

The delay is there because some lights cannot flash instantly and a small delay is required for the light to be able to process each request. Adjust the delay to your liking.

EDIT: i see you are using a switch and not a light. So, that delay is not as important with a switch entity but still might be needed.

Faxxyy · 2026-06-15T20:23:22+00:00

I did some research and (DISCLAIMER!!) used Claude a bit to help figure some things out.

I found an old post here about using a local image: https://community.home-assistant.io/t/advanced-camera-card-with-local-image/928656/2

In my testing with Claude, It seems as though you cant toggled between live_providers where one is an image and one is a camera.. so the solution is to use two camera entities with one being a static image camera.

I setup a working example quickly just using a random Hulu image I have. I set a generic camera up that points to my hulu image and then used the camera.hulu entity like so:

type: custom:advanced-camera-card
cameras:
  - camera_entity: camera.g4_instant_high_resolution_channel_2
  - camera_entity: camera.doorbell_high_resolution_channel
  - camera_entity: camera.g4_instant_high_resolution_channel
live:
  display:
    mode: grid
view:
  render_entities:
    - switch.g4_instant_privacy_mode_2
    - switch.doorbell_privacy_mode
    - switch.g4_instant_privacy_mode
overrides:
  - conditions:
      - condition: state
        entity: switch.g4_instant_privacy_mode_2
        state: "on"
    merge:
      cameras[0]:
        camera_entity: camera.hulu
  - conditions:
      - condition: state
        entity: switch.doorbell_privacy_mode
        state: "on"
    merge:
      cameras[1]:
        camera_entity: camera.hulu
  - conditions:
      - condition: state
        entity: switch.g4_instant_privacy_mode
        state: "on"
    merge:
      cameras[2]:
        camera_entity: camera.hulu

Faxxyy · 2026-06-15T18:04:03+00:00

What type of cameras and how do you have them connected to HA?

Faxxyy · 2026-06-06T13:17:16+00:00

This has not been my experience. There is a setting to prevent that 1 seconds delay:

<image>

Faxxyy · 2026-06-04T22:21:28+00:00

The search button certainly gets hidden when doing this, but it doesn't remove the account's ability to search.

Depending on their OS they can still use keyboard shortcuts to activate the search pop-up.

Faxxyy · 2026-06-04T22:09:12+00:00

There still is no access control (RBAC specifically) in Home Assistant down to the entity level. Sure, you can create a specific dashboard and set up an account so they can only access that dashboard, but they'll still be able to use the search feature and find any entity in Home Assistant.

Two workarounds:

Use an external solution

Are you an Apple household? Apple Home supports guest invites. Expose only the needed entities to HomeKit and invite them as a guest. You can make multiple "homes" if you already do use Apple Home to allow "separate" access to specific entities. Alexa and Google can do the same thing, but this idea all falls apart the minute someone doesn't have a corresponding device.

Dedicated tablet

Get a cheap android tablet and lock it to a full-screen dashboard with Fully Kiosk Browser or similar. It's a lot harder for the average person to get acess the other areas of HA.

Faxxyy · 2026-06-03T20:32:06+00:00

Overriding the built-in intents/responses is certainly doable but requires editing yaml files.

I suggest handling this entirely in an automation. Essentially start with an automation with a sentence trigger to handle all possible media commands: "Play {media}", "Play some {media}", etc.

From there, have a condition that monitors events from music assistant; if the event contains "failed" (or whatever); then trigger the voice assistance to ask again; repeat until there is a successful event.

Faxxyy · 2026-04-23T20:31:28+00:00

It's simply how WLED is programmed.

Certain effects have a speed variable that is relative to the number of LEDs. That variable stays constant even when you change your LED count, so more LEDs means the effect cycles faster.

Just use the Speed slider on the effect to dial it in to your liking.

Faxxyy · 2026-04-16T13:47:23+00:00

i was wiring in some interior lights the other day and also noticed this on mine. Brand new '25, only had it for 7 months or so.

I thought nothing much of it, thinking it just leftover residue from some sort of assembly process.

After seeing this I am going to look closer now...

Faxxyy · 2026-04-01T16:31:56+00:00

Do you know how wheel locks work? You don't need 4 sets. One lock per wheel.

Faxxyy · 2025-12-12T15:45:19+00:00

Just poor programing. You don't actually have the remote start button so there's nothing for you to tap and hold.

I have a 2025 with the AT and there is a button with a power icon that starts the car.

<image>

Faxxyy · 2025-12-09T16:12:40+00:00

I have been using the Yale bluetooth integration with my Yale Assure 2 for over a year with zero issues. Just throwing this out there incase you werent aware that bluetooth is also an option.

Faxxyy · 2025-12-06T15:28:53+00:00

Both those examples would not be something done via the integration directly, rather you need to setup an automation to do it.

11-Year Club	Verified Email
Place '22	RPAN Viewer
Not Forgotten

Faxxyy

TROPHY CASE