# \[APP\]\[Pro\] sysInternals - Shows Homey’s System Internals

**URL:** <https://community.homey.app/t/app-pro-sysinternals-shows-homey-s-system-internals/78650>\
**Category:** Apps\
**Tags:** app, homey-pro, homey-pro-2023\
**Created:** [March 30, 2023, 5:37pm UTC](https://community.homey.app/t/app-pro-sysinternals-shows-homey-s-system-internals/78650 "2023-03-30T17:37:57Z")\
**Posts on this page:** 1\
**Showing post:** 231

<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:** [February 21, 2026, 12:51am UTC](https://community.homey.app/t/app-pro-sysinternals-shows-homey-s-system-internals/78650/231 "2026-02-21T00:51:05Z")

</div>

> [@DoctorBazinga](#):
>
> Tried To import the file with that name an the content below but it only worked when the file was created in plain tekst (with notepad) an had this exact (filename) :
> 
> “Poll for firmware updates.homeyadvflow” (No .json ending or “aflowname”)

Yes code always needs to be handled by code editors, not the infamous _Word_ or such.

Ah, we learn every day, I didn’t know you’d have to save the flow export with it’s original name 🫡

It was exported as `Poll for firmware updates.homeyadvflow.json`  
When I remove the .json part prior to importing it, it is grayed out. I could import the flow on my 2 other Homey’s just fine with the .json part in the name.

“aflowname” was just a placeholder to use your own flowname. But apparently I have to pass the original flowname with flow exports. Thanks for the heads-up.

> [@DoctorBazinga](#):
>
> I could enable the automatic firmware update or even start the firmware update

Unfortunately Homeyscript limits the owner’s options;  
The firmware auto-update toggle and the backup enable toggle are read-only.  
So, you can check them, but not set them.

You’ll have to request for less tight Hscript permissions at Athom’s.

However, apps can have more permissions, so returning to your original request:  
if possible at all, and dev Geurt likes to extend the sysInternals app with Toggles for:  
enabling Firmware auto-updates,  
enabling auto-backups and  
manual firmware updates,  
we’ll be able to control it with flows.

> [@DoctorBazinga](#):
>
> (the last backup(how long ago)

Getting the timestamp is possible with this command:

```auto
const lAstbackup = await Homey.backup.getOptionLastSuccessfulBackup();
log('Last succesful Backup:', lAstbackup.value);

```

 ![927](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/c/4cbe063e57f0cc95b250c5ae0b8d3f24cf8f4002.jpeg)

Compare the two timestamps to get the ‘how long ago’ info.

With the tip from @smarthomesven I added the last changelog to the flow;  
For Pro 2023 and up:

 ![902](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f82692df8705d43bbed6c45793cc1fa36a557531.jpeg)

For Pro 2019 and earlier:

 ![906](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/d/4dc9f3b986dd32f876d1a18015ad509514e9ac12.jpeg)

---

_[View the full topic](https://community.homey.app/t/app-pro-sysinternals-shows-homey-s-system-internals/78650)._