2 minutes delay in device trigger DZVents in log

Easy to use, 100% Lua-based event scripting framework.

Moderator: leecollings

klaaspiet
Posts: 34
Joined: Tuesday 09 January 2018 8:29
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Harlingen
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by klaaspiet »

Hey. Thank al for the help. I dit der that the rate limit of the p1 USB hardware is 0. If i increase that the CPU is going down.
Attachments
2F9A3D4C-7B76-4196-A5FA-B047BF9B2C84.png
2F9A3D4C-7B76-4196-A5FA-B047BF9B2C84.png (126.3 KiB) Viewed 405 times
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by waaren »

klaaspiet wrote: Sunday 30 December 2018 15:19 the rate limit of the p1 USB hardware is 0. If i increase that the CPU is going down.
The value of 0 is the default. The CPU usage will go down if you raise it but I expect that this is not the root cause of your CPU usage problem.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
klaaspiet
Posts: 34
Joined: Tuesday 09 January 2018 8:29
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Harlingen
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by klaaspiet »

I set the rate limit on 120sec. And now my CPU is 21 25%. And my scrips are working fine.
User avatar
Egregius
Posts: 2592
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by Egregius »

Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by waaren »

Egregius wrote: Sunday 30 December 2018 16:59 Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
Wow these Raspberries must be much faster in Belgium than they sell them in the Netherlands... :D
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
klaaspiet
Posts: 34
Joined: Tuesday 09 January 2018 8:29
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Harlingen
Contact:

Re: 2 minutes delay in device trigger DZVents in log

Post by klaaspiet »

waaren wrote: Sunday 30 December 2018 17:51
Egregius wrote: Sunday 30 December 2018 16:59 Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
Wow these Raspberries must be much faster in Belgium than they sell them in the Netherlands... :D
:D
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest