1.Links have been updated in my original installation instructions to reflect HG 1.3 Stable v19
All system files can be found at /usr/local/bin/homegenie after installation.
I’ve no control over slow download speeds, faulty SD cards or versions of Raspberry Pi boards used. I did recommend using a RPI3+b for stable operation. I did highlight downloading the Raspberry PI OS Lite so there’s no way a full desktop version could appear after an update.
I think I provided enough instructions for even the most basic user to get HG up and running on the Raspberry Pi/
Yes you did! I just confirmed operations on my RP4 with this setup using HG and the X10 module with a CM19A transciever. Light on/off operational! Thanks for the explanations.
As for confusion, the original link you pointed to but do not maintain is wrong when it states for the raspberry PI installation that the home will be home/homegenie. It should be changed to /usr/local/bin where indeed everything exists! Thanks again!
Time to reopen this: my ZW pi stopped communicating on network sometime between 5pm yesterday and 10am this morning. Ping could not find it. I assume it died between 6am and 10am today as HG DID disarm the alarm. HG just keeps posting ‘event stream disconnected.’ Green lite solid on (normal) on the pi.
Cycled power to it to get it back. Now HG again has lost names on ALL x10 sensors, not just security modules. OpenWeather lost all its settings and it is back to default UK location, no key. e-mail tester program fails with ‘missing email address.’ HG email account back empty. Guess only my groups remained unchanged.
Thankfully a restore brought everything back.
So I guess this proves my old SD system was perfectly fine as this new HG only card looses all the HG data also.
Since others do not seem to have this issue of loosing all the customer data in HG, perhaps HG has grown to the point of requiring that fancier pi and the zero W is just too weak a performer? I wonder if anyone else is still using a model ZERO W?
I only had this issue when I first started playing with HG. I suspect it was due to the cheap SD 4 gig card I was using at the time. I have no idea what class it was but suspect it was slower then a class 6 it had no markings indicating the class. Moving to a larger faster SD card has in any case stopped me from experiacing this issue.
Resurrecting this with a newly received Pi4… It would NOT read my ZERO w Pi so I had to burn a new raw buster 8-20-2020 SD card. It fails on updating with the first line of mono code from Pete 11/30 how to install mono:
Failure is:
pi@raspberrypi4:~ $ sudo apt install apt-transport-https dirmngr gnupg ca-certificates
E: Type ‘“deb’ is not known on line 1 in source list /etc/apt/sources.list.d/mono-official-stable.list
E: The list of sources could not be read.
E: Type ‘“deb’ is not known on line 1 in source list /etc/apt/sources.list.d/mono-official-stable.list
E: The list of sources could not be read.
pi@raspberrypi4:~ $
Is this important? I plan to just keep going down Pete’s list and see if HG gets installed and runs…
Further, since first line of upgrade is wrong with “deb,” nothing else works as expected.
pi@raspberrypi4:~ $ sudo apt-get update
E: Type ‘“deb’ is not known on line 1 in source list /etc/apt/sources.list.d/mono-official-stable.list
E: The list of sources could not be read.
pi@raspberrypi4:~ $
pi@raspberrypi4:~ $ sudo apt-get install gdebi-core
E: Type ‘“deb’ is not known on line 1 in source list /etc/apt/sources.list.d/mono-official-stable.list
E: The list of sources could not be read.
E: Type ‘“deb’ is not known on line 1 in source list /etc/apt/sources.list.d/mono-official-stable.list
E: The list of sources could not be read.
pi@raspberrypi4:~ $
pi@raspberrypi4:~ $ sudo gdebi homegenie_1.3-stable.19_all.deb
sudo: gdebi: command not found
pi@raspberrypi4:~ $
So using chown and changing ownership from root to pi, I could not delete the offending etc/file but I could mofify it to be empty - that worked and allowed upgrade and update to work.
Ok down thru to LAST line of installing hg: sudo gdebi homegenie_1.3-stable.19_all.deb
HomeGenie - open source, programmable, home automation server for smart connected devices and applications.
Do you want to install the software package? [y/N]:Y
/usr/bin/gdebi:113: FutureWarning: Possible nested set at position 1
c = findall("[(/\S+[])]", msg)[0].lower()
pi@raspberrypi4:~ $ …
INTERESTING! Pi4 distinguishies between cap and non caps on the y/n answer! Resending the commmand and using lower case y let it installl… no clue it if works yet tho as out of time today
Well, pi4 installs and indeed runs much much faster than the zero w! HG restore file in zero takes 3-4-5 minutes to restore; here it took maybe 5 seconds.
I certainly did research my error (not a warning as your link pointed to). My error would not let gdebi even install. My research did not find any solution so I just went to the ext folder where the offending file was located and edited/deleted all content inside it (I could not get permission to delete the file itself with my chown command). Then reran the install command and it worked.
BTW, this is now the 3rd new SD card I have made with buster these last couple weeks. ALL 3 of course work, but all three insist there is a HG update available:
Solution in answer 1. You’re trying to run a warning/error message using sudo. Makes no sense. You’ll actually do more damage to your install entering random commands like that.
Answer was
sudo sed -i ‘s|"[[.]"|"[\(/\S+[\])]"|’ /usr/share/gdebi/gdebi
sudo sed -i 's|"[[.]"|"[\(/\S+[\])]"|’ /usr/share/gdebi/GDebi/GDebiCli.py
Findall=c was the output from the warning message not a command to run. I thought that was obvious from the link I sent you. Sudo sed was the solution. Sed is a stream editor that allowed you to edit the relevant file on the fly. Running that command resolved your issue. Randomly removing lines is not recommended unless you know what the implications are.
As was advised in the link I included you probably ran a command with an incorrect syntax which executed but didn’t execute correctly or executed partially.
