Domoticz doesn't keep running very long

[wkossen]

Hi,

i'm quite new to this, so this will probably be user error. My domoticz install will only run for a few hours and then not run anymore. There are error log entries, that i really cant logically tie to crashes like

2020-11-11 08:42:59.938 Error: (Space Weather) Device creation failed, Hardware/Unit combination (26:1) already exists in Domoticz.
2020-11-11 08:42:59.924 Error: (Corona Dashboard) 'onStart' failed 'KeyError'.
2020-11-11 08:43:40.236 Error: (FritzBox) restart cnx: ? last None or 0

so i did the old windows system administration trick to at least schedule restart at night in crontab, but that's not what i want.

how do i figure out what makes it stop/crash? and how to fix it? What info do you need on my setup (which is very much only a beginning/tryout type of thing) to help me with this?

Thanks for helping me.
Regards,
Willem

[psubiaco]

Hi Willem,
did you try to disable Space Weather, then Corona Dashboard, .... to determine which one is the problem?
I'm running domoticz in a raspberry PI3 and it works like a charme. No need to restart it or reset every day/week/month!
Paolo

[elzorrovega]

Hello Willem

I have the following setup

Linux raspberrypi2 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux
Domoticz Version 2020.2 running on Raspberry Pi (RPI) 3 B+ , 1G RAM

I and have the following connected

Code: Select all

Node		Name			Description					Manufacturer	ID	Type
014 (0x0e)	Garage D/W		FIBARO System FGDW002 Door Opening Sensor 2+	FIBARO System	0x1000	0x0702	
013 (0x0d)	Chamber 2 Motion Sensor	FIBARO System FGMS001-ZW5 Motion Sensor+	FIBARO System	0x1002	0x0801	
012 (0x0c)	Chamber 1 Motion Sensor	FIBARO System FGMS001-ZW5 Motion Sensor+	FIBARO System	0x1002	0x0801		
011 (0x0b)	Chamber 2 D/W		FIBARO System FGK101 Door Opening Sensor	FIBARO System	0x1000	0x0700	
010 (0x0a)	Chamber 3 D/W		FIBARO System FGK101 Door Opening Sensor	FIBARO System	0x1000	0x0700	
009 (0x09)	Bathroom D/W		FIBARO System FGK101 Door Opening Sensor	FIBARO System	0x1000	0x0700	
008 (0x08)	Hall Siren		AEON Labs ZW080 Siren Gen5+			AEON Labs	0x0050	0x0004	
007 (0x07)	Hall Keyboard		Schlage Link (Wintop) Mini Keypad RFID		Schlage Link 	0x4501	0x6131
006 (0x06)	Living Motion Sensor	FIBARO System FGMS001 Motion Sensor		FIBARO System	0x1001	0x0800	
005 (0x05)	Hall Motion Sensor	FIBARO System FGMS001 Motion Sensor		FIBARO System	0x1001	0x0800	
004 (0x04)	Chamber 1 D/W		FIBARO System FGK101 Door Opening Sensor	FIBARO System	0x1000	0x0700	
003 (0x03)	Chamber 1 Siren		AEON Labs ZW080 Siren Gen5+			AEON Labs	0x0050	0x0004	
002 (0x02)	Fibaro Wall Plug 1	FIBARO System FGWPE/F Wall Plug			FIBARO System	0x1000	0x0600	
001 (0x01)	Controller		AEON Labs ZW090 Z-Stick Gen5 EU			AEON Labs	0x005a	0x0001

Like all RPIs you need to restart LXPANEL, windows manager, periodically because it has memory leaks. You can put thjis in a script in cron.

Do you have the latest updates in your RPI? Are you running the Buster flavour of the Debian Distribution?

El Zorrovega

[wkossen]

i have lates rpi. how do i restart lxpanel? in fact, i don't need the gui at all, as i am running headless anyway and know my way around the cli (or at least, well enough)