# \[APP\]\[Pro\] Homewizard 🧙‍♂️

**URL:** <https://community.homey.app/t/app-pro-homewizard/19267>\
**Category:** Apps\
**Tags:** app, official, homey-pro\
**Created:** [October 14, 2019, 2:25pm UTC](https://community.homey.app/t/app-pro-homewizard/19267 "2019-10-14T14:25:58Z")\
**Posts on this page:** 20\
**Page:** 128

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 16, 2025, 2:02pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2568 "2025-09-16T14:02:34Z")

</div>

Homewizard Energy app is cloud based while Homey is all local….BIG difference people tend to forget.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 17, 2025, 3:10pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2569 "2025-09-17T15:10:53Z")

</div>

v3.6.66 went live

This version should improve mDNS problems, but do note that the first run might still fail as it has to store the url first on success.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 19, 2025, 1:31pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2570 "2025-09-19T13:31:37Z")

</div>

v3.6.67 (test/beta)

- Enforcing interval clears on various devices when interval is reset
- try\_authorize handler bugfix (interval / timeout) app crash logs

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 8:35am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2571 "2025-09-20T08:35:38Z")

</div>

After every update I have the same issues. Only solution for me is to reboot the whole wifi mesh network. This Homewizard app is the only app causing this issue. Other mDNS apps are working perfect and it had nothing to do with the local network or setup.

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 8:36am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2572 "2025-09-20T08:36:57Z")

</div>

Let’s hope this will work.

I will find out with the next update.

Thank you 🙏

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 9:17am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2573 "2025-09-20T09:17:17Z")

</div>

Why dont you answer my earlier question? I’ve implemented something with an assumption now. I have 2x P1’s, 1x kwh, 6 sockets, PIB, watermeter and no problems with mDNS.

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 9:40am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2574 "2025-09-20T09:40:37Z")

</div>

I didn’t see a question addressed to me

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 9:49am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2575 "2025-09-20T09:49:15Z")

</div>

I replied to your repsonse 22 days ago.

> [@\[APP\]\[Pro\] Homewizard man\_mage](https://community.homey.app/t/app-pro-homewizard/19267/2550):
>
> Strange, sounds like your Homey is unable to process all mdns updates from the network. If the records are there then you Homey should pick them up. Have you raised this with Athom support? Is this with the Homey Pro 2023 or the older one? And what error message do you see in the device cards met the ! sign?

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 10:13am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2576 "2025-09-20T10:13:04Z")

</div>

I have missed that one.

Till now I didn’t raise a ticket at Homey because this is the only app with this issue.

Devices are discovered with mDNS as they are unavailable in de Homewizard app.

The Homewizard app shows them as: Device unavailable.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 10:18am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2577 "2025-09-20T10:18:26Z")

</div>

There are more causes than just mDNS. Are you on a Homey 2016|2019? Or the new 2023?

Do use an internal dns? Are using .local domain in your DHCP scope?

Seems only a rare few are affected of the nearly 17000+ users.

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 10:29am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2578 "2025-09-20T10:29:41Z")

</div>

I use the Homey Pro 2023.

The network DNS is internally without .local. DNS is using Pihole. mDNS is enabled.

All devices have a DHCP reservation, so a static IP.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 10:41am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2579 "2025-09-20T10:41:39Z")

</div>

I rely what your Homey is able to discover on your network. I added even an extra 1s delay to process the result. There is nothing in my code that has influence on mDNS at all.

```auto
'use strict';

const Homey = require('homey');
const fetch = require('node-fetch');

module.exports = class HomeWizardEnergyWatermeterDriver extends Homey.Driver {

  async onPairListDevices() {

    const discoveryStrategy = this.getDiscoveryStrategy();
    await new Promise((resolve) => setTimeout(resolve, 1000));

    const discoveryResults = discoveryStrategy.getDiscoveryResults();
    const numberOfDiscoveryResults = Object.keys(discoveryResults).length;
    await new Promise((resolve) => setTimeout(resolve, 1000));

    const devices = [];
    await Promise.all(Object.values(discoveryResults).map(async (discoveryResult) => {
      try {
        const url = `http://${discoveryResult.address}:${discoveryResult.port}/api`;
        const res = await fetch(url);
        if (!res.ok)
        { throw new Error(res.statusText); }

        const data = await res.json();

        let name = data.product_name;
        if (numberOfDiscoveryResults > 1) {
          name = `${data.product_name} (${data.serial})`;
        }

        devices.push({
          name,
          data: {
            id: discoveryResult.id,
          },
        });
      } catch (err) {
        this.error(discoveryResult.id, err);
      }
    }));
    return devices;

  }

};

```

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 10:51am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2580 "2025-09-20T10:51:37Z")

</div>

Okay. This is in the last update?

Then I will wait for another update to check. If the problem exists then I will do more testing in my network or raise a ticket at Homey.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 11:27am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2581 "2025-09-20T11:27:13Z")

</div>

No that delay is there for a year or more.

I added a url fallback store. Once successfully connect (without a red ! Icon) it will store that url. When next time this mDNS discovery or update fails, it retrieve the last known working connection instead. If this fails as well then it is out of my scope and you have to ask Athom support. Poor wifi or failing multicast is not my responsibility.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 20, 2025, 11:49am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2582 "2025-09-20T11:49:59Z")

</div>

@Arnold_vd_Linden maybe this is worth looking at? Add avahi/mdns support to your pihole?

> **[Use avahi/mDNS to advertise your Pi-hole's services to network clients](https://discourse.pi-hole.net/t/use-avahi-mdns-to-advertise-your-pi-holes-services-to-network-clients/78593)**
>
> mDNS (multicast DNS) is distinct from DNS. It allows devices across a network to get information about available services without requiring any configuration input from the user. It was originally designed by Apple as the core of their Bonjour...

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 20, 2025, 1:26pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2583 "2025-09-20T13:26:21Z")

</div>

Thank you for the effort so far!

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 21, 2025, 8:09am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2584 "2025-09-21T08:09:27Z")

</div>

v3.6.67 is live now

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [September 21, 2025, 2:54pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2585 "2025-09-21T14:54:41Z")

</div>

I just dit the update to version 3.6.67.  
When the app came back the P1 Meter en Water meter were directly available, and the kWh meter took about 5 seconds. Most of the times this one was giving the issue.

I did install the avahi services on the PiHole before as described in the article.  
So it looks like this issue is solved now.

thx again.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 21, 2025, 4:23pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2586 "2025-09-21T16:23:16Z")

</div>

So sounds like it is/was mDNS problem after all at your network and not my app.

---

<div class="post-metadata">

**Author:** ![basvanderploeg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/basvanderploeg/32/83556_2.png) [@basvanderploeg](https://community.homey.app/u/basvanderploeg)\
**Post date:** [September 25, 2025, 7:51pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2588 "2025-09-25T19:51:30Z")

</div>

@Jeroen_Tebbens I noticed that my 1 phase kWh meter isn’t working when I use the beta version of the app:

> Cannot read properties of undefined (reading 'catch’)

When I revert back to the current live version, it immediately works again.

[Previous page](https://community.homey.app/t/app-pro-homewizard/19267.md?page=127)

[Next page](https://community.homey.app/t/app-pro-homewizard/19267.md?page=129)