# \[APP\]\[Pro\] Insight Trends Reloaded

**URL:** <https://community.homey.app/t/app-pro-insight-trends-reloaded/71307>\
**Category:** Apps\
**Tags:** app, tools, insights, homey-pro\
**Created:** [October 28, 2022, 8:39am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307 "2022-10-28T08:39:36Z")\
**Posts on this page:** 19\
**Page:** 19

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [October 13, 2025, 8:26pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/364 "2025-10-13T20:26:29Z")

</div>

> [@m.plo.b](#):
>
> per hour

Is currently per hour, but only for the trend value. And it’s now global on all trend value, since i adjusted the base function.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [October 13, 2025, 9:14pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/365 "2025-10-13T21:14:48Z")

</div>

> [@spkesDE](#):
>
> ### Breaking Change: Trend Calculation Changes
> 
> I’ve reworked the trend calculation to make it more consistent and easier to understand.  
> Before, one of the flow cards multiplied the trend result by **1000** , while others didn’t, which made things confusing. That factor is now **removed**. The trend number will now feel much more natural (no huge or tiny numbers that depend on arbitrary scaling).

Hi Sir ! Long time… thanks for keeping your apps alive 😉 ….so it means all conditions needs to be reworked now in all relevant flows, do I understand that correctly ? It would be still better to implement it in non-breaking manner, eg. keeping trend and trend and implement TrendHumanized. I haven’t installed the testing version yet.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [October 13, 2025, 10:12pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/366 "2025-10-13T22:12:42Z")

</div>

Only if you use the trend, so often yes 🙂  
I’ll add a setting to the app setting, so you can choose.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [October 13, 2025, 10:45pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/367 "2025-10-13T22:45:38Z")

</div>

# [Test Version 1.6.0🚀](https://homey.app/a/com.spkes.insightTrendsReloaded/test/)

### 🎉 **What’s New**

> - Added option to humanize the trend value in the app settings (Default Off).
> - Added Trend Direction Tag to flow cards.
> - Bug fixes

Your feedback is incredibly valuable for making this app as reliable and feature-rich as possible!

### 💡 **Support My Development:**

If you appreciate my work and want to help out, consider buying me an energy drink ⚡ or a beer 🍺. Donations are a great way to support and motivate me!  
You can donate via [PayPal](https://www.paypal.com/paypalme/spikes022).

### 👩‍💻 **Calling All Developers!**

Are you a developer? Want to contribute to this project? I’d love to collaborate! Feel free to send a pull request on GitHub and join me in making this app even better.

## 🙏 **Thank you for your support!**

---

<div class="post-metadata">

**Author:** ![Tom\_Van\_de\_Putte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tom_van_de_putte/32/122561_2.png) [@Tom\_Van\_de\_Putte](https://community.homey.app/u/Tom_Van_de_Putte)\
**Post date:** [December 16, 2025, 4:19pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/368 "2025-12-16T16:19:11Z")

</div>

I have the following error:

Calculated trend for “\>Eenergieverbruik”. Cannot read properties of undefined (ready ‘y))  
Below you find the diagnostics id:

75e5fcda-4924-4b59-89fa-f0212caf7e3b

What is going wrong? It was working until yesterday and this afternoon I noticed this error the first time.  
I uninstalled the app already. I restarted Homey already and did a combination of the two. (uninstall/restart)  
I checked my app insights but seems to have it for every device and don’t see strange app insights.

something additional: My homey updated this night to version 12.10.0 ? Any correlation?

---

<div class="post-metadata">

**Author:** ![Henny\_Karreman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henny_karreman/32/9581_2.png) [@Henny\_Karreman](https://community.homey.app/u/Henny_Karreman)\
**Post date:** [December 17, 2025, 9:39am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/369 "2025-12-17T09:39:20Z")

</div>

I want to calculate the average of the energy consumption per minute. I use Insight trends reloaded for this. If I set that I want to calculate the average over 1 minute every minute, it doesn’t work. Only when I increase the time to 3 minutes is an average value calculated.

 ![IMG_0647](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9b4726f12b909e433c4f4841b4e9f82e2296f57f.jpeg)

 ![IMG_0646](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/7/97ac0b78cd295d45074b5dcfc9d65897308c2040.jpeg)

Am I doing something wrong?

---

<div class="post-metadata">

**Author:** ![Maarten\_Rensen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maarten_rensen/32/122616_2.png) [@Maarten\_Rensen](https://community.homey.app/u/Maarten_Rensen)\
**Post date:** [December 17, 2025, 7:58pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/370 "2025-12-17T19:58:33Z")

</div>

Same here, since couple of days an error in those trend cards if using less than 3 minutes. Was working before.

---

<div class="post-metadata">

**Author:** ![Smit](https://avatars.discourse-cdn.com/v4/letter/s/a183cd/32.png) [@Smit](https://community.homey.app/u/Smit)\
**Post date:** [December 18, 2025, 10:54pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/371 "2025-12-18T22:54:51Z")

</div>

Same here.

---

<div class="post-metadata">

**Author:** ![4x4\_Pete](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/4x4_pete/32/113286_2.png) [@4x4\_Pete](https://community.homey.app/u/4x4_Pete)\
**Post date:** [December 19, 2025, 9:07am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/372 "2025-12-19T09:07:54Z")

</div>

Same here. - And I have the strong suspicion that Athom´s new (and for many reasons catastrophic) handling of insights data is the reason.

Pls. everybody file a complaint to Athom so that they might come to their senses and revert the insights data handlingt to what it was before the last update!!!

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [December 19, 2025, 9:45am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/373 "2025-12-19T09:45:06Z")

</div>

Strange. on my first try to debug this issue, it didn’t worked. Once I re-selected the device from the flow card, it works again.

Could you try that?

---

<div class="post-metadata">

**Author:** ![4x4\_Pete](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/4x4_pete/32/113286_2.png) [@4x4\_Pete](https://community.homey.app/u/4x4_Pete)\
**Post date:** [December 19, 2025, 9:57am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/374 "2025-12-19T09:57:55Z")

</div>

For me that did not change anything.  
But I can confirm that calculations for time periods greater than one minute still work while for one minute or less they do not.

---

<div class="post-metadata">

**Author:** ![Tom\_Van\_de\_Putte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tom_van_de_putte/32/122561_2.png) [@Tom\_Van\_de\_Putte](https://community.homey.app/u/Tom_Van_de_Putte)\
**Post date:** [December 24, 2025, 7:51am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/375 "2025-12-24T07:51:11Z")

</div>

I can not use the app for 8 days now. Can anything be seen from my diagnostics? Anything I can do to assist to find this issue?

---

<div class="post-metadata">

**Author:** ![ersa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ersa/32/56495_2.png) [@ersa](https://community.homey.app/u/ersa)\
**Post date:** [January 2, 2026, 11:55am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/376 "2026-01-02T11:55:10Z")

</div>

Same here. 1 min does not work, but 3 min does. This has messed up my dynamic EV charge flows.

---

<div class="post-metadata">

**Author:** ![Philip\_Meulenkamp](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philip_meulenkamp/32/68549_2.png) [@Philip\_Meulenkamp](https://community.homey.app/u/Philip_Meulenkamp)\
**Post date:** [January 3, 2026, 9:22am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/377 "2026-01-03T09:22:29Z")

</div>

I have a flow to turn on the bathroom fan based on the steepness of increasing humidity (LV), based on the trend of the past 2 minutes. Doesn’t work anymore either.

Now adjusted to 3 minutes (see picture), see if that works.

I put timeline notifications on it for the benefit of debugging. the notifications ‘1LV BG’ and 2 Cal’ always come through, but the report ‘3 trend LV’ with also the value to which the trend calculation comes out does NOT get through.

I’m going to take a shower now, see if this works…

 ![Foto 03-01-2026 om 10.13](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/d/cdd99f2da3d27e968a48656d416df545e34c6d65.jpeg)

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [January 3, 2026, 11:46am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/378 "2026-01-03T11:46:48Z")

</div>

I’ve looked into this a bit deeper and both errors have the **same cause**.

**Both happen when Insights returns 0 logs (empty result).**

- **`Cannot read properties of undefined (reading 'y')`**  
→ With 0 logs there is no trend data, so the result is `undefined` and reading `.y` fails.
- **“Invalid token”**  
→ Also caused by 0 logs. Calculations end up with `NaN` or missing values and the parser throws an error.

That also explains why **1 minute doesn’t work** , but **2–3 minutes often does** :  
longer periods usually return at least some data points.

I didn’t change anything in the app that would cause this.  
This looks like a **change in Athom’s Insights handling** , especially for short time ranges with zero values.

At the moment there’s **nothing I can safely fix on app side**.  
**TL;DR:** It’s broken due to Insights returning 0 logs.

---

<div class="post-metadata">

**Author:** ![4x4\_Pete](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/4x4_pete/32/113286_2.png) [@4x4\_Pete](https://community.homey.app/u/4x4_Pete)\
**Post date:** [January 3, 2026, 11:56am UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/379 "2026-01-03T11:56:37Z")

</div>

This is caused by a bug in Athoms last update. - See [Rounded and flattened charts in Insights](https://community.homey.app/t/rounded-and-flattened-charts-in-insights/147075).  
They reduce data points as they normally only do for older data.

I recommend to complain/bug report to Athom to make sure, they put a fix high on the agenda for the next update.

[EDIT]  
Just got confirmation from Athom that the problem described in ”[Rounded and flattened charts in Insights](https://community.homey.app/t/rounded-and-flattened-charts-in-insights/147075)” will be fixed with the next update. - I am pretty positive, that this will resolve the problem here as wel.

---

<div class="post-metadata">

**Author:** ![Philip\_Meulenkamp](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philip_meulenkamp/32/68549_2.png) [@Philip\_Meulenkamp](https://community.homey.app/u/Philip_Meulenkamp)\
**Post date:** [February 5, 2026, 1:50pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/380 "2026-02-05T13:50:21Z")

</div>

Version 12.11.0 just landed.

My flows have come to life. Issue is fixed!

---

<div class="post-metadata">

**Author:** ![To\_Lou](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/to_lou/32/79159_2.png) [@To\_Lou](https://community.homey.app/u/To_Lou)\
**Post date:** [May 28, 2026, 1:17pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/381 "2026-05-28T13:17:20Z")

</div>

I think there’s a problem when calculation averages over one year, 365 days, as it seemingly divides between years, last year and this year.  
So the average I get looks like average from ‘last year’ data only?

---

<div class="post-metadata">

**Author:** ![P\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/p_w/32/71251_2.png) [@P\_W](https://community.homey.app/u/P_W)\
**Post date:** [September 24, 2026, 8:18pm UTC](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307/382 "2026-09-24T20:18:19Z")

</div>

I use trend for change in room humidity but this is since July not working anymore on homey pro 2026.

Looks like the trend is calculated but in flow it shows (-)

[Previous page](https://community.homey.app/t/app-pro-insight-trends-reloaded/71307.md?page=18)
