Switchbot Bluetooth automations not running despite updating

[tiny onyx]

So I have my switchbot air quality monitor connected over bluetooth, it's updating correctly, but the automations I made using the visual editor fail to fire despite my dashboard showing the co2 sensor updating.

My automation works if I manually trigger it

Every other automation I've created runs fine, but those are all Zigbee devices.

id: '1750130051783'
alias: New automation
description: ''
triggers:
  - type: carbon_dioxide
    device_id: 5f470ac3d919ac66567b0de0c7a9154c
    entity_id: e46df45504200537bf56699368cc15a3
    domain: sensor
    trigger: device
    above: 1000
conditions: []
actions:
  - action: light.turn_on
    metadata: {}
    data:
      flash: long
    target:
      device_id: 6288ca48057961e037164ac3d3b16b20
mode: single```

Ok, checking github issues shows the switchbot integration has some issues

switchbot kinda sucks it seems

[calm cosmos]

Is, by any change, the sensor value already above 1000? And just changing values, all above 1000?

This automation will only trigger when the value goes from below 1000 to above 1000. It will not trigger when the value changes but stays above 1000.

[tiny onyx]

Is there a way to trigger it if it's above?

It's fallen below and climbed and I haven't seen it trigger, I'll retest it today.

redid the automation, it's working now. ty.

Gotta figure out why my homekit bridge is timing out now

[calm cosmos]

No, not directly as that's not an event but a state. But the question then would be, why didn't it trigger when it did go above. Because then then would be no reason to try to trigger "when it's above"

[tiny onyx]

There's no way to check the state when it updates?

Also ty for the help

[calm cosmos]

When it changes, yes. That IS an event. But if you're looking at doing something when it goes above 1000 is something different then doings something every time it changes. Sometimes you do need it, but if you turn the light on when it does go above 1000 there is no need to do it again on every change

[tiny onyx]

I just want to check for any change and check if that's above 1200 and send a notification

[calm cosmos]

then you had the right thing. A device-trigger or numeric_state trigger with above: 1200. That will trigger when it goes above. As you don't want a notification every time is changes an it's above 1200, that would just spam you. But if you make the automation and that value is already above 1200 it will first need to go below 1200 and then above 1200 gain to get the notification. But once set, it should just work as you like 🙂

[tiny onyx]

fair enough. I was going to use it to alert + start fans to circulate air

I'll have it turn them on when it spikes, off when it drops

Ty for the help 🙂

[calm cosmos]

for that a numeric_state trigger (or device trigger) with above: and/or below is the way to go 🙂

only change your mindset that is should do something the moment you hit save 😄

[tiny onyx]

oh no I am pressing the update button on the sensor and blowing into it to see if it's registering!