Change LAN TCP/IP for Powerline?

In case it helps anyone, I learned that the Orbi in AP mode picked up many of the IP addresses for the devices connected directly to the old router via EoC and Powerline, i.e. it showed them as attached devices in the router portal even though they were connected to the old router which was handling IP assignments.  The Orbi router showed 192.168.0 addresses for devices since the older router was now handling the duties.

Unfortunately with that setup, and I assume it was the old router (DLink 880L), some of the devices (both via Orbi and directly connected to the old router) would lose data throughput/buffer - they stayed connected but the signal was inconsistent - and defeated the primary goal to get a faster connector for some video devices via Powerline or EoC.

Therefore, I reset the Orbi to Router mode and the Dlink to bridge mode, and switched their positions (Modem-Orbi-Dlink-Powerline/EoC).  Interestingly the Orbi continued to show the devices connected via Powerline/EoC as connected devices , but with 192.168.0.X addresses, i.e their old addresses - however they were not really connected and had no internet access.  The Dlink in bridge mode was assigned a 192.168.1.X address, so it was connected, but wasn't passing along the Powerline or EoC.

Since the Dlink wasn't getting the Powerline and EoC devices access, I removed it.  However, the Orbi router then lost internet access and would not connect, even after rebooting several times. It somehow had become tied to the Dlink even though it was back in router mode.

I was thus forced to factory reset the Orbi and go through setup again.

Once back online, for one last attempt I changed the LAN settings for the Orbi router to use 192.168.0.X addresses (versus 192.168.1.X), and connected the Powerline and EoC connetions to the lan ports on the Orbi router.

Magically, all of my devices connected through Powerline and EoC now have internet access via the Orbi Router.  Quite some strange behavior of that router.