# \[Hoe dan?\] Zet de waarde van een virtuele sensor

**URL:** <https://community.homey.app/t/hoe-dan-zet-de-waarde-van-een-virtuele-sensor/46108>\
**Category:** Flows\
**Tags:** virtual-device\
**Created:** [April 11, 2021, 4:40pm UTC](https://community.homey.app/t/hoe-dan-zet-de-waarde-van-een-virtuele-sensor/46108 "2021-04-11T16:40:03Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [August 28, 2022, 4:15pm UTC](https://community.homey.app/t/hoe-dan-zet-de-waarde-van-een-virtuele-sensor/46108/20 "2022-08-28T16:15:50Z")

</div>

Dit is wel wat je ongeveer bedoelt, denk ik (klik op de link, of op de `v`)

> [@MQTT NodeRed values](https://community.homey.app/t/mqtt-nodered-values/60459/6):
>
> You’re welcome. Yea, I left it for you to figure out grimacing It is possible, but is it better… There’s a disadvantage: As you can see, there’s a delay needed. While the shortest delay possible is ONE whole second, using 2 flows makes it respond quicker. In the previous 2 flow example, the 2nd flow fires as soon as the numeric var has changed…

---

_[View the full topic](https://community.homey.app/t/hoe-dan-zet-de-waarde-van-een-virtuele-sensor/46108)._