# Insights give me an error on desktop: n.toLowerCase

**URL:** <https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [March 26, 2023, 11:41am UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416 "2023-03-26T11:41:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [March 26, 2023, 11:41am UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/1 "2023-03-26T11:41:06Z")

</div>

On desktop i get the following error when clicking on the insights tab ( Homey Pro 2023 ).

 ![Capture 2023-03-26 at 13.35.50@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/0/d020fe66dbfe87b94cbe210dfa86cb33392ae6c7.png)

As quickly as i click the insights menu everything disappears and i’ll see what’s on the screenshot. When i go back one page, i’ll have to refresh to get my menu back.

I’ve reported it often a new version came out, but still no luck.  
Is it something in my settings, of have more people this?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 26, 2023, 3:41pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/2 "2023-03-26T15:41:12Z")

</div>

[Known issue](https://community.homey.app/t/power-supply-can-cause-slow-homey-pro-2023/78279/50), it was discussed on Slack but I don’t think there’s a solution yet.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 26, 2023, 3:45pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/3 "2023-03-26T15:45:54Z")

</div>

Ah, just got an update from @Jero on Slack that this issue should be solved soon.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [March 26, 2023, 4:59pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/4 "2023-03-26T16:59:29Z")

</div>

@Jero can you explain why it happens and what resolved it. I’m very curious

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [March 26, 2023, 8:08pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/5 "2023-03-26T20:08:16Z")

</div>

Some logs have a units property that has an object in them with translations. The back end should pick the current value based on the current homey language but it doesnt do that.

So the front end expects units to be a string but it’s an object and toLowerCase on an object throws.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [March 26, 2023, 8:16pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/6 "2023-03-26T20:16:53Z")

</div>

Ah right, i debugged a bit and think it broke with °C but can’t be sure.  
I hope the fix is soon to be delivered. or is there a way to work around it (already)?

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [March 26, 2023, 8:20pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/7 "2023-03-26T20:20:53Z")

</div>

Not easy no. Deleting the log with the API should fix it but it might be recreated pretty soon after that.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 1, 2023, 9:16pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/8 "2023-04-01T21:16:14Z")

</div>

Is there a thing i can do myself, i really miss the insights

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [April 1, 2023, 9:39pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/9 "2023-04-01T21:39:48Z")

</div>

Have you updated to the latest rc?

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 1, 2023, 10:03pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/10 "2023-04-01T22:03:22Z")

</div>

i’ve got 10.0.0-rc.65 installed

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [April 1, 2023, 10:14pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/11 "2023-04-01T22:14:18Z")

</div>

Ah seems the rc with the fix is still in experimental. It should be fixed in rc66.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 1, 2023, 10:16pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/12 "2023-04-01T22:16:04Z")

</div>

Thanks, i’m looking forward to it.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 3, 2023, 12:32pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/13 "2023-04-03T12:32:54Z")

</div>

Even to i upgraded to \*.70, that still didn’t help.  
I’ll contact athom …

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 3, 2023, 12:38pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/14 "2023-04-03T12:38:23Z")

</div>

Sounds like the issue is (partially) with the frontend, so try cleaning your browser cache (at least for `*.homey.app`).

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 3, 2023, 1:23pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/15 "2023-04-03T13:23:13Z")

</div>

I test in an incognito window and brave / chrome report the same error

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [April 3, 2023, 1:39pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/16 "2023-04-03T13:39:46Z")

</div>

Ok this is really odd I will see if I can ignore it in the web app and add some extra logging.

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [April 3, 2023, 2:29pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/17 "2023-04-03T14:29:16Z")

</div>

It should no longer crash now can you confirm that?

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 3, 2023, 2:29pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/18 "2023-04-03T14:29:43Z")

</div>

` Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Ben%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.`

[update]: This was on the console

 ![Capture 2023-04-03 at 16.31.23@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/5/c552c54730072fc0d8b7ce5cc08db5528720e809.png)

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [April 3, 2023, 2:57pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/19 "2023-04-03T14:57:13Z")

</div>

Ja … hij doet het … 😃

---

<div class="post-metadata">

**Author:** ![Jero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jero/32/17556_2.png) [@Jero](https://community.homey.app/u/Jero)\
**Post date:** [April 3, 2023, 2:59pm UTC](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416/20 "2023-04-03T14:59:55Z")

</div>

Band aid fix 😄

I made the mistake assuming the fix was shipped in rc.66 but it is not.

[Next page](https://community.homey.app/t/insights-give-me-an-error-on-desktop-n-tolowercase/78416.md?page=2)
