I used to use Static IP on every FPP (Pi or Beagle) but am not so consistent now.

I do have a Static (192.168.0.90) on my "Master" Pi that always sits in my computer room with the Antenna. From that FPP, I rely on the Multisync page to locate and access any other FPP on the system. That can vary from one to ten FPPs depending on what I'm testing or how close to Halloween or Christmas. Doesn't matter whether they are Standalone, Remote or Bridge. I only keep the one as Master, though.

I reloaded the image of 1.9, and it does the same thing. I did notice that if I don't have the "Enable LED Panel Output" checked in the LEDscape/Octoscoller LED panel, the FPPD will start. However, when I check the box it doesn't start.

I have 4 panel, but I am just trying to get one working now. Been having a hard time.

I figured out and got the entire 2 x 2 panel working. However, on the LED Panel Page, when I set up the page. When I save and restart the FPPD, my test sequences seem to work when tested. (I need to do further tests)

However, when I got back to the LED Panel Page, it does not pull in the current configuration. Mind you, it works. Just not showing the correct information when I reload the page.

Is there a way to have FPP boot faster than a minute and 47 seconds on a RaspPi3?? I timed this reaction from power on to first lights of sequence running. Could it be cut to under a minute, if possible?

One thing you can do to "speed things", at least a little bit, is to turn off the automatic checking for updates.

I think that the default should be DON'T check for updates.

Sounds reasonable to me. Now that we have a way to view the pending updates in the UI, it is easier for a user to check to decide if they want to pull in any new changes. I think I have an easy way to add this into the existing code for new users or builds, but want to think about it first. I made a note in my short-term "2017 Q4" ToDo list. I just knocked out one thing on that list by merging in all the changes from master-v1.x to the v1.9 branch. master-v1.x had several enhancements and bug fixes which I ran in my display last year but didn't want to release in mid to late December. That code has been stable for me, so I just pushed all those changes to v1.9 and built new v1.9 binaries and pushed them to the repo. If you are on v1.9, you will now see v1.9-64.

I'm also looking at merging the new channel outputs in master over to master-v1.x so they can be get into a v1.x release. This includes the Linsn and ColorLight support as well as support for the small ILI9488 LCD panels for the Pi that I posted a demo video of eons ago.