You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an idea for a new kind of object - not sure if a helper or some other class. It would let you specify an existing entity. It would then enumerate all the entity's properties, and build a UI that let's you specify calibration math for each, perhaps optionally offering separate functions for read and write.
You could then enter whatever simple math, eg addition, multiplication, to correct the values received it sent to the actual device, to account for inaccuracies or other desired offsets.
I would use this to normalize thermometers, barometric pressure sensors; to implement thermostat target offsets, and probably other cases where you want to tweak a value before consuming or displaying it.
You would then use the CalClone version of the sensor as usual, with all the freebies that come with it.
This could also be a calibration "shim" object that works the same way, but it's optionally hooked by native entities to modify the I/O - but no doubt that's a deeper problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is an idea for a new kind of object - not sure if a helper or some other class. It would let you specify an existing entity. It would then enumerate all the entity's properties, and build a UI that let's you specify calibration math for each, perhaps optionally offering separate functions for read and write.
You could then enter whatever simple math, eg addition, multiplication, to correct the values received it sent to the actual device, to account for inaccuracies or other desired offsets.
I would use this to normalize thermometers, barometric pressure sensors; to implement thermostat target offsets, and probably other cases where you want to tweak a value before consuming or displaying it.
You would then use the CalClone version of the sensor as usual, with all the freebies that come with it.
This could also be a calibration "shim" object that works the same way, but it's optionally hooked by native entities to modify the I/O - but no doubt that's a deeper problem.
Beta Was this translation helpful? Give feedback.
All reactions