# Detect 433-button on-signal eve if device is already on **URL:** \ **Category:** Questions & Help\ **Tags:** homey-pro\ **Created:** [December 17, 2023, 8:08am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119 "2023-12-17T08:08:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Jan-Erik\_Hallkvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_hallkvist/32/79000_2.png) [@Jan-Erik\_Hallkvist](https://community.homey.app/u/Jan-Erik_Hallkvist)\ **Post date:** [December 17, 2023, 8:08am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/1 "2023-12-17T08:08:33Z")
Hello! Migrating to Homey Pro 2023… All nice but got stuck at implementing a flow for forced bathroom ventilation. A Nexa 433 onoff wall button activate/deacrivate ok and is put off after 40 minutes by the flow. The problem is that I want a new on-push to restart downcount prolonging forced vent. Unlike my old hub system Homey seem to ignore incoming ON if device is already on. Don’t know if it is in Homey or in Nexa app. Anyone found a solution? Thanks! /Jan ---
**Author:** ![Henrik\_Johnsson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_johnsson/32/13707_2.png) [@Henrik\_Johnsson](https://community.homey.app/u/Henrik_Johnsson)\ **Post date:** [December 17, 2023, 5:44pm UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/2 "2023-12-17T17:44:40Z")
I think the problem may be in your flow rather than the app, at least if it is all implemented in one continuous flow with a delay card to turn the ventilation off. A solution would be to split in into two flows (and using the Chronograph app): First flow is triggered by the button, it activates ventilation and starts/restarts a 40 min Chronograph countdown timer. Second flow is triggered by the timeout of the timer you started in the first flow and here is where the ventilation is deactivated. ---
**Author:** ![Jan-Erik\_Hallkvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_hallkvist/32/79000_2.png) [@Jan-Erik\_Hallkvist](https://community.homey.app/u/Jan-Erik_Hallkvist)\ **Post date:** [December 18, 2023, 5:30am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/3 "2023-12-18T05:30:11Z")
Thanks for your answer, Henrik. In principle my solution is as you described. The problem is that the Activated/Deactivated card do not fire if incoming command=device status. To simplify test I made 2 standard flows 1. Activate card → Push notice 2. Deactivate card → Push notice The ”when”card only fires when device status is opposite from incoming command. Tested this on Nexa card and Telldus card. Same behaviour. The question is if there is a way to catch command ”raw”? ---
**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\ **Post date:** [December 18, 2023, 9:33am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/4 "2023-12-18T09:33:07Z")
Please share your test flows. ---
**Author:** ![Jan-Erik\_Hallkvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_hallkvist/32/79000_2.png) [@Jan-Erik\_Hallkvist](https://community.homey.app/u/Jan-Erik_Hallkvist)\ **Post date:** [December 18, 2023, 9:48am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/5 "2023-12-18T09:48:27Z")
Thanks Rmb! OFF [https://homey.app/f/sdbkYN/](https://homey.app/f/sdbkYN/) ON [https://homey.app/f/SevkYN/](https://homey.app/f/SevkYN/) Best regards Jan ---
**Author:** ![Henrik\_Johnsson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_johnsson/32/13707_2.png) [@Henrik\_Johnsson](https://community.homey.app/u/Henrik_Johnsson)\ **Post date:** [December 18, 2023, 11:51am UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/6 "2023-12-18T11:51:11Z")
OK, then you trig on the device state change and not the button input, which explains the problem. The Nexa app is a bit limited, it’s quite likely that your button is not supported, try the app for [Trust Smart Home](https://homey.app/sv-se/app/nl.klikaanklikuit/Trust-Smart-Home/), it covers a wider range of devices. ---
**Author:** ![Jan-Erik\_Hallkvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_hallkvist/32/79000_2.png) [@Jan-Erik\_Hallkvist](https://community.homey.app/u/Jan-Erik_Hallkvist)\ **Post date:** [December 18, 2023, 1:05pm UTC](https://community.homey.app/t/detect-433-button-on-signal-eve-if-device-is-already-on/98119/8 "2023-12-18T13:05:39Z")
Thanks Henrik. Found a TSH-button that acts the way I need. Firing in flow for every on or off push.