Pauldy's House of Geek

————– First Step —————

Download tools from a site like https://www.apkmirror.com/
Kingo Root 4.5.6
Multi Action Home Button 2.5.0
Nova Launcher 5.5.4
Firefox 66.0.2-2015619145 very important for HA this build
AutoStart 2.2 No Root to launch custom UI apps on boot.

————– Second Step —————

Hold Finger Over IR Oval Press and Hold Bottom Relay 2
Button for 30 seconds
Head Straight to Settings.

Setup WiFi make sure to get the ip assigned once connected

Next Go To About Tablet
Tab Build Number 7 times
Back Out
Select Security
Check Unknown Sources
Back Down to Developer Options
Check Stay Awake, USB Debugging

reboot, small button on the bottom

—————— First Timer Backup Edison.zip ———————–

adb pull /device/edison.zip

This is just in case the device gets bricked at least you won’t find yourself SOL trying to locate an image on the internet if SHTF you’ll be able to recover using a usb ttl serial cable. 170MB over shit wifi will take a tik or two.

—————— ADB commands to interact with Device ————–
adb install “com.kingoapp.apk_4.5.6-456_minAPI16(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi).apk”
adb install “Multi action Home Button_v2.5.0_apkpure.com.apk”
adb install “com.teslacoilsw.launcher_5.5.4-59400_minAPI16(nodpi)_apkmirror.com.apk”
———— Optional —————
adb install “org.mozilla.firefox_66.0.2-2015619145_minAPI16(armeabi-v7a)(nodpi)_apkmirror.com.apk”
adb install “AutoStart No root_v2.2_apkpure.com.apk”

——————- Launch the Kingo Root ———————–
adb shell am start -n com.kingoapp.apk/com.kingoapp.root.LaunchActivity

——————- Launch Nova Launcher ———————–
adb shell am start -n com.teslacoilsw.launcher/.NovaLauncher

——————- Launch MA Home button ———————
adb shell am start -n com.home.button.bottom/com.home.button.activity.MainActivity

——————- Launch the Launcher ———————–
adb shell am start -n com.android.launcher/com.android.launcher2.Launcher

——————- Launch firefox HA ————————-
adb shell am start -n org.mozilla.firefox/.App https://homeassistant.local:8123/

<must root the device for these commands to work>

—————– Install The MQTT App ——————

adb push c:\adb\wink_manager /sdcard/wink_manager
adb push c:\adb\wink_manager.ini /sdcard/wink_manager.ini
adb shell
su
mount -o remount,rw /system
pm disable http://com.quirky.android.wink.projectone
rm /system/bin/edisonwink
cp /sdcard/wink_manager /system/bin/edisonwink
chmod 755 /system/bin/edisonwink

—- optional —-

setprop net.hostname <SomeWinkRelay>

———————– Power Management ———————-

adb shell svc power stayon false

———————– Remove Unused KingoRoot —————
adb uninstall com.kingoapp.apk

——————– Starting a package from the shell ———————

pm list packages

dumpsys package <com.android.launcher>

— find the action you want, in the case of launcher the following minus the <>

am start -n <com.android.launcher/com.android.launcher2.Launcher>

Multiple log entries similar to the following are caused by the homeassistant service receiving mdns across multiple interfaces. Those of us working across subnets and such will be susceptible to this. You may still want broadcasting of mdns across both broadcast domains so the best way to handle this is to block homeassistant from broadcasting across both as it already has an interface in each broadcast domain.

2025-03-29 00:24:49.309 homeassistant systemd-resolved[580]: Detected conflict on homeassistant601808.local IN A 10.x.x.x

Each device that handles the broadcasting of this information will be slightly different I use pfsense to manage this so in my case I simply add each interfaces ip address to the block list and it will prevent it from forwarding from those ips.

To restore the admin password on the controller, follow these steps:

1. Log in from the console.
2. Use “password” as the user name and use “forgetme!” as the password.
3. Enable the mode password as “enable”.
4. In configuration mode, enter the ‘mgmt-user admin root’ command to reset the admin password.
5. Re-login using the new admin password.
6. In configuration mode, enter the ‘enable secret’ command to reset the enable mode password.

 For example: 

 User: password
Password: forgetme!
(aruba) >enable
Password: enable
(aruba) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(aruba) (config) #mgmt-user admin root
Password: <new admin password>
Re-Type password: <new admin password>
(aruba) (config) #exit
(aruba) #exit
(aruba) >exit

Below are the steps to reset the enable mode password from the controller CLI.

User: admin
Password: <new admin password>
(aruba) >enable
Password: enable
(aruba) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(aruba) (config) #enable secret
Password: <new enable password>
Re-Type password: <new enable password>
(aruba) (config) #write memory

sometimes you have the admin password of the controller but not have the enable mode password so what to do…….?

Access the Controller via GUI And change the enable mode password in Controller Wizard.

Navigate to Configuration > Controller Wizard > Under Wizards > Configure Controller >Basic Info> Enter any Name of your choice, Password for User Admin, retype the same, Password for Enable mode Access here is the place where we can reset the enable mode password and retype the same click on Next

From the following site just in case it gets nuked, I scoured tons of pages before this one saved me and my purchase.

How to reset password for Aruba Controller

When securing your network it’s nice to have firewall rules that control traffic to only what you expect or allow and for this, you would need the ip of that device. With the amazon alexa there isn’t an easy way to do this so you have to start by getting the mac address of the device you’re trying to find the ip for.  You can do this if your alexa is already setup by going to https://alexa.amazon.com/.  From here click Settings on the left hand side, then under devices select the alexa you wish to find the ip address for.  Under the About section at the bottom of the page you can see the MAC address.  Copy this and the next step is dependent on your router.  Most allow you to see all the machines on your network.  find that page and simply search the MAC address.  You can also use various network scanning tools that will probe your network for machines.  Most all report the mac address and if they don’t you can 

cp /etc/php/7.2/fpm/pool.d/nextcloud.conf /etc/php/7.4/fpm/pool.d/

vi /etc/php/7.4/fpm/pool.d/nextcloud.conf

change the line 

listen = /run/php/php7.2-fpm.nextcloud.sock

to

listen = /run/php/php7.4-fpm.nextcloud.sock

Next we need to install some items that for whatever reason don’t get upgraded if you are using something other than pgsql change that here too.

apt install php7.4-fpm php-pgsql php-curl php7.4-xml php7.4-gd php-json php-mbstring php-zip php-bz2 php-intl php-ldap php-imap php-bcmath php-gmp php-redis php-igbinary php-memcache

systemctl enable php7.4-fpm

service php7.4-fpm start

grep php7.2-fpm `find ./`

change all these instances to php7.4-fpm

service apache2 restart

Doing these steps should solve the following errors:

No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.2-fpm.nextcloud.sock

Memcache \\OC\\Memcache\\Redis not available for local cache

Got error ‘PHP message: PHP Fatal error: Uncaught Doctrine\\DBAL\\DBALException: Failed to connect to the database: An exception occurred in driver: could not find driver

failed to make connection to backend: httpd-UDS

First we create multiple instances of octopi itself.

sudo su -
cd /home/pi
cp .octoprint .printer1
cp .octoprint .printer2

cd /etc/init.d
update-rc.d -f octoprint remove
cp octoprint printer1
cp printer1 printer2

cd /etc/default
cp octoprint printer1
cp octoprint printer2

Now we edit some files.

The way this works currently is you need to be able to access a remote url inside your home.  Usually this will require the use of a dynamic dos host provider that can provide you with a hostname that points to your dynamic home address that is updated automatically by your router.  This is not exactly ideal security wise but obscure enough that you’re not likely to have some hacker turning your lights on and off just to mess with you and about the worst case scenario is they turn all your lights on while you are way turning up your electric bill.

Bind is horrible at telling you what is going on if you happen to have the setup and mess it up.

Mod_mono is much easier to config at the moment than it has been int he past.  Assuming you can use apt-get and installed the packages the following is all you need.

Here are the steps to upgrading bugzilla so you don’t end up wanting to commit homicidal acts.

Download a new version of bugzilla and resist the patches.

http://www.bugzilla.org/download/

Unpack this new version into a newdirectory. I use the /usr/local directory.

root@sourcecontrol:/usr/local# ls -l
total 40
drwxr-x--- 16 www-data www-data 4096 May 28 11:36 bugzilla-4.4.2
drwxr-x--- 16 www-data www-data 4096 May 28 11:46 bugzilla-4.4.4

Now I keep a symlink in /var/www that points to the current version so i delete and update the symlink here.

ln -s /usr/local/bugzilla-4.4.4 /var/www/bugzilla
ls -l /var/www
lrwxrwxrwx 1 root root   26 May 28 11:37 bugzilla -> /usr/local/bugzilla-4.4.4/

Next enter the new bugzilla directory and update the perl modules using the built in script.

./install-module.pl --all

Once that is complete copy the localconfig form the previous installation into the new installation.

cp /usr/local/bugzilla-4.4.2/localconfig /usr/local/bugzilla-4.4.4/

Then run checksetup.pl and you should be up and running.

./checksetup.pl