My RB5009UPr+S+ is updated to 7.19.1
Now the mainboard temp sensor is gone
It does not show up in /system/health print anymore
It was there as pcb temperature on V7.16.1 if I remember correctly
Please help
Hi,
v7.17
*) health - removed board-temperature on RB5009UPr+S+IN device;
Regards,
Oh no!! 
Then what’s the point that the product still advertises the removed feature on the product page?
Is there any good reason to remove it?
How is your ticket about board temp going?
Temp sensors worked fine on mine until upgraded (or version up downgrade??)
Ticket was closed with this comment:
Hello,
Unfortunately, due to a problem with the component that provided the temperature readings, we have removed this parameter from Health.
Sorry for the inconvenience.Best regards,
Very sad, the sensors gave absolute reliable reading. Have no temp since they removed the OID 
It seems like an unprofessional solution.
(It’s actually acceptable if it’s a temporary solution until fix is done)
This feature should always be available and it should have option to turn ON and turn OFF if one finds issue.
For this matter, maybe I should rethink if I should purchase anything MikroTik in the future or step away.
You could ask Mikrotik support directly if the health sensors come back or are gone forever.
I was away for quite long time.
What’s the current support channel if it’s not this forum?
Please keep us posted.
on reliability: Two RB5009UPr+S+ with 10C degrees difference, same location
Agreed, not professional to remove this, while it was a feature at purchase. They let the warranty gone, so no claims can be made.
To me, the hotter one seems like it’s uncalibrated or defect.
Or it’s from different batch that’s defected, or it has wrong NTC/PTC installed.
Why does not MikroTik just add sensor calibration or manual adjustment via the WinBox?
Because with a dodgy sensor, for 1000 units sold, there are 1000 possible errors, how do you expect Mikrotik to tell the uses to offset? Based on what?
I am quite happy that it has been removed, because it just yielded nonsense values…
Of course it would be better when it could be made correct, but for now we have CPU temperature.
I once worked on a product that had a sort of similar issue - and with a temperature sensor too. These things interface digitally, and often include internal calibration logic, and the one that we used actually ran a really small MCU inside. When there was some RF noise on the interface signals with just the right parameters, the sensor would simply lock up. Only a reset helped - but of course the reset pin was not separately controllable.
This is one of those situations, where a recall/replacement would be insane. The most one could hope for is a “$1 off” coupon for MikroTik merch, then again that’s just pathetic.
Sometimes bad things simply happen…