Adding "counts per minute" to the sensor community binding

Add-ons Bindings
1

Hi,

it would be very useful if the binding would support radiation sensors. Currently I need to transform the json answer for counts_per_minute. An example of the json answer:

[{“sampling_rate”:null,“sensordatavalues”:[{“value”:“72”,“id”:66244464531,“value_type”:“counts_per_minute”},{“value”:“30024”,“id”:66244464534,“value_type”:“hv_pulses”},{“value”:“181”,“id”:66244464537,“value_type”:“counts”},{“value”:“149985”,“id”:66244464539,“value_type”:“sample_time_ms”}],“location”:{“country”:“AT”,“longitude”:“14.17789856482”,“indoor”:0,“latitude”:“48.18064425000”,“exact_location”:1,“id”:66616,“altitude”:“294.8”},“timestamp”:“2026-03-09 16:05:25”,“sensor”:{“pin”:“19”,“id”:77506,“sensor_type”:{“name”:“Radiation Si22G”,“manufacturer”:“EcoCurious”,“id”:36}},“id”:28514541414},{“sampling_rate”:null,“sensordatavalues”:[{“value”:“66”,“id”:66244412637,“value_type”:“counts_per_minute”},{“value”:“29403”,“id”:66244412638,“value_type”:“hv_pulses”},{“value”:“168”,“id”:66244412639,“value_type”:“counts”},{“value”:“152284”,“id”:66244412640,“value_type”:“sample_time_ms”}],“location”:{“country”:“AT”,“longitude”:“14.17789856482”,“indoor”:0,“latitude”:“48.18064425000”,“exact_location”:1,“id”:66616,“altitude”:“294.8”},“timestamp”:“2026-03-09 16:02:55”,“sensor”:{“pin”:“19”,“id”:77506,“sensor_type”:{“name”:“Radiation Si22G”,“manufacturer”:“EcoCurious”,“id”:36}},“id”:28514520654}]

Many thanks

Paul

2

Hi @pkarrer,

pretty cool. I see Europe is preparing for the apokalypse :smiley:
I need this too!

Decoding your values


    "sensordatavalues":[
    {
        "value":"72",
        "id":66244464531,
        "value_type":"counts_per_minute"
    },
    {
        "value":"30024",
        "id":66244464534,
        "value_type":"hv_pulses"
    },
    {
        "value":"181",
        "id":66244464537,
        "value_type":"counts"
    },
    {
        "value":"149985"
        ,"id":66244464539,
        "value_type":"sample_time_ms"
    }

My personal decoding of this data
What I can see is counts_per_minute is counts divided by sample_time_ms.
Basically this shall result into one value. But what does this actually means? Is 72 a good or bad value?

Normally for radiation Sievert is the common measurement. Asking Gemini I would apply this conversion:

image
image1226×1102 59.9 KB

For hv_values I’m honestly clueless what it means.

3

hv_pulses is the count for clock to the high voltage generator. A drifting value can indicate a problem with the hardware.

I convert the cpm into Sievert similar to your Gemini answer. I also compare it with other stations to get alarmed if there is something happening (increasing) in the neighbourhood (Ukraine, Poland, etc)

4

Sounds good!
So for a new Radition Thing I see 2 channels

Is there also some kind categorization? Like ~30.000 is normal? 25.000 is too much drift (red/yellow flag)?
Just note I’ve no clue :smiley: . But I don’t want to report raw numbers where I don’t know the meaning behind it.

5

hv_pulses counts the current pulses to charge the high voltage condensator. If there is a leakage current on the print then this count goes up. This indicates a serious issue on the device like humidity or a fault of a component. As long as the hv_pulses is stable all is good, if it rises we need to check the device. The „normal“ amount of pulses varies by device based on component tolerances.

I hope that helps.

6

Here we go

  • Remove your current installed sensorcommunity binding
  • Install this version which contains the new radiation sensor
  • Please also check updated readme if everything is described correctly
1 Like
7

works like a charm - many thanks for that!

Best

Paul

1 Like