Can Not Access Device
**Description**
Updated my Hoobs in a box from v3 to v4. Migration process ran, came back to the page unable to connect, reviewed router and found device was assigned IP and tried to directly connect by IP and no connection was established nor was hoops.local working. Opened the device, plugged in HDMI and keyboard to find it listing v4 Hoobs but admin account I made did not work, but default account did. Once logged in as admin, followed process to uninstall v3 and install v4 but an unable to find hoobs hoobs-cli hoobs-gui etc. 

All attempts to reach the device remotely by SSH, IP, etc have failed after update but worked prior to v4 update. I can't understand how direct access I can run commands and ping servers but does not seem to be allowing remote connections post upgrade.

**Version**
Unknown - v4.19.97-v7 stated on screen but unsuccessful on fresh install.

**Did you upgrade**
Please let us know if you upgraded from a previous version.
- [ X] Yes
- [ ] No

**Pervious version**
If you upgraded, please let us know your previous version.

**Did you orginally upgrade to HOOBS 3 from HOOBS 2.1.1?**
Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
- [ ] Yes
- [ X] No 3 to 4

**What device are you using?**
Please let us know the device you are running HOOBS on.
- [X ] HOOBS Box
- [ ] HOOBS SD Card
- [ ] Custom Install

**If this is a custom install, what's your operating system?**
Please let us know what operating system and version you are using. Ex. Fedora 30 or macOS Catalina.

**List your plugins**
homebridge-dyson-link
homebridge-bond
homebridge-ring
homebridge-roomba-stv

**Post your config**
Can't paste direct access.
Server - port 80, origin *, autostart 0, home_setup_id "X-HM://0023ISYWYK99L
package manager "nom"
system "hoops"
This can be found in the interface, Configuration -> Advanced or you can get it via SSH `cat ~/.hoobs/etc/config.json`

* Remove any passwords from the config file. This is public.

```
POST CONFIG HERE
```

**Post your log**
You can get the log from the interface. This is in the Log section.

```
POST LOG HERE
```

**Additional context**
Add any other context about the problem here.
