# Changing state of device in Homey without triggering it?

**URL:** <https://community.homey.app/t/changing-state-of-device-in-homey-without-triggering-it/87988>\
**Category:** Questions & Help\
**Created:** [August 25, 2023, 7:06pm UTC](https://community.homey.app/t/changing-state-of-device-in-homey-without-triggering-it/87988 "2023-08-25T19:06:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![torarnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torarnv/32/83065_2.png) [@torarnv](https://community.homey.app/u/torarnv)\
**Post date:** [August 25, 2023, 9:49pm UTC](https://community.homey.app/t/changing-state-of-device-in-homey-without-triggering-it/87988/3 "2023-08-25T21:49:53Z")

</div>

Yepp, Nexa 433Mhz. I’ve been hesitant to cut the direct coupling between the devices, as if Homey is down I can no longer control my lights. Also, Homey seems to have very buggy or poor 433 reception ([Poor 433 Mhz reception](https://community.homey.app/t/poor-433-mhz-reception/87562)) so removing the direct connection would make the switches more flakey, and even non-responding at times ☹

Is there really no way to update the logical state of the Homey side of things without also triggering the capability?

---

_[View the full topic](https://community.homey.app/t/changing-state-of-device-in-homey-without-triggering-it/87988)._