# \[HomeyScript\] Regular system overview by email with a change summary

**URL:** <https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768>\
**Category:** Tutorials\
**Tags:** homey-pro, system-about, system\
**Created:** [August 26, 2026, 8:40am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768 "2026-08-26T08:40:17Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![telenut](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/telenut/32/12666_2.png) [@telenut](https://community.homey.app/u/telenut)\
**Post date:** [August 30, 2026, 4:36pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/22 "2026-08-30T16:36:01Z")

</div>

That fixed it! thx!

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [August 31, 2026, 3:24pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/23 "2026-08-31T15:24:29Z")

</div>

Just to let you know, it looks pretty accurate. This is one of the ideas & scripts you didn’t know you needed, until you use it. Well done! 🥳

> ![Screenshot_20260831_172022_Proton Mail](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/b/5bb5eae0b2efbb3ba69db5251b58d05fc3bd9fb9.jpeg)

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [August 31, 2026, 7:44pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/24 "2026-08-31T19:44:03Z")

</div>

Thanks, appreciated!

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 1, 2026, 7:53am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/25 "2026-09-01T07:53:42Z")

</div>

Update to 1.4.0 fixes an inconsistency in the detailed report: variables and scripts are now also listed.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 1, 2026, 11:12am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/26 "2026-09-01T11:12:21Z")

</div>

Thanks, Dagmar!

A bit of nitpicking 😊 :  
The comments mentioning Homey Pro 2023 got me a bit confused, because it is not a unique model regarding functionality;  
Because the Pro 2026 and Pro Mini use the same firmware, I think the comments solely mentioning `Homey Pro 2023` should be adjusted a bit.  
Which makes me think, Homey SHS has / should have the same functionality as well (apart from all wireless protocols but WiFi)

Maybe something like `Homey Pro models (post 2022) & Homey Self-Hosted` covers it?

Lines I found:

```auto
039. const showGroupDevices = true; // Show composition of group devices (Homey Pro 2023 only)
491. let groupDevices = {}; // groupId -> { name, devices: [] }, Homey Pro 2023 only

```

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 2, 2026, 6:01am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/27 "2026-09-02T06:01:20Z")

</div>

Fair point, thanks for catching that, and no nitpicking at all. 😊

All comments referring to “Homey Pro 2023” now say “Homey Pro models post-2022” instead.

On Homey Self-Hosted specifically: I don’t have one to test against, so I can’t confirm whether it reports the same `homeyPlatformVersion` value. If you (or anyone running SHS) can check, I’d be happy to update the wording further based on that.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 2, 2026, 11:40am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/28 "2026-09-02T11:40:14Z")

</div>

YW!  
Yeah I’ll fire up a test Homey SHS to check on that.

EDIT: Done @DGalama

```auto
--------------- Homey Pro Overview (v2 API) --------------
Homey name: Homey Self-Hosted Server
Homey version: 13.4.1
Homey model: Homey Self-Hosted Server (4 core(s))
Uptime: 34435.33 (9 hours, 33 minutes, 55 seconds)
WiFi: not connected
Ethernet: not connected
Update available: None
Failed: Getting last backup
Storage: 42796822528 total, 12002664448 free

------------------ Main ---------------------
1 Users (1 owner, 0 manager(s), 0 user(s), 0 guest(s))
---------------------------------------------
SDKv3 apps:
HomeyScript
Email sender
---------------------------------------------
---------------------------------------------
Updateable apps:
---------------------------------------------
---------------------------------------------
Disabled apps:
---------------------------------------------
---------------------------------------------
Crashed apps:
---------------------------------------------
2 Apps (2 Stable, 0 Test, 0 Development, 0 SDKv2, 2 SDKv3, 0 updateable, 0 disabled, 0 crashed)
5 Zones
1 Notifications (Timeline)
1 Logic Variables (0 boolean (yes/no), 0 number, 1 string)
---------------------------------------------
Disabled flow names:
---------------------------------------------
---------------------------------------------
Broken flow names:
---------------------------------------------
0 Flows (0 broken, 0 disabled)
---------------------------------------------
Disabled advanced flow names:
---------------------------------------------
---------------------------------------------
Broken advanced flow names:
---------------------------------------------
0 Advanced flows (0 broken, 0 disabled)
0 Moods
0 Alarms (0 enabled)
Failed: Getting HomeyScript

----------------- Devices -------------------
---------------------------------------------
Virtual devices:
---------------------------------------------
---------------------------------------------
Infrared devices:
---------------------------------------------
---------------------------------------------
Other devices:
---------------------------------------------
0 Virtual devices
0 Infrared (database) devices
0 Other devices
0 Group devices
0 UniFi network-presence devices excluded
Failed: Getting Z-Wave State
---------------------------------------------
ZigBee nodes:
---------------------------------------------
---------------------------------------------
ZigBee routers:
---------------------------------------------
---------------------------------------------
ZigBee end devices:
---------------------------------------------
0 Zigbee nodes (0 router, 0 end device, 0 unknown type)
0 Total devices
Email sent to xxxxxxx

———————————————————
✅ Script Success
↩️ Returned: "Overview finished, email sent to xxxxxxx

```

.

Two things I noticed:

1. 

`Ethernet: not connected`  
It surely is, but it uses Host Networking mode using the host (Home Assistant) LAN adapter (@ port 4859)  
(see [https://github.com/Doekse/addon-homeyshs/blob/main/homey-shs%2FDOCS.md](https://github.com/Doekse/addon-homeyshs/blob/main/homey-shs%2FDOCS.md)).  
I noticed with the SHS model there’s no distinguishing between Ethernet/WiFi; it just mentions “a” network connection IP & MAC → see developer site screenshot:

 ![Screenshot_20260902_152021_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/2/4256141ffd61fcdf9e5b9269c6621c6fdcaafa6a.jpeg)

1. 

In general (both Pro & SHS related): I"ve disabled all z-wave and zigbee checks,

 ![Screenshot_20260902_145128_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/9/698149b71e26b68299f18813d4a139fd189c7096.jpeg)

but both still are mentioned in the initial / full report. Is this just by design, or is it possible to omit the related entries from the report when these checks are disabled?

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 2, 2026, 8:00pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/29 "2026-09-02T20:00:52Z")

</div>

Thanks for testing this on Self-Hosted! Issues should be fixed now.

**WiFi/Ethernet false “not connected”:** SHS seems to have no separate WiFi/Ethernet radios to query, so those fields always came back `false`. Fixed in v1.5.1 and is now detected via the Homey model name and shown as “-” on SHS instead of a false alarm.

**Backup-status check failing:** same root cause (`homeyPlatformVersion` couldn’t tell Pro 2023+ apart from SHS). Fixed in v1.5.2 and excluded specifically for SHS, storage/throttling untouched.

Two things still open, and I would appreciate your input:

- `getAppSettings` for HomeyScript also fails on SHS. Do you know if it’s exposed under a different app id there?
- The Z-Wave/Zigbee section headers showing even with all toggles off is actually consistent with every other category (only name lists are toggle-gated). Thinking about a proper “hide whole section” master toggle later, across all categories at once.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 2, 2026, 11:19pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/30 "2026-09-02T23:19:00Z")

</div>

With pleasure!

> [@DGalama](#):
>
> Backup-status check failing:

Ahhh good catch as well!

> [@DGalama](#):
>
> - `getAppSettings` for HomeyScript also fails on SHS. Do you know if it’s exposed under a different app id there?

In the web app URL it’s the same as for the Pro 2026: `com.athom.homeyscript`  
Oh, and as a test I installed BLL and it shows the test variable I created.

> [@DGalama](#):
>
> - The Z-Wave/Zigbee section headers showing even with all toggles off is actually consistent with …

No problem, I’m all hands down for a “master toggle” some day.

.

→ Here’s the v1.5.2 output of a Homey SHS

```auto
--------------- Homey Pro Overview (v2 API) --------------

Homey name: 5.Homey SHS

Homey version: 13.4.1

Homey model: Homey Self-Hosted Server (4 core(s))

Uptime: 73652.7 (20 hours, 27 minutes, 32 seconds)

Update available: None

Storage: 42796822528 total, 11929735168 free

------------------ Main ---------------------

1 Users (1 owner, 0 manager(s), 0 user(s), 0 guest(s))

---------------------------------------------

SDKv2 apps:

---------------------------------------------

---------------------------------------------

SDKv3 apps:

Better Logic Library
Email sender
HomeyScript

---------------------------------------------

---------------------------------------------

Updateable apps:

---------------------------------------------

---------------------------------------------

Disabled apps:

---------------------------------------------

---------------------------------------------

Crashed apps:

---------------------------------------------

3 Apps (3 Stable, 0 Test, 0 Development, 0 SDKv2, 3 SDKv3, 0 updateable, 0 disabled, 0 crashed)

5 Zones

1 Notifications (Timeline)

1 Logic Variables (0 boolean (yes/no), 0 number, 1 string)

---------------------------------------------

Disabled flow names:

---------------------------------------------

---------------------------------------------

Broken flow names:

---------------------------------------------

1 Flows (0 broken, 0 disabled)

---------------------------------------------

Disabled advanced flow names:

---------------------------------------------

---------------------------------------------

Broken advanced flow names:

---------------------------------------------

1 Advanced flows (0 broken, 0 disabled)

0 Images

0 Moods

0 Alarms (0 enabled)

Failed: Getting HomeyScript

1 Better Logic Variables (0 boolean (yes/no), 0 number, 1 string)

----------------- Devices -------------------

---------------------------------------------

Virtual devices:

---------------------------------------------

---------------------------------------------

Infrared devices:

---------------------------------------------

---------------------------------------------

Other devices:

---------------------------------------------

0 Virtual devices

0 Infrared (database) devices

0 Other devices

0 Group devices

0 UniFi network-presence devices excluded

Failed: Getting Z-Wave State

0 Zigbee nodes (0 router, 0 end device, 0 unknown type)

0 Total devices

Email sent to xxxxxxx

———————————————————
✅ Script Success

↩️ Returned: "Overview finished, email sent to xxxxxxxx"

```

.

Emailed report:

 ![Screenshot_20260903_011752_Proton Mail](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/4/34bc7f49c987baf60191fdcbbb6e4291c3da30b1.jpeg)

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 3, 2026, 4:22am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/31 "2026-09-03T04:22:26Z")

</div>

Good catch on both, that rules out a wrong app id, and it’s useful that BLL’s `getAppSettings` works fine on SHS while HomeyScript’s doesn’t. So it’s failing for a more specific reason, not a blanket SHS limitation.

Rather than guess, I just added logging in v1.5.3: the actual error message, and what fields the returned object actually has.

Can you run it once more and paste the console log? That should tell what’s different about the HomeyScript response on SHS.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 3, 2026, 12:50pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/32 "2026-09-03T12:50:30Z")

</div>

Here you go:  
`Failed: Processing HomeyScript settings — Cannot convert undefined or null to object — result keys: id, uri, scripts`

Full log:

```auto
--------------- Homey Pro Overview (v2 API) --------------

Homey name: 5.Homey SHS

Homey version: 13.4.1

Homey model: Homey Self-Hosted Server (4 core(s))

Uptime: 122512.02 (1 day, 10 hours, 1 minute, 52 seconds)

Update available: None

Storage: 42796822528 total, 11553501184 free

------------------ Main ---------------------

1 Users (1 owner, 0 manager(s), 0 user(s), 0 guest(s))

---------------------------------------------

SDKv2 apps:

---------------------------------------------

---------------------------------------------

SDKv3 apps:

Better Logic Library
Email sender
Home Assistant Community
HomeyScript

---------------------------------------------

---------------------------------------------

Updateable apps:

---------------------------------------------

---------------------------------------------

Disabled apps:

---------------------------------------------

---------------------------------------------

Crashed apps:

---------------------------------------------

4 Apps (3 Stable, 1 Test, 0 Development, 0 SDKv2, 4 SDKv3, 0 updateable, 0 disabled, 0 crashed)

5 Zones

1 Notifications (Timeline)

1 Logic Variables (0 boolean (yes/no), 0 number, 1 string)

---------------------------------------------

Disabled flow names:

---------------------------------------------

---------------------------------------------

Broken flow names:

---------------------------------------------

1 Flows (0 broken, 0 disabled)

---------------------------------------------

Disabled advanced flow names:

---------------------------------------------

---------------------------------------------

Broken advanced flow names:

---------------------------------------------

1 Advanced flows (0 broken, 0 disabled)

0 Images

0 Moods

0 Alarms (0 enabled)

Failed: Processing HomeyScript settings — Cannot convert undefined or null to object — result keys: id, uri, scripts

1 Better Logic Variables (0 boolean (yes/no), 0 number, 1 string)

----------------- Devices -------------------

---------------------------------------------

Virtual devices:

---------------------------------------------

---------------------------------------------

Infrared devices:

---------------------------------------------

---------------------------------------------

Other devices:

Itho Fan

---------------------------------------------

0 Virtual devices

0 Infrared (database) devices

1 Other devices

0 Group devices

0 UniFi network-presence devices excluded

Failed: Getting Z-Wave State

---------------------------------------------

ZigBee nodes:

---------------------------------------------

---------------------------------------------

ZigBee routers:

---------------------------------------------

---------------------------------------------

ZigBee end devices:

---------------------------------------------

0 Zigbee nodes (0 router, 0 end device, 0 unknown type)

1 Total devices

Email sent to 

```

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 3, 2026, 9:44pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/33 "2026-09-03T21:44:28Z")

</div>

Thanks, think I fixed it. On Self-Hosted the `tokens` key was missing from the response, which crashed the whole HomeyScript section. Should be fixed in **v1.5.4.**

Let me know if it’s clean now.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 3, 2026, 10:18pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/34 "2026-09-03T22:18:00Z")

</div>

Confirmed, it’s clean with v1.5.4

```auto
--------------- Homey Pro Overview (v2 API) --------------

Homey name: 5.Homey SHS

Homey version: 13.4.1

Homey model: Homey Self-Hosted Server (4 core(s))

...

17 HomeyScript scripts (0 tokens/tags)

1 Better Logic Variables (0 boolean (yes/no), 0 number, 1 string)

...

```

And the mailed report shows the scripts listing:

 ![Screenshot_20260904_001924_Proton Mail](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/2/4292a0a3f6c4689b968be3fab2157cbfe6dad695.jpeg)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 4, 2026, 10:22am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/35 "2026-09-04T10:22:19Z")

</div>

This possibly crossed your mind as well: Nice to have: filter the “example-xxx” scripts from the script listing?

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 4, 2026, 11:27am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/36 "2026-09-04T11:27:56Z")

</div>

Yes, that did cross my mind. 🙂 I occasionally use some of those example scripts, which is why I did not consider this too important. But since now someone is thinking the same, I added it as a toggle: `showExampleScripts` (default off, filters them out) so you can flip it back on if you use them. Now live in v1.5.5.

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 9, 2026, 9:37am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/37 "2026-09-09T09:37:41Z")

</div>

v1.6: I added WhatsApp-functionality, so you can also receive the summary in WhatsApp.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 9, 2026, 5:54pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/38 "2026-09-09T17:54:10Z")

</div>

Very cool again, Dagmar!

With an already configured CallMeBot WhatsApp “device”, the WhatsApp message appeared right away:

 ![Screenshot_20260909_192408_WhatsApp](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/2/52b7627fa5f0e0fd870bc1c61ee888172a1c2c5f.jpeg)

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 10, 2026, 9:39pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/39 "2026-09-10T21:39:47Z")

</div>

**v1.7.0 updates:**

- Zigbee nodes that haven’t reported in longer than `zigbeeStaleDays` (default 3 days) are now flagged in the Summary, same as Z-Wave already did.
- Low-battery warning (`lowBatteryWarningPercent`, default 20%), across all device types, excluding EVs.
- Unexpected Homey restarts are now detected via uptime comparison.
- The footer now also shows the actual script’s name (“…HomeyScript homey-overview v1.7.0”), read dynamically

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 18, 2026, 12:46pm UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/40 "2026-09-18T12:46:43Z")

</div>

**Homey Overview v1.7.1 update:**

- Zigbee and Z-Wave devices are now diffed by their stable ID instead of by name, so renaming a device in the Homey app shows up as a single “renamed” entry instead of a confusing remove+add pair.
- Added diagnostic logging for a rare case where the Storage field showed “-” — no fix yet (cause still unknown), but next occurrence should give more info.

---

<div class="post-metadata">

**Author:** ![DGalama](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dgalama/32/10402_2.png) [@DGalama](https://community.homey.app/u/DGalama)\
**Post date:** [September 20, 2026, 10:04am UTC](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768/41 "2026-09-20T10:04:45Z")

</div>

**Homey Overview v1.7.2 - update**

- **Zigbee “not responding” / Z-Wave “unreachable” tracking** could get confused if you renamed a device while it was already stale/unreachable. It would falsely report it as both “recovered” and “newly affected” in the same run. Now tracked by stable ID instead of name, so a rename alone no longer triggers a false pair.
- **Basic and Advanced flows** are now also diffed by their stable ID, so renaming a flow is reported as “renamed” instead of a confusing delete+create pair, and if a flow is renamed _and_ becomes broken/disabled in the same run, both changes are now reported separately (previously one could mask the other).

[Previous page](https://community.homey.app/t/homeyscript-regular-system-overview-by-email-with-a-change-summary/158768.md?page=1)
