You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When restarting Homebridge from Power Options screen, saving in JSON Config screen, or by modify a plugin config, you get the spinner as Homebridge goes through the process.
In dev mode, it would be nice if it automatically switched to the Logs screen, so you can watch the restart process.
The text was updated successfully, but these errors were encountered:
Better solution to avoid dev/not dev mode, would be to make Power Options a popup.
The popup will auto close once the service is running. Or it can be dismissed by the user with no adverse effects. So if I am on the Logs screen, I can restart Homebridge then dismiss the popup to watch the logs.
justjam2013
changed the title
Switch to Logs screen when Homebridge restarts
~~Switch to Logs screen when Homebridge restarts~~ Make Power Options a popup instead of a separate screen
Nov 18, 2024
justjam2013
changed the title
~~Switch to Logs screen when Homebridge restarts~~ Make Power Options a popup instead of a separate screen
~~ Switch to Logs screen when Homebridge restarts ~~ Make Power Options a popup instead of a separate screen
Nov 18, 2024
justjam2013
changed the title
~~ Switch to Logs screen when Homebridge restarts ~~ Make Power Options a popup instead of a separate screen
Make Power Options a popup instead of a separate screen
Nov 18, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Feature Description
When restarting Homebridge from Power Options screen, saving in JSON Config screen, or by modify a plugin config, you get the spinner as Homebridge goes through the process.
In dev mode, it would be nice if it automatically switched to the Logs screen, so you can watch the restart process.
The text was updated successfully, but these errors were encountered: