# status.Cannot destructure property \`wakeUpInterval\` of 'undefined' or 'null'

**URL:** https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688
**Category:** Developers
**Tags:** z-wave
**Created:** [July 17, 2019, 8:19am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688 "2019-07-17T08:19:11Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Tiggerito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiggerito/32/613_2.png) [@Tiggerito](https://community.homey.app/u/Tiggerito)
#### Post date: [July 17, 2019, 8:19am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/1 "2019-07-17T08:19:11Z")

</div>

My Vision Sensor (ZD2201) stopped working at some point. Today I have been trying to get it back. I removed it, but when I try to pair it again as a basic Z-wave device I get this cryptic error:

`status.Cannot destructure property`wakeUpInterval`of 'undefined' or 'null'.`

I also tried adding it using the Vision Security plugin. The garage door device responded, but caused the same error message.

p.s. while I’m here. How can I find out a devices details like its productId if I can’t pair it?

Cheers

---

<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: [July 17, 2019, 8:38am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/2 "2019-07-17T08:38:29Z")

</div>

Sounds like a possible Homey core issue (did you upgrade your Homey’s firmware recently?). I can’t find the term `wakeUpInterval` in the Vision Security app anywhere, so it’s not related to the app specifically.

I think you should send a bug report through the request form: [https://support.athom.com/hc/en-us/requests/new](https://support.athom.com/hc/en-us/requests/new)

---

<div class="post-metadata">

### Author: ![Tiggerito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiggerito/32/613_2.png) [@Tiggerito](https://community.homey.app/u/Tiggerito)
#### Post date: [July 17, 2019, 8:52am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/3 "2019-07-17T08:52:18Z")

</div>

done. Thanks

---

<div class="post-metadata">

### Author: ![Michael\_Medin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_medin/32/2311_2.png) [@Michael\_Medin](https://community.homey.app/u/Michael_Medin)
#### Post date: [August 3, 2019, 10:09am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/4 "2019-08-03T10:09:40Z")

</div>

Did you find anything?  
I tried adding a basic dimmer and get the same error…

---

<div class="post-metadata">

### Author: ![Tiggerito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiggerito/32/613_2.png) [@Tiggerito](https://community.homey.app/u/Tiggerito)
#### Post date: [August 3, 2019, 11:27am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/5 "2019-08-03T11:27:55Z")

</div>

No progress. Support helped me properly reset the device, but it no longer works with the default z-wave driver. So I will need to write one at some point.

---

<div class="post-metadata">

### Author: ![Michael\_Medin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_medin/32/2311_2.png) [@Michael\_Medin](https://community.homey.app/u/Michael_Medin)
#### Post date: [August 3, 2019, 2:44pm UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/6 "2019-08-03T14:44:02Z")

</div>

Well, question is if you can, the pairing is done by the homey z wave driver so you cant really tinker with that. So in effect the bug in Homey makes the device impossible to use right?

All the driver can do is parse events and such, right?

---

<div class="post-metadata">

### Author: ![Tiggerito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiggerito/32/613_2.png) [@Tiggerito](https://community.homey.app/u/Tiggerito)
#### Post date: [August 3, 2019, 10:40pm UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/7 "2019-08-03T22:40:23Z")

</div>

I think in the past the default driver behaved as a switch, which happened to work for this device. After the update it stopped working. I’ve not had a chance to look into it yet.

---

<div class="post-metadata">

### Author: ![Michael\_Medin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_medin/32/2311_2.png) [@Michael\_Medin](https://community.homey.app/u/Michael_Medin)
#### Post date: [August 4, 2019, 4:59am UTC](https://community.homey.app/t/status-cannot-destructure-property-wakeupinterval-of-undefined-or-null/15688/8 "2019-08-04T04:59:04Z")

</div>

I created a driver for my device and the error went away, not sure why to be honest, but as long as I can pair it I am happy 🙂
