Hi everybody,
Looks like the story about the impact of the full moon is a truth: everybody become more emotional and aggressive . So I ask you to keep calm and help community and HomeGenie.
I completely agree with @David_Wallis that HG needs more automation tests in order that everybody can be sure that new features are not breaking existing ones. During refactoring of the statistics submodule I wrote a number of tests - so we have first steps done in this direction.
Also, I understand @raptorjr and @bkenobi problems with restoring backups from HG r526. I expected that this should work for most cases (and I personally was able to successfully restore my settingsā backup), but if you have problems - I think that they may be related with missing native libraries. Thatās what I suggest:
Iāll add more logging to the restore process and will publish the new version (I think it would be V1.1.16)
You will try to restore your backups on the fresh install of this version
I know that itās time-consuming and I very appreciate that you are spending your free time trying to catch all that bugs.
No, dotnet core works on RPi 2, too.
Finally, this topic looks overloaded, so I advise you to start a new topic for discussing different aspects of the system. For example, here is the topic to discuss Distribution and installation.
I didnāt realize we were considering this a different program from Geneās HG. I looked at it as the next version. There are lots of projects on GitHub that get forked and the new fork becomes the main version. If itās been rewritten in some way, then obviously compatibility issues may occur. In any case, since the project is still called HomeGenie, it seems reasonable for someone without any other knowledge to assume that they can simply upgrade to your version and their backups should work.
That said, since they donāt currently work, a simple work-around to get a backup to work should be possible. The backup file is a zipped file containing the different programs, modules, settings, etc. If the database is not compatible, the guide would say ādelete the database and insert database X in itās placeā. Obviously if the issue is inside a file like modules.xml, that would be a more difficult instruction.
As far as testing goes, I have my RPi3 running with the script I attached above without issue for over 1 week. When I restored my backup from 525, it started crashing and restarting the RPi every few hours. I am going to install 525 and let it sit for a few days and then restore my backup just to verify that the issue is HG and not the RPi. Assuming that goes well, weāll hopefully have 1.1.16 available so I can try again. When that is released, please make sure to note where the debug file you need is located so I can upload as necessary.
The main problem wil be as more commits go in then it stops being backwards compatibleā¦ I would really like to rename the Interface for the interfaces to be prefixed with an I but that would stop the third party hg interfaces from working unless they were updatedā¦ if we are going to go down this route then we really need to ensure that we are using semantic versioning (see semver.org for more info regarding this) but fundamentally changing the way the interfaces work might be a better idea after trying loading into a new appdomain didnāt fix the issues.
Is there a reason that after installing HG 1.1.15 I canāt run 525? I uninstalled the newer one and installed the older but it wonāt start up. I have done no debugging yet, just checking if thereās something known before I go further. I can create a new SD if that would be better.
As this project forks further from the last āofficialā release of HG v526 Iād imagine you will encounter problems like this. Possibly software that was installed in the newer version that conflicts with the older version. Iāve often had this problem with other variants of Linux.
Check your versions of Mono too. There was a significant upgrade to it quite recently which may affect downgrading to an older version of HG. Bounz reported difficulties when upgrading to Mono v5.1 recently,
As you say a fresh image is probably the quickest route.