Inverter temperature sensor value spiking to ~ -9,000C (exact value varies) since around 4th November.

[LoznOz]

The problem

Its summer here, so higher temps & I noticed solar Inverter was quite hot one day so I checked the temperature sensor from Solax inverter integration - it was fine real time (40C) but on looking then at history I see these apparently random (x7 this month) sudden drops in temperature history to -9,824C at around (but not exactly the same time) 5:50AM. (I determine this by clicking on the HA history graph to see temp value and time.) Last month I see seven too, however temp then dropped to between -57C and -249C. These drops occur all the way back till I installed integration August 2023 I now see. I've attached screenshots which hopefully is sufficient to show the description of the issue. Other observation is the drops to the -9000 range have started from around November this year - again visual indication from Inverter temperature history graphs.
The effect is temperature monitoring by visual graph is now being effectively masked by these massive temp drop spikes - resulting in the graph scale self adjusting to display these & 'otherwise 'normal temp readings are drowned and appear all as a straight line (because their variations are so small compared to these spikes).
happy to provided as anything else needed.
Is anybody else seeing this? would it be possible to look at correcting (or filtering out any significant negative values) in the sensor?
Thanks

What version of Home Assistant Core has the issue?

core-2024.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SolaX Power

Link to integration documentation on our website

https://www.home-assistant.io/integrations/solax

Diagnostics information

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @squishykid, mind taking a look at this issue as it has been labeled with an integration (solax) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of solax can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign solax Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

solax documentation
solax source
_{^{(message by IssueLinks)}}

[darmach]

I have X3-hybrid-G4. In my case it randomly drops to 0 (definitelt not true)

[LoznOz]

I have X3-hybrid-G4. In my case it randomly drops to 0 (definitely not true) !

If its helpful to you I created the work-around sensor filter which with may help

template:

• sensor:
  • name: "Filtered Solax Inverter Temperature"
    unique_id: filtered_solax_inverter_temperature
    unit_of_measurement: "°C"
    device_class: temperature
    state: >
    {% set current_temp = states('sensor.solax_inverter_temperature') | float(default=0) %}
    {% set previous_temp = states('sensor.filtered_solax_inverter_temperature') | float(default=0) %}
    {% if 0 <= current_temp <= 60 and (previous_temp == 0 or abs(current_temp - previous_temp) <= 5) %}
    {{ current_temp }}
    {% else %}
    {{ previous_temp }}
    {% endif %}
    availability: >-
    {{ states('sensor.solax_inverter_temperature') | is_number }}

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.