Devices not showing in dropdowns

Recently hit a problem with devices not showing up in dropdowns when creating automations. The devices exist in developer tools but I can not choose them to complete the automation. The main devices are Genius Hub smart plugs. Automations created before this started to happen are still working properly.

I have tried removing the genius hub entries in config and re discovering the devices but still no luck.

Any ideas as to what I can do to rectify this would be appreciated.

Try deleting your browsers cache or another browser

Thanks for reply. I have cleared cache and cookies on Firefox, Safari and Edge. Still not showing as available in dropdowns. Have also tried on iPad and iPhone apps. Really not sure what else is wrong :frowning:

Dropdowns will only populate with devices or entities that fit the context of what you’re trying to do. Post a screenshot of the dropdown in question and the device you want to select. Chances are your device isn’t supported for the dropdown you are trying to use.

Thanks Petro


I’m sad this issue doesn’t seem to have a resolution. I’m running into the exact same issue (or very similar) but I don’t think it’s because the action is not supported (because it was available before and it’s a basic function). It seems to correlate with a recent update (2023.7.2?) but rolling back didn’t help. Let me detail the issue:

I have MANY devices that seem to no longer show up in the menus for automation creation, but they still exist as devices (PLUG, DEVICE).

I noticed this when some automations broke (potentially after the update) the automation(s) still show actions but look odd (BROKEN)

What’s weird is I can confirm the device exists fine, it just cant be selected as a device when I create a new automation (NOLIST)

Even weirder, I can create an automation from the device info page (INFO, WORKAROUND) and create an automation and it loads in the device no problem! But again I cant do this from scratch or even add other devices as the action, etc, so it’s not very useful.

I still have a workaround - I can create an automation that uses the (ENTITY) rather than devices (I select states as triggers and call switch and light.turn_on/off, but not all of the entities are available - for instance I’m currently unable to recreate an automation where “if the power usage is above a certain level for 15min, turn the plug off”

ps after all my image notation, it will only let me upload one image, so I’ve uploaded it as a collage :frowning:

Why wouldn’t a numeric state trigger work?

It’s a bug in 2023.7 and it’s being fixed in 2023.8. Roll back to 2023.6.

So 7.2 and even 7.1 potentially had this as well?

That seems to fit, since I rolled back to those and it didn’t help, but I didn’t go all the way back to 6.x.

Also, does that mean everyone is having this issue on 7.x? Seems like this would be much more prevalent online if making automations is this difficult

Oh yes, that’s part of my work around. I can do a lot of this with “states” But for some reason some of the entities don’t show up or work the same way (Even though I can find most of the entities from the device, when I treat it as a state I can’t say “your power usage is above x for y minutes”)

Yes, everyone using 2023.7 has this issue. No it doesn’t affect everyone because a large group of people do not use device triggers, conditions, or actions. This only affects people who use those and are running 2023.7.x.

Numeric state triggers allow for that.

- platform: numeric_state
  entity_id: sensor.power
  above: x
  for:
    minutes: y

FYI device triggers just point at other methods. So if a device trigger can do something, other triggers can too.