# \[APP\]\[Pro\] Synology

**URL:** <https://community.homey.app/t/app-pro-synology/49744>\
**Category:** Apps\
**Tags:** app, official, homey-pro\
**Created:** [July 24, 2021, 2:55pm UTC](https://community.homey.app/t/app-pro-synology/49744 "2021-07-24T14:55:38Z")\
**Posts on this page:** 20\
**Page:** 16

<div class="post-metadata">

**Author:** ![Heula](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heula/32/31852_2.png) [@Heula](https://community.homey.app/u/Heula)\
**Post date:** [April 5, 2023, 5:38am UTC](https://community.homey.app/t/app-pro-synology/49744/301 "2023-04-05T05:38:19Z")

</div>

> [@martijnpoppen](#):
>
> `console.log(await fetch('http://192.168.178.5:5000'));`

Problem is solved!  
For some reason the ip adress of my Homey was set on the blacklist on my NAS.  
Removed the ip adress from the blacklist and added it to the Whitelist and all is working again.

Can’t check the script now because my NAS is set to off (at work right now). So on/off setting is working again.

Because of many DOS attacks lately I have set it to go to the blacklist after one wrong password. Must be related to this but can’t happen no more, I think/hope.

Thanks for thinking with me.

This also solved my FTP client issue 😊

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 5, 2023, 6:37am UTC](https://community.homey.app/t/app-pro-synology/49744/302 "2023-04-05T06:37:17Z")

</div>

Nice ! 😃

---

<div class="post-metadata">

**Author:** ![Bert\_Wissink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert_wissink/32/30075_2.png) [@Bert\_Wissink](https://community.homey.app/u/Bert_Wissink)\
**Post date:** [April 25, 2023, 3:53pm UTC](https://community.homey.app/t/app-pro-synology/49744/303 "2023-04-25T15:53:47Z")

</div>

Hi again Martijn,

I still notice that the CPU usage (14 days old value) and disk usage (7 months old value) don’t get updated. When I check my NAS, the disk usage has a different value that the app is showing. Any idea?

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 25, 2023, 4:06pm UTC](https://community.homey.app/t/app-pro-synology/49744/304 "2023-04-25T16:06:21Z")

</div>

@Bert_Wissink  
Can you do a `update data` and send a report after that?

---

<div class="post-metadata">

**Author:** ![Bert\_Wissink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert_wissink/32/30075_2.png) [@Bert\_Wissink](https://community.homey.app/u/Bert_Wissink)\
**Post date:** [April 25, 2023, 4:51pm UTC](https://community.homey.app/t/app-pro-synology/49744/305 "2023-04-25T16:51:43Z")

</div>

Here you go

9cc6566b-c641-480a-85f2-65f8f0b7a99c

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 26, 2023, 7:26am UTC](https://community.homey.app/t/app-pro-synology/49744/306 "2023-04-26T07:26:59Z")

</div>

@Bert_Wissink I checked the logs, but according to the API you synology is at 100% CPU.

```auto
 "cpu": {
      "15min_load": 249,
      "1min_load": 289,
      "5min_load": 265,
      "device": "System",
      "other_load": 35,
      "system_load": 8,
      "user_load": 57
    },

```

The app calculates it as follows:

> other\_load + system\_load + user\_load = 100

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 26, 2023, 7:37am UTC](https://community.homey.app/t/app-pro-synology/49744/307 "2023-04-26T07:37:05Z")

</div>

@Bert_Wissink for the disk\_usage:

```auto
vol_info: [
    {
      desc: '',
      inode_free: '121078714',
      inode_total: '121798656',
      name: 'volume_1',
      status: 'normal',
      total_size: '1964237742080',
      used_size: '1578918449152',
      volume: 'volume_1'
    }
  ],

```

The app calculates it as follows:

> (used\_size / total\_size) \* 100

---

<div class="post-metadata">

**Author:** ![Bert\_Wissink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert_wissink/32/30075_2.png) [@Bert\_Wissink](https://community.homey.app/u/Bert_Wissink)\
**Post date:** [April 26, 2023, 11:42am UTC](https://community.homey.app/t/app-pro-synology/49744/308 "2023-04-26T11:42:29Z")

</div>

Thanks for checking this, Martijn!  
I will have a look into my NAS itself to validate if those numbers are in synch with those.  
Thanks!

---

<div class="post-metadata">

**Author:** ![Daniel\_Aaborg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_aaborg/32/71907_2.png) [@Daniel\_Aaborg](https://community.homey.app/u/Daniel_Aaborg)\
**Post date:** [April 28, 2023, 9:11pm UTC](https://community.homey.app/t/app-pro-synology/49744/309 "2023-04-28T21:11:32Z")

</div>

I created a flow to turn off my NAS in the night, and back on in the morning. The off-flow works without any issues, but not the on-flow. And I cannot turn it on using the button in the app neither.  
It reports I have to wait up to 10 minutes, before the NAS is shown as ON. But before it gets to that, it shows as OFF again, and nothing else happens.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 28, 2023, 9:43pm UTC](https://community.homey.app/t/app-pro-synology/49744/310 "2023-04-28T21:43:50Z")

</div>

@Daniel_Aaborg did you enable WOL on your NAS?

Make sure you have enabled WOL in your NAS.

> DSM → control panel → hardware & power → WOL on lan 1

If you want to use WOL. You can find the mac address here:

> DSM → control panel → info center → network → Lan 1 → mac address.

Fill this mac address in the device settings in Homey

---

<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:** [April 29, 2023, 8:01am UTC](https://community.homey.app/t/app-pro-synology/49744/311 "2023-04-29T08:01:19Z")

</div>

@martijnpoppen , may I ask, is the REBOOT button really REBOOT or it’s Shutdown ? I realized already twice that I had to send “Wake-up” (via ON - works fine) call to my Synology to get again operational… I think in both cases I was waiting like 5 or 10 min. Would debug logs make any sense next time ? Not sure…

When using Homey to “reboot button” from your app

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/8/9822b9f84ea59d9fe917ab664742469b593e0dbf.png)

When doing Reboot from DSM :

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aa5b3bf0793aa808f84374d1d8031b2ad3b122b4.png)

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 29, 2023, 9:38am UTC](https://community.homey.app/t/app-pro-synology/49744/312 "2023-04-29T09:38:15Z")

</div>

@Sharkys it should really reboot. It uses the reboot function from the API

---

<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:** [April 29, 2023, 9:15pm UTC](https://community.homey.app/t/app-pro-synology/49744/313 "2023-04-29T21:15:10Z")

</div>

Thank you Martijn, it’s weird, because in log under given Homey user, I see it initiated shutdown… ?  
Now I tested again - I wait 5min, then I had to do WOL.

adb37a9f-5e4d-486b-90d8-170d42457833

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/c/0ce57697d0ea0096efc75becd64a9d198de1013f.png)

I’m using DSM 7.1.1-42962 Update 5 on DS220+

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 30, 2023, 8:05am UTC](https://community.homey.app/t/app-pro-synology/49744/314 "2023-04-30T08:05:27Z")

</div>

Will check with DSM 7 🙂

---

<div class="post-metadata">

**Author:** ![DoctorBazinga](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doctorbazinga/32/39686_2.png) [@DoctorBazinga](https://community.homey.app/u/DoctorBazinga)\
**Post date:** [June 24, 2023, 10:00pm UTC](https://community.homey.app/t/app-pro-synology/49744/315 "2023-06-24T22:00:25Z")

</div>

Sorry if its already done/supoorted or answered.

Will/Does it support SRM of the synology routers (please) ?

I Would like to be able to (re)start and monitor my router from my Homey Pro 23

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [June 24, 2023, 10:13pm UTC](https://community.homey.app/t/app-pro-synology/49744/316 "2023-06-24T22:13:53Z")

</div>

@DoctorBazinga no it doesnt.  
Not sure if i’ll implement that. Got the request only 2 times. So not sure about that.

Depends on the amount of users who want this 😉

---

<div class="post-metadata">

**Author:** ![DoctorBazinga](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doctorbazinga/32/39686_2.png) [@DoctorBazinga](https://community.homey.app/u/DoctorBazinga)\
**Post date:** [June 27, 2023, 8:27pm UTC](https://community.homey.app/t/app-pro-synology/49744/317 "2023-06-27T20:27:40Z")

</div>

Can I maybe persuade you with some cup of Coffees or Cans of beer ?? 😉

---

<div class="post-metadata">

**Author:** ![Mike1233](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike1233/32/20991_2.png) [@Mike1233](https://community.homey.app/u/Mike1233)\
**Post date:** [June 27, 2023, 9:38pm UTC](https://community.homey.app/t/app-pro-synology/49744/318 "2023-06-27T21:38:39Z")

</div>

@DoctorBazinga  
[[PayPal.Me](https://www.paypal.com/paypalme/martijnpoppen)] 😉😉

But i think that Martijn needs more requests.

---

<div class="post-metadata">

**Author:** ![Heula](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heula/32/31852_2.png) [@Heula](https://community.homey.app/u/Heula)\
**Post date:** [August 1, 2023, 12:22pm UTC](https://community.homey.app/t/app-pro-synology/49744/319 "2023-08-01T12:22:11Z")

</div>

Hi @martijnpoppen what I’ve noticed for a while when I turn my nas on or off is the double notifications and illogical notifications.

When I turn it on, I see that the nas is turned on and turned off again a minute later, after which it is turned on again.  
Same thing when powering off but off on off.

In practice this is not the case at all so the question is why does the log see it differently?

f66dbed5-23ca-451a-aa35-a54eaf93aece

Thanks

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

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [August 1, 2023, 1:22pm UTC](https://community.homey.app/t/app-pro-synology/49744/320 "2023-08-01T13:22:47Z")

</div>

Hey @Heula (English topic 😉 )

Hmm only thing what i can think of. Homey can’t really see if the NAS is booting or not. There’s a timer which checks every now and then if it is up again.

I think that’s why it flashes. For Reboot I have some logic in place, but for turning on not really.

So what happens:

- send turn on
- homey checks status
- nas is booting, but not up
- status will be OFF
- when NAS is up, status will change to ON.

[Previous page](https://community.homey.app/t/app-pro-synology/49744.md?page=15)

[Next page](https://community.homey.app/t/app-pro-synology/49744.md?page=17)
