[APP][PRO] YouLess, Enelogic, PVOutput - Belgian and Dutch P1 Smart Meter Reader

I noticed the renamed screensavers. :grin: Is there a description of the new behavior and colouring?

I guess Homey still needs to get used to the new name :joy:

It should behave exactly the same as before: more red means more usage. More blue means more production. The maximum red and blue can be set in the device settings.

version 4.0.1 just went live in the app store.

  • Fix optical water driver.
1 Like

Since the update to 4.0.0 my Enelogic P1 has lost the connection with Homey. I tried to add it again, but Homey says: session.on is not a function.

Unfortunately, reinstalling the app didnā€™t help either. What to do?

Hi @Ancent ,
That is unfortunate. I cannot test it myself. Send me an app diagnostics report. I hope that gives me a clue.

Hi @Gruijter

Thank you looking in to it. Here are the last lines of the app diagnostic report:

Blockquote
[err] 2021-12-02 20:06:49[Driver:LS120] Pair error Error: Info could not be retrieved from device at Youless.getInfo (/node_modules/youless/youless.js:198:11) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async /drivers/LS120/driver.js:51:18
[log] 2021-12-02 20:06:49[Driver:LS120] save button pressed in frontend
[err] 2021-12-02 20:06:47[Driver:LS120] Pair error Error: Info could not be retrieved from device at Youless.getInfo (/node_modules/youless/youless.js:198:11) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async /drivers/LS120/driver.js:51:18
[log] 2021-12-02 20:06:47[Driver:LS120] save button pressed in frontend
[err] 2021-12-02 20:06:36[Driver:LS120] Pair error Error: Info could not be retrieved from device at Youless.getInfo (/node_modules/youless/youless.js:198:11) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async /drivers/LS120/driver.js:51:18
[log] 2021-12-02 20:06:36[Driver:LS120] save button pressed in frontend
[err] 2021-12-02 20:06:29[Driver:LS120] Pair error Error: connect ECONNREFUSED 192.168.10.110:80 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) { errno: ā€˜ECONNREFUSEDā€™, code: ā€˜ECONNREFUSEDā€™, syscall: ā€˜connectā€™, address: ā€˜192.168.10.110ā€™, port: 80 }
[log] 2021-12-02 20:06:29[Driver:LS120] save button pressed in frontend
[err] 2021-12-02 20:06:18[Driver:LS120] Pair error Error: Info could not be retrieved from device at Youless.getInfo (/node_modules/youless/youless.js:198:11) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async /drivers/LS120/driver.js:51:18

You are trying to add the Enelogic as a Youless? You do have the old Enelogic P1 device right? Not the LS120?

Can you share the logs from when the device was sill paired? I need to see what error happened.

Iā€™m running into the exact same problem. Donā€™t think I have a report from when it was connected, since I reinstalled the app a few days ago.

@SjoerdAch @Ancent

Can you try a new test version I created for you both: Youless and Enelogic | Homey

It will only solve pairing the Enelogic. I need the error log after pairing from you to debug the rest :slight_smile:

@Gruijter

Thanks! With this version the Enelogic P1 is connected to Homey, but it says ā€˜cannot read property ā€˜offPeak of undefinedā€™

Blockquote
err] 2021-12-05 11:38:43[Driver:enelogicp1] [Device:d57388df-85d0-4b96-be5f-0a20e6abbbbd] Poll error Cannot read property ā€˜offPeakā€™ of undefined
[err] 2021-12-05 11:38:23[Driver:enelogicp1] [Device:d57388df-85d0-4b96-be5f-0a20e6abbbbd] Poll error Cannot read property ā€˜offPeakā€™ of undefined
[err] 2021-12-05 11:38:13[Driver:enelogicp1] [Device:d57388df-85d0-4b96-be5f-0a20e6abbbbd] Poll error Cannot read property ā€˜offPeakā€™ of undefined
[log] 2021-12-05 11:38:03[Driver:enelogicp1] [Device:d57388df-85d0-4b96-be5f-0a20e6abbbbd] start polling 192.168.10.110 @10 seconds interval
[log] 2021-12-05 11:37:33[Driver:enelogicp1] [Device:d57388df-85d0-4b96-be5f-0a20e6abbbbd] Meter renamed to: 192.168.10.110

Yes. With this error I am on to something I can work on. To be continuedā€¦

v4.0.3 Hopefully fixes Eneleogic. Hard for me to fully test since I donā€™t own that device myself.

@Gruijter

You solved it. The app works as before. Thanks again!

Super! I will release it as stable version then. Thx for reporting and testing @Ancent @SjoerdAch

Iā€™m not getting it. Hopefully someone can shed some light on it. Iā€™m trying to get a little bit more grip on my energy usage. Iā€™m using the LS120 for some time now but have always assumed it would just work like it is supposed to. I have never looked at any of the other apps besides the one in homey.

Now Iā€™m using this app together with the powerbythehour app to summarize the daily usage.

Powerbythehour reports i have been using 20kWh yesterday. When I check the site of Vattenval (my energy supplier) it reports 27kWh. So for the first time ever I looked in the app of the LS120 on my iPhone and that reports 27kWh too. What could it be powerbythehour reports only 20kWh. I do have solar panels, but there was practically no sun yesterday and my solarman reports it only have produced 0,7kWhā€¦ so that cannot make this difference.

As I understand LS120 only reports what it reads from the P1 meter. This is correct right? If this is correct I could create some calculations to check against powerbythehour right?

One thing that might throw things off: Power by the hour uses the Homey clock to see when the day/week/month/year changes. As of Homey firmware 5.0 Homey decided to change the clock from local time to UTC without informing app builders on how to properly get local time and/or test what the effect of the change would be.

The result is, that Power By the hour no longer resets the counters at 0:00 local time but UTC time, which differs 1 or 2 hours, depending on daylight savings. That may account for the difference, although if should be a shift a part of your usage from one day to another.

Most likely your power consumption around midnight was different from one day to the next.

I believe the developer of Power By the Hour recently became aware and was contemplating a way to fix this. But Athom isnā€™t making it easy. Ah but now I see: same developer :slight_smile:

No I already fixed that in an app update.

Just check your insights of the LS120 in Homey. Substract the kWh value at 0:00 from the value next midnight. I am eager to learn if PBTH is wrong or Vattenvalā€¦

Curious how? Must not have been very easy to get right with daylight savings?

There is a function for getting the timezone the Homey is using. In the end it is only 2 lines of code to correct for timezone offset.

1 Like