More for my own purpose here, I want to make a note I can refer back to for future emonhub development.
Although not the case here, there could be a scenario where the node definition tries to scale the value passed through emonhub. In this instance we do not want emonhub to crash because it cannot multiply “infinity” by what ever scale is set by the user.
What does happen in that scenario will need to comply with emonhub’s global policy on handling errors without interfering with the data, perhaps we will just not do the math if it’s not possible, leaving the source data as it is. (eg infinity is infinity whether it’s multiplied by 0.01 or not).
But as emoncms still won’t accept that and emonhub needs to be robust, perhaps we will end up omitting a result (null) so the rest of that frame is accepted by emoncms, this depends on whether emoncms can handle the invalid data.
Ideally any emoncms specific casting of data should be done in the emoncms interfacer/reporter, but that adds additional processing.