# Flow - flowcard\_not\_registered error - any ideas?

**URL:** <https://community.homey.app/t/flow-flowcard-not-registered-error-any-ideas/67228>\
**Category:** Flows\
**Created:** [August 11, 2022, 6:32pm UTC](https://community.homey.app/t/flow-flowcard-not-registered-error-any-ideas/67228 "2022-08-11T18:32:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Busta999](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/busta999/32/10053_2.png) [@Busta999](https://community.homey.app/u/Busta999)\
**Post date:** [August 11, 2022, 6:32pm UTC](https://community.homey.app/t/flow-flowcard-not-registered-error-any-ideas/67228/1 "2022-08-11T18:32:22Z")

</div>

Just started using Homey Flow and Advanced Flows.

Trying to get Homey to reset zwave energy meters to zero at midnight and I keep getting flowcard\_not\_registered error.

Any ideas what that means and how to fix this error?

Thanks

---

<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 11, 2022, 7:09pm UTC](https://community.homey.app/t/flow-flowcard-not-registered-error-any-ideas/67228/2 "2022-08-11T19:09:28Z")

</div>

It is a bit of guessing if you don’t share the flow right away. Thanks 🙃  
Maybe it is a syntax error, or something in the zwave app’s code.

---

<div class="post-metadata">

**Author:** ![Busta999](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/busta999/32/10053_2.png) [@Busta999](https://community.homey.app/u/Busta999)\
**Post date:** [August 11, 2022, 8:26pm UTC](https://community.homey.app/t/flow-flowcard-not-registered-error-any-ideas/67228/3 "2022-08-11T20:26:34Z")

</div>

Aha, I suspect it is in the App code.

I’ll just send a zwave string to do an energy reset.

I thought the error was something more fundamental, you have tweak the bidet before you use a flow type of thing.

No problem workaround exists.
