-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OctoDash support multiple instances of OctoPrint #1148
Comments
Probably something for after v3. |
I would also like to see this feature. I have two printers side by side, with the pi running OctoDash in the middle. A left/right arrow, or button to pop up a list of configured Printers/Octoprint instances would be ideal. There would also need to be a persistent title to display what the currently active printer is. |
I run 4 printers from my Pi 4 with 4 instances of Octoprint. It would be so cool to be able to configure and jump from one instance to another with one OctoDash screen. I used to work as an Angular developer and might be able help with some guidance. |
Definitely will be possible, the functionality to apply a new config without fully restarting the Pi is already there, so the only thing that is missing for this would be support for multiple configs (and a UI for that). While its not super easy, it isn't super complicated either. For a first version the UI can also be included in the Custom Actions, so you just would create a new Custom Action there until a fully fledged UI is available for that. |
Do you need people to test this? I just finished getting my Octoprint setup with two instances for my printers and would be more than willing to give this a try! |
Any update on this? @UnchartedBull |
Create copies of config.json to store as templates and edit for each instance (change URL, API key, name, etc. and add appropriate custom action as described below).
OCTO1: add custom action to config1.json
OCTO2: add custom action to config2.json
Install gcode system commands plugin in each instance and set commands as follows: OCTO1:
OCTO2:
|
Thanks for reply, but how to show ip on the screen? |
Maybe set the name in config files to match ip? Not sure of the question as it seems unrelated to the request. |
I have the same question as @GerogeFu. Issues #622 (Display network status icon with a current IP address) and #1202(Show IP on Dashboard) were both merged into this one and closed with the V3 milestone, but what they requested does not seem to have been implemented. I have some unresolved issues with my Pi3b+, in which sometimes the octoprint instance becomes unreachable and PuTty is unable to log in at what should be a static IP address assigned to the rPi. It would be very helpful if I could just glance at the Octodash screen, to see whether the rPi is still online & what is its current ip address. |
I just merged the issues into this one so it's easier to track. The functionality isn't implemented yet. |
I've just released version 0.0.7rc5 of OctoDash Companion plugin that can handle swapping instances in a little easier way than the hack approach mentioned above. It adds a new |
Hello everyone! Please add a display of the current IP address to the OctoDash screen. The printer is on a network that I cannot configure. The IP keeps changing and I have to sweat to connect to the web page. |
**Is your feature request related to a problem? I have a raspberry PI with 4 instances of OctoPrint installed controlling 4 printers. I installed OctoDash to the raspberry PI. It was aware of what instance I wanted OctoDash to control.
Describe the solution you'd like
It would be nice to be able to setup OctoDash to interact with all instances of OctoPrint. The feature would allow you to know what instance is active by displaying the Title from OctoPrint. There also would be a means to switch between active octoprint instance. Preferably this would be done with hot buttons on the main screen.
Link other projects
If you want OctoDash to include other OctoPrint plugins or similar please link them here.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: