#Temperature Plot
1 messages · Page 1 of 1 (latest)
Ahoi @jagged kelp!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message
you use a "not generic klipper sensor". this is a SGP40 and this modul is programmed, that the temperature is the VOC value. so its just an issue from your "unofficial klipper modul".
pls close this post when all questions are answered.
Is returning real temperature
check the output of:
http://<ip or hostname>/printer/object/objects/query?temperature_sensor%20filter_intake
I'm out of town for a few days so I can't run that now. Will do when I get home. Thanks for help
but this is your issue. your module report it "the wrong way", because all of these "unofficial modules" want to show this value in the chart, but moonraker only store temperature in the history. thats why they "hacked" them...
The hack is in moonraker?
why should this hack be in moonraker?
What do you mean by "the wrong way"?
My code is reporting temperature as temperature
these unofficial moduls uses the wrong value to "hack" the system to show it in the chart
is the github link above your own module?
Yes
why do you create another unofficial module for the same sensor?
(just out of interresst)
Because I couldn't find one that worked with moonraker update manager and vanilla klipper instead of a custom firmware
this one would work...
Archived
and here is also already an open PR for klipper itself
here the discussion about it: https://klipper.discourse.group/t/support-for-sgp40-sensors/20033
I created a PR to add support for the SGP40 Sensor. I’m not a python pro, so I’m happy for any input. I’m also unsure about adding the klippy-requirement. it looks a bit “wild” to me to add a lib just to convert the raw value. Link to the PR: sgp40: Add sgp40 support by meteyou · Pull Request #6738 · Klipper3d/klipper · GitHub
it doesnt matter...
How is this the wrong way?
at first, you look on the wrong object. do you use the nevermore module also?
(i see no log for your system here, so i dont know your system)
I don't use the nevermore module
the sgp40 object will create an printer object called sgp40 <name>. so all values from here: https://github.com/thetic/klipper-sgp40/blob/33a080926c1c43e58c83647eef883b1bfb404e83/src/klipper_sgp40/sgp40.py#L188
are only in this object. but the entry in the temperature list will use the object temperature_sensor <name> and only the "small values below the temperature" will only from the sgp40 <name> object.
Ahhh ty
but before you continue working on your other sgp40 fork / unofficial klipper modules, would you help me work on the PR for klipper so that the sensor simply gets “mainline klipper support”?
or can help me testing it? i hope to have time to finish the pr next week
I probably won't have time until the new year, but I'd be happy to help
I've copied your code here so i can use it in kalico. It won't boot.
it looks like sgp40 initialization depends on temperature/humidity sensor initialization but that order isn't guaranteed
the original code didn't have this issue
Did you install the dependency?
yes
I've done some significant rework: https://github.com/thetic/klipper-sgp40/blob/0d14f9f3fc7b335a986081a6d2fdab53b1be1651/src/klipper_sgp40/__init__.py
This will validate the ref_temp_sensor and ref_humidity_sensor settings at startup and adds a QUERY_SGP40 command
I still don't quite understand why mainsail is reporting the gas status as temperature though
I'm using the sensirion library from the pull request, but can switch to a local implementation fairly easily.
Mainsail has nothing like that implemented...
ya, it's somewhere in moonraker or klipper