# Device CapabilitiesObj in HomeyScript stays the same value when triggered in a flow

**URL:** <https://community.homey.app/t/device-capabilitiesobj-in-homeyscript-stays-the-same-value-when-triggered-in-a-flow/14529>\
**Category:** Developers\
**Created:** [June 17, 2019, 5:48pm UTC](https://community.homey.app/t/device-capabilitiesobj-in-homeyscript-stays-the-same-value-when-triggered-in-a-flow/14529 "2019-06-17T17:48:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 17, 2019, 7:12pm UTC](https://community.homey.app/t/device-capabilitiesobj-in-homeyscript-stays-the-same-value-when-triggered-in-a-flow/14529/3 "2019-06-17T19:12:22Z")

</div>

Looks like you need a workaround:

```auto
const device = await Homey.devices.getDevice({ id: '45f27858-c506-4d3c-a800-1954d803e3e3' });
const cap = device.makeCapabilityInstance('measure_power');

console.log(cap.value);

```

I think it has to do with lazy evaluation, where capability values are only updated when explicitly required.

---

_[View the full topic](https://community.homey.app/t/device-capabilitiesobj-in-homeyscript-stays-the-same-value-when-triggered-in-a-flow/14529)._