Show Active Spool for multiple instances

[PeteCondliffe]

Showing the active spool works (#86) great if you only have one instance of klipper however for multiple instances it appears there's no way of showing the active spool for each printer.
I can see the correct information if i go to https://[klipper url]:port/server/spoolman/spool_id on each instance I get the correct spool ID's.

[Disane87]

Can you test the following:
Add another spoolman instance with the same spoolman url but with other Klipper url.

Chances are high that this would work. Unfortunately I don’t have another Klipper instance so I can’t really test that.

[PeteCondliffe]

Nice idea for a workaround although it doesn't work unfortunately. The second device in HA generates no entities.

I enabled debugging then reloaded the device relevant parts of the logs seem to be

2024-05-13 22:03:53.087 DEBUG (MainThread) [custom_components.spoolman.coordinator] Finished fetching Spoolman data data in 0.021 seconds (success: True)
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Silver PLA+_1 already exists - ignoring sensor.esun_silver_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Black PLA+_2 already exists - ignoring sensor.esun_black_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Cold White PLA+_3 already exists - ignoring sensor.esun_cold_white_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Yellow PLA+_4 already exists - ignoring sensor.esun_yellow_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Pine Green PLA+_5 already exists - ignoring sensor.esun_pine_green_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Brown PLA+_6 already exists - ignoring sensor.esun_brown_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Grey PLA+_7 already exists - ignoring sensor.esun_grey_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Orange PLA+_8 already exists - ignoring sensor.esun_orange_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Blue PLA+_9 already exists - ignoring sensor.esun_blue_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Pink PLA+_10 already exists - ignoring sensor.esun_pink_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Light Blue PLA+_11 already exists - ignoring sensor.esun_light_blue_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Red PLA+_12 already exists - ignoring sensor.esun_red_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Purple PLA+_13 already exists - ignoring sensor.esun_purple_pla
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Light Blue PLA+_14 already exists - ignoring sensor.esun_light_blue_pla_2
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Blue PLA+_15 already exists - ignoring sensor.esun_blue_pla_2
2024-05-13 22:03:53.088 ERROR (MainThread) [homeassistant.components.sensor] Platform spoolman does not generate unique IDs. ID eSun Peak Green PLA+_16 already exists - ignoring sensor.esun_peak_green_pla

[Disane87]

I guess you got me wrong. It was only a way to test if multiple connection could work with that „workaround“. Actually this were only meant to be a workaround just for testing purposes.

Currently I have no idea to implement this in a proper and convenient manner. Need to think about it how and if I can solve this.

Multi printer with active spool never was on my list and focus so I didn’t implemented this. Indeed this is a great feature but this should be implemented pretty well and not just some hacky hacky stuff.

But let me have a think about this.

[PeteCondliffe]

Certainly interesting to know you can't add multiple devices. For a workaround creating the RESTful sensors described in #75 would work.

As for a permanent implementation: taking the assumption people using this will also be using the moonraker integration? How feasible it is i don't know but to me logicly would it not make sense for the moonraker integration to expose the spool ID's via a sensor then this integration to make use of them?

[Disane87]

In fact, I think that feature is better off in Moonraker and the integration. I would hate to implement something that would be better solved via an "official" way.

If Moonraker were to propagate the active spool per printer, then you could simply grab it in HA and then map it to the IDs from Spoolman. Therefore, it is actually more consistent that you would report this to Moonraker, that they offer the entity and that I remove the configuration for Moonraker from this navigation.

After I slept, I don't really like the integration of Klipper in this integration any more, as responsibilities are mixed up here.

[Disane87]

I have added a feature request to the Moonraker integration: marcolivierarsenault/moonraker-home-assistant#342

[PeteCondliffe]

makes sense. Thanks for your help and time on this