Target Temperatures Can No Longer Be Displayed On The Same Graph As Actual Temperatures

Mar 13, 2025 by ADMIN 88 views

Target Temperatures Can No Longer Be Displayed on the Same Graph as Actual Temperatures: A Moonraker Integration Issue

As a 3D printing enthusiast, having a clear understanding of temperature readings is crucial for achieving optimal print quality. However, with the recent update to Moonraker integration version 1.7.0, target temperatures can no longer be displayed on the same graph as actual temperatures. This change, which migrated bed and extruder targets from sensor entities to number entities, has caused a significant inconvenience for users who rely on visualizing temperature data in real-time.

For those unfamiliar with the Moonraker integration, it is a powerful tool that allows users to monitor and control their 3D printers remotely. The integration provides a range of features, including temperature monitoring, print scheduling, and filament tracking. With the latest update, the bed and extruder targets have been moved from sensor entities to number entities, which has resulted in the separation of target and actual temperatures on the history graph card.

To better understand the issue, it's essential to describe the setup used in this scenario. The following components are part of the system:

Mainsail 2.13.2: This is the web interface used to control and monitor the 3D printer.
Moonraker 0.9.3-66: This is the integration software that connects the 3D printer to the web interface.
Klipper 0.12.0-452: This is the firmware used on the 3D printer.
Modded Ender 5 Plus: This is the 3D printer model used in this scenario.

The bug is quite straightforward. Since the update to Moonraker integration version 1.7.0, the target temperatures can no longer be displayed on the same graph as actual temperatures. This is because the number entities used for target temperatures do not have the same °C unit as the actual temperatures. As a result, the history graph card separates the target and actual temperatures automatically, making it difficult to visualize temperature data in real-time.

There are a few possible solutions to this issue:

Attach the proper unit to the new number entities: If it's possible to attach the proper unit to the new number entities, it would be useful to do so, allowing target temperatures to be displayed on the same graph as actual temperatures.
Support both sensor and number entities for target temperatures: Another possible solution is to support both sensor and number entities for target temperatures. This would allow users to choose which type of entity to use, depending on their preferences.

In conclusion, the recent update to Moonraker integration version 1.7.0 has caused a significant inconvenience for users who rely on visualizing temperature data in real-time. While there are possible solutions to this issue, it's essential to address the root cause of the problem. By attaching the proper unit to the new number entities or supporting both sensor and number entities for target temperatures, users can once again display target temperatures on the same graph as actual temperatures.

As the Moonraker integration continues to evolve, it's essential to prioritize user feedback and address issues like this one. By doing so, the community can continue to rely on the integration for their 3D printing needs.

Based on the information provided, here are some recommendations for users who are experiencing this issue:

Update to the latest version of Moonraker integration: Make sure to update to the latest version of Moonraker integration to ensure you have the latest features and bug fixes.
Check the history graph card settings: Check the settings for the history graph card to ensure that it's not separating the target and actual temperatures.
Contact the Moonraker community: If you're still experiencing issues, contact the Moonraker community for support and guidance.

For more information on the Moonraker integration and its features, please visit the official website. Additionally, the community forum is a great resource for users who are experiencing issues or have questions about the integration.

Moonraker Integration Documentation: The official documentation for the Moonraker integration provides a comprehensive guide to its features and settings.
Moonraker Community Forum: The community forum is a great resource for users who are experiencing issues or have questions about the integration.

The following image shows the history graph card with the target and actual temperatures separated:

This image illustrates the issue and highlights the need for a solution that allows target temperatures to be displayed on the same graph as actual temperatures.
Target Temperatures Can No Longer Be Displayed on the Same Graph as Actual Temperatures: A Moonraker Integration Issue - Q&A

Q: What is the issue with the Moonraker integration version 1.7.0?

A: The issue is that the target temperatures can no longer be displayed on the same graph as actual temperatures. This is because the number entities used for target temperatures do not have the same °C unit as the actual temperatures.

Q: Why was the change made to migrate bed and extruder targets from sensor entities to number entities?

A: The change was made to improve the integration's performance and functionality. However, it has caused a significant inconvenience for users who rely on visualizing temperature data in real-time.

Q: How can I display target temperatures on the same graph as actual temperatures?

A: Unfortunately, there is no straightforward solution to this issue. However, there are a few possible solutions that can be explored:

Attach the proper unit to the new number entities: If it's possible to attach the proper unit to the new number entities, it would be useful to do so, allowing target temperatures to be displayed on the same graph as actual temperatures.
Support both sensor and number entities for target temperatures: Another possible solution is to support both sensor and number entities for target temperatures. This would allow users to choose which type of entity to use, depending on their preferences.

Q: What are the benefits of displaying target temperatures on the same graph as actual temperatures?

A: Displaying target temperatures on the same graph as actual temperatures provides a clear and concise view of temperature data in real-time. This allows users to make informed decisions about their print jobs and optimize their printing process.

Q: How can I report this issue to the Moonraker community?

A: To report this issue to the Moonraker community, you can:

Visit the Moonraker community forum: The community forum is a great resource for users who are experiencing issues or have questions about the integration.
Submit a bug report: You can submit a bug report to the Moonraker team, providing detailed information about the issue and any relevant screenshots or logs.

Q: What are the next steps for the Moonraker integration?

A: The Moonraker team is committed to addressing this issue and providing a solution that meets the needs of the community. In the meantime, users can continue to provide feedback and suggestions for improving the integration.

Q: How can I stay up-to-date with the latest developments on the Moonraker integration?

A: To stay up-to-date with the latest developments on the Moonraker integration, you can:

Visit the Moonraker website: The official website provides a comprehensive guide to the integration's features and settings.
Follow the Moonraker community on social media: The community is active on social media platforms, providing updates and news about the integration.

Moonraker Integration Documentation: The official documentation for the Moonraker integration provides a comprehensive guide to its features and settings.
Moonraker Community Forum: The community forum is a great resource for users who are experiencing issues or have questions about the integration.

The following image shows the history graph card with the target and actual temperatures separated:

This image illustrates the issue and highlights the need for a solution that allows target temperatures to be displayed on the same graph as actual temperatures.