[APP][Pro] Homewizard

Pushed 2.1.8 for review, hope it will be more stable for the experimental users that use the stable Homewizard app version 2.1.3.

Seems to run fine overhere, Jeroen.
v2.1.8
(I’ve only a P1 dongle in use)

Ok thx, found one new unhandled error for energy_socket which I will fix tomorrow.

Since the update to v2.1.8 the EnergyLink device is offline for about 20-30 seconds when opening the Homey app. Or opening the Homewizard app within the Homey app.


image

Please sent me a diagnostic report.

Here same problem. And the wind is not found anny more after update.

I adjusted the timeouts please try test version in store 2.1.9

Looks like v2.1.9 solver this issue.

Ok pushed to stable so others can profit.

Oops…
The issue showed up again, but less often.
Diagnostics id is 8e2ecce8-8259-46f6-bb65-0332c1ab9183

@Arnold_vd_Linden

You got a Homey <-> Homewizard connection issue

FetchError: Response timeout while trying to fetch http://192.168.1.5/<>/get-sensors (over 13000ms)
at Timeout._onTimeout (/node_modules/node-fetch/lib/index.js:387:12)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7) {
message: ‘Response timeout while trying to fetch http://192.168.1.5/<>/get-sensors (over 13000ms)’,
type: ‘body-timeout’
}
FetchError: request to http://192.168.1.5/<>/get-sensors failed, reason: socket hang up
at ClientRequest. (/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:311:20)
at Socket.socketOnEnd (_http_client.js:460:9)
at Socket.emit (events.js:323:22)
at endReadableNT (_stream_readable.js:1204:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
message: ‘request to http://192.168.1.5/<>/get-sensors failed, reason: socket hang up’,
type: ‘system’,
errno: ‘ECONNRESET’,
code: ‘ECONNRESET’
}

---- stderr ----
FetchError: Response timeout while trying to fetch http://192.168.1.5/<>/el/get/0/readings (over 13000ms)
at Timeout._onTimeout (/node_modules/node-fetch/lib/index.js:387:12)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7) {
message: ‘Response timeout while trying to fetch http://192.168.1.5/<>/el/get/0/readings (over 13000ms)’,
type: ‘body-timeout’
}

The issue was not there with the previous version.

I did a wifi network optimization now and reboot of the Homey.
Let’s see if this will help.

I had to drop timeout from 20 to 13 seconds. So your Homewizard is unable to handle a query from Homey/Homewizard app within 13 seconds. This is very slow and related to Wifi issue on the Homewizard. Move it, flip it and see if it improves the connectivity.

My Homewizard with Energylink, Heatlink and 2 temp sensors are working fine with the test version 2.1.8. The P1 meter has a red exclamation mark. With test version 2.1.9 the P1 is also not working.
It has worked fine with the previous versions.
Homey is on version 7.2.0.
Because maybe other apps not working on 7. 30 ore the RC 7.4.0.

Please sent diagnostic report so I can see what the app detects from your end.

My diagnostic report.
4de24335-aaac-4e14-937b-cb11abbeeeb7

Can’t see P1 dongle. But your Homewizard is slow as it cant get the energylink data.

FetchError: Response timeout while trying to fetch http:///<>/get-sensors (over 13000ms)
at Timeout._onTimeout (/node_modules/node-fetch/lib/index.js:387:12)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7) {
message: ‘Response timeout while trying to fetch http:///<>/get-sensors (over 13000ms)’,
type: ‘body-timeout’
}

My Energylink was working normal when I made the report.
But now after a couple of hours the P1 is back in Homey.
Strange, but it works now.
Thanks for looking.

It’s strange. Never had issues before but since this version an red exclamation mark for a couple of seconds on the EnergyLink. And suddenly this should be a wifi issue.

Replaced the devices and optimized my wifi signal and still the same issue.
Strange effect is that when opening the Homey app I see the EnergyLink tile updating the number. And within 2 seconds a exclamation mark appears for about 5 seconds.

I’m pretty sure it has to do with this update and is possible for me to go back tot the older version?

Manually install from my github.
Older versions have a tag so pick your flavor. Download the package and do a developer cli install.