Skip to content
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

[Enhancement] Float values vs string values #18

Open
alnavasa opened this issue Dec 5, 2023 · 2 comments
Open

[Enhancement] Float values vs string values #18

alnavasa opened this issue Dec 5, 2023 · 2 comments

Comments

@alnavasa
Copy link

alnavasa commented Dec 5, 2023

Some sensors such us print core, printer status or printed type should be a string, not a float, not possible to manage the history with float values for strings, and therefore automations harder to program (when going from printing to paused)

(Float values -> numbers
String values -> text)

@RedwoodForest
Copy link

Based on my local testing it seems like changing the unit of measurement for these sensors from "" to None fixes this issue. For example:

    "status": ["Printer status", None, "mdi:printer-3d"],

@alnavasa
Copy link
Author

alnavasa commented Feb 20, 2025

State_class: measurement

Does help too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants