System won't trigger restart - initial plugin config - no child bridge

[BKeyport]

Analysis

I noticed that when the system is recommending a child bridge after initial config, and you decline to do it (turn off the child bridge at the configuration page) - the system will save the config and not offer a restart. You have to either manually restart or go in and re-save the configuration for the system to offer the restart.

This screen:

Expected Behavior

I expect that when you decline the child bridge option as shown - the system will offer to restart, rather than just save the configuration.

Steps To Reproduce

1. install new module or delete the configuration in json config.
2. go to plugins page and hit the initial setup button
3. configure plugin and hit save/next (I don't remember which)
4. Decline child bridge on the next page (as shown in screen shot)
5. System will just save config, not offer restart.

Logs

N/A - no logs known to be generated.

Configuration

N/A - configuration of new module.

Environment

• OS: Various - Tested on Synology DSM and Homebridge OS
• Software: Various HB software
• Node: Not important
• npm: Not Important

Process Supervisor

other (Explain in Additional Context)

Additional Context

Use whatever supervisor is run in the HB os and Synology installs. Everything is generic and up to date.

Note: As system is not restarting, this also causes the system to not realize that the configuration has been saved.

[bwp91]

Good catch, and thanks for the clear write-up — the steps to reproduce were spot on, which made this quick to track down.

You were right that it did not belong in the main Homebridge repo, so I have moved it over here to the UI repo, which is where the behaviour actually lives.

The short version: when you decline the child bridge on that screen, the plugin config has genuinely been saved, but the restart prompt gets missed. So nothing is lost, it just does not tell you it needs restarting — which is also why it looks like it has not saved.

I am working on a fix now and it will be in the next beta.