Just to follow up guys:
I’ve moved my HG installation to a PC machine running Windows 10 and have had no issues.
It’s clearly unstable on Pi (well, at least on the newest Pi running the newest raspbian).
Works on Raspberry Pi3 and Zero W as long as you tie it to Mono version as above. The latest Raspberry Pi 3+ has problems the developers are still trying to resolve.
Works fine on the pi… its not unstable. .but one of the programs may be…
Can you edit your nlog config file and set the logfile level to trace if not already.
I have a script for backing up my installations that I use from my desktop… but I did intend to add functionality to do a scheduled backup… just never got around to it. .
Ill post the script later, it was on the old forum… infact… let me google…
2 secs later:
http://old.homegenie.club:8080/www.homegenie.it/forum/indexe1db.html?topic=1360.0
That may indeed be so. However, I’ve already moved the installation to a PC machine and have already connected a MySensors gateway and started connecting some other devices as well, and will most probably use the pi board for another project.
I am experiencing some weird behaviour with the UdpClientHelper at the moment - I’m working on a Program and a Widget to connect my BMW Wallbox charger to HG. Depending on how I go, I might open a separate thread here asking for some help or share my success 
1 Like
what wierd behaviour are you seeing… I vaguely remember someone raising an issue with the TCP or UDP helper on the old forum… but that was a while ago…
I’m running a 3B+ and have been for a while now.
initially I was experiencing the Issue reported in this thread however I removed programs (not just disable) not required like Philips hue, the IR controller…….
I’ve not had HG hang or die since but my setup here at the off grid place is small and mostly just X10 devices.
Yes stripping back your HomeGenie package should help as you’ve probably eliminated the offending program that is causing the issue. The offending package is probably missing a dependency which is triggering the crash.
What version of HomeGenie and Mono are you using on the 3B+.
Looks like @bkenobi solution of tying HomeGenie to Mono 5.4 is now a problem. I was doing a fresh install for another user yesterday and Mono will not let me tie to 5.4 now. It’s reporting that this version could cause problems to the system and would not proceed with Mono installation. It worked three weeks ago when I tried it.
My installation was not that stable either. I did not get Mono or HG messages though. I basically got frustrated after the 10th installation attempt. The info I provided was as optimized as I could come up with at the time, but it wasn’t perfect.
Your information you supplied earlier in the thread was working perfectly up till recently.
The Mono developers seem to have made changes in such a way that you can no longer tie version 4.5 of Mono to your Mono download.
What we need to do now is to get HomeGenie running in a current version of Mono. Maybe stripping back all the unnecessary add ins in HomeGenie till we find the offender as suggested earlier could help.
I’ve got a issue raised on the github site for a minimal version so this might be a good starting point…
Personally I would like to see Zwave, UPNP, X10 etc all split out as seperate projects and Interfaces that you install should you require them - also makes refactoring of those easier as it doesnt mean a new HG build, but that is @Bounz’s call
Also interesting around the mono version - I will take a look at this as well as it will probably be stopping my test hardware with the machinon from working…
A longer term option would be to ditch mono in its entirety and use .net core - but thats not a quick task!
If HomeGenie finds itself tied to a legacy version of Mono I’m afraid that not many Linux users will persevere with it.
many linux users probably shudder at the thought of it running in mono anway - which is where the docker route will help!
typing mono --version shows this:
Mono JIT compiler version 4.6.2 (Debian 4.6.2.7+dfsg-1)
Copyright © 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: normal
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen
Interestingly I never specifically installed a mono version I just installed HG 1.1 beta r526 if I remember right.
Maybe in all the excitement of trying to get HomeGenie working 
you’d forgotten that Mono is a requirement of v526 to get it running http://genielabs.github.io/HomeGenie/#/get_started
V526 and Mono 5.4 Complete were probably the most stable combination I’ve used to date. It sorted out SSL certificates which were constantly causing failures when using email notifications.
Mono is still an evolving software. Not ideal I’ll admit but it worked well enough with HomeGenie up to v526.
I’ve read mixed reviews about Docker. Have you tried out rkt. Works nicely with systemd I believe. Would this be an alternative for running HomeGenie I’m the Linux environment.
Again you’re the expert here on this one.
Nope! That states for optional packages SSL to be specific.
the latest Debian Stretch (Full) comes with SSL, not sure about the lite version.
Also if I did install mono it would have been 5.4 or newer I would have thought.
I know I installed mono complete on my pi zero originally but with trying different versions of Debian I doubt I installed it separately last time.
Since that is running in the city I can’t check it right now.
The quote under that section you mentioned as follows
Note HomeGenie requires mono runtime version 3.2 or later.
As far as I’m aware it never came prepackaged with HomeGenie so I’m not sure how you came to have it without installing it manually.
Unless you use the separate key signing method of installing Mono from its own project, the standard version of HomeGenie in the Stretch repos is 4.x
I guess to be sure I’ll have to pull out a fresh SD card and attempt a install of Debian then HG.
I believe that’s all I did last time but getting old sucks, sometimes I forget what I walked into a room for.