QuickApp - Radiation Monitor ​☢️​

[SmartHomeEddy 814]

The Radiation Monitor collects radiation levels from all available stations around the world and shows 5 nearest stations to your location and one station with highest current readings and one station with the highest 24 hour average readings. The QuickApp uses the location (latitude and ongitude) of your Homecenter to measure the distance to the stations and to get the nearest stations. The bearings in degrees from your location to the stations is shown. Next to the measurements, the five nearest reactors are shown. The languages English, French, Polish and Duth are supported. 

 

Thanks to @Sankotronic for his work for his HC2 Virtual Device version and ideas. 

 

Please login or register to see this attachment.

 

The main device shows the nearest measurement μSv/h. There are Child Devices for:

• Nearest sensor 24h average μSv/h
• 2nd, 3rd, 4th, 5th nearest sensor measurement with the 24 average in the log text
• Nearest maximum measurement
• Nearest maximum 24h average measurement

 

The nearest five reactors are retrieved once at startup of the QuickApp or at the next interval if you click on the button. 

Radioactive@Home is a Polish science project using the distributed computing capabilities of the BOINC platform. The main goal of the project is to create a free and continuously updated map of radiation levels available for everyone, by gathering information about gamma radiation using sensors connected to the computers of volunteers willing to participate in the project. Project is completely non-commercial, participating will be free of charge (excluding cost of detector) and the software will be licensed under the GNU General Public License (GPL).

 

μSv/h: The sievert (symbol: Sv) is a unit in the International System of Units (SI) intended to represent the stochastic health risk of ionizing radiation.

 

In land navigation, a 'bearing' is ordinarily calculated in a clockwise direction starting from a reference direction of 0° and increasing to 359.9 degrees. Measured in this way, a bearing is referred to as an azimuth by the US Army but not by armies in other English speaking nations, which use the term bearing.

 

The human population is continuously exposed to ionizing radiation from several natural sources (cosmic and terrestrial contributions). For most individuals, exposure to natural sources exceeds that from all man-made (artificial) sources combined. The man-made sources arise from peaceful (e.g. medical use, energy generation, and associated fuel cycle facilities, radioisotope production, waste management) and military purposes (nuclear tests and their fallout or radioactive release, nuclear explosions).

 

Radiation levels: 
Green: Radiation up to 0.3 μSv/h
Yellow: Radiation between 0.3 and 0.8 μSv/h 
Red: Radiation above 0.8 μSv/h

 

1.14 µSv/h - Shelter population
5.7 µSv/h - Evacuation of population
11.4 µSv/h - Issue Iodine tablets
0.114 µSv/h - Max daily dose == 1 mSv/year

 

Reverse Geocoding by Nominatim
Reverse geocoding generates an address from a latitude and longitude. The reverse geocoding API does not exactly compute the address for the coordinate it receives. It works by finding the closest suitable OSM object and returning its address information. This may occasionally lead to unexpected results. 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this image.

/monthly_2022_11/radiation-monitor-1c.png.762783dcc152d2602bb666ee45869ef9.png" />

 

QuickApp code logics:

• onInit() Initialise the QuickApp
• getQuickAppVariables() Get all Quickapp Variables or create them
• createVariables() Setup the global variables
• setupChildDevices() -- Setup all child devices
• loadMap() Get the webpage from

  Please login or register to see this link.

  (This is the main loop of the QuickApp)
• extractData() Extract the data from the webpage source-code
• geoDistance() Calculate the distance from the HC3 (QuickApp variables) lat/lon to the sensors lat/lon
• geoBearing() Calculate the bearing from the HC3 (QuickApp variables) lat/lon to the sensors lat/lon
• Check for the values to give the right dot colours for the sample and average measurements
• Store the values of all sensors in a table and sort the table on distance
• Run through the table to get the maximum sample and maximum average measurements. If there are more than one, get the one that is the nearest-by
• updateIcon() Set the icon (colour) based on the sensor measurement
• getCity() Get the cities and countries for the seven selected sensors from

  Please login or register to see this link.

  and store them in a table
• updateLabels() Update the labels
• updateProperties() Update the properties
• updateChildDevices() Update the Child Devices
• Return to the main loop loadMap()

 

Links:

• Radioactive@Home Map:

  Please login or register to see this link.

• Status servers:

  Please login or register to see this link.

• Reverse geocoding:

  Please login or register to see this link.

  licence:Data © OpenStreetMap contributors, ODbL 1.0.

  Please login or register to see this link.

• Nominatim Usage Policy (aka Geocoding Policy):

  Please login or register to see this link.

Variables (mandatory and created automatically): 

• latitude = Latitude of your location (Default is the latitude of your HC3)
• longitude = Longitude of your location (Default is the longitude of your HC3)
• language = Preferred language (default = en) (supported languages are English (en), French (fr), Polish (pl), Croatian (hr) and Dutch (nl))
• interval = Interval in seconds to get the data from the Radioactive@Home website
• debugLevel = Number (1=some, 2=few, 3=most, 4=all) (default = 1, debugLevel 4 is only recommended for solving difficult issues)
• icon_refresh = User defined icon number for refresh status
• icon_green = User defined icon number for values less than 0.3 μSv/h
• icon_yellow = User defined icon number for values between 0.3 and 0.8 μSv/h 
• icon_red = User defined icon number for values greater than 0.8 μSv/h
• icon_error = User defined icon number in case of an error gettng the data

 

 

Version 1.4 (6th February 2024)

• Added extra check for an empty response in the address from Geocity (thanks to @Sankotronic from the Fibaro forum)

Version 1.3 (17th July 2023)

• Added extra check for the right response from Geocity (in case of response {"error":"Unable to geocode"})

Version 1.2 (11th January 2023)

• Added support for Croatian language thanks to @Sankotronic

Version 1.1 (9th January 2023)

• Changed handling of negative values for dots and icons: if tonumber(num) >= 0 and tonumber(num) <= 0.3 then 
• Added a better translation for French (thanks to @fredokl)

Version 1.0 (5th November 2022)

• Added the nearest five reactors to the labels with distance and bearing
• Added a button to refresh the list of (five nearest) reactors
• Added a warning at startup if the latitude or longitude differs from the setup of your HC3
• Replaced the creation of the dots 🟢🟡🔴 to the labels, so no longer for all sensors
• Added some extra notifications to the labels in case the website is down
• Extended the http timeout a bit, to give the reverse geocoding some more time to respond
• Added translations for new functions

Version 0.5 (29th October 2022)

• Added translation to the Reverse API geocoding response (city and country)
• Changed calculation of the bearings only for the 7 selected sensors, not all sensors
• Optimized the code and added more structure by using multi file code (main, childs and i18n)

Version 0.4 (22nd October 2022)

• Added six Child devices for the nearest sensor 24h average, 2nd, 3rd, 4th, 5th nearest sensor sample, the nearest sensor maximum sample and the nearest sensor maximum 24h average
• Added icons based on sensor measurements to all Child Devices
• Added translations for the labels and properties from English to French, Polish and Dutch. (Thanks to @ppeterr and @fredokl for help with the translation)
• Limited the details of the response of the Reverse Geocoding with zoom=10 (address detail = city)

Version 0.3 (16th October 2022)

• Added the City and Country also for worst sample and worst average sensors
• Added all debug information and set the debug levels
• Optimised the code

Version 0.2 (15th October 2022)

• Added the City and Country for all 5 sensors, not only the first one

Version 0.1 (15th October 2022)

• Initial version

 

Download the QuickApp here (download the file and un-zip):

Please login or register to see this link.

or from the Fibaro Marketplace:

Please login or register to see this link.

How to install: 

1. Open the Configuration Interface
2. Go to Settings > Devices
3. Click  +
4. Choose Other Device
5. Choose Upload File
6. Choose file from your computer with .fqa

 

Icons thanks to @Sankotronic

 

 

Edited February 6 by SmartHomeEddy

[fredokl 10]

Hello. I understand your approach. It's true that if the QA works, why tweak it? The explanation of how you have just done is very interesting for those, like me, who are not real coders. I try to understand the code and I admit that, sometimes (even often), I struggle because it's not easy. To train and/or do small unpretentious QA, I use a lot of already existing codes and I adapt it according to my needs. In any case, thank you for taking our comments into account to improve the QA.

[Merlin 2]

Hi,

 

I can’t get the QA to use the icons, I have added the icons, but don’t know how to get the QA to display them automatically.

 

I think I must have missed a step.

 

Also when I installed it; the QA, didn’t automatically use my HC location of set the Language, these issues I have sorted by setting the variables.

 

Help greatly appreciated.

 

 

 

 

[SmartHomeEddy 814]

15 minutes ago, Merlin said:

I can’t get the QA to use the icons, I have added the icons, but don’t know how to get the QA to display them automatically.

 

If you have uploaded the icons, you can do a "right-mouse-click" and "save picture as" (not actually saving the picture) on the icon to see the number. That number you have to fill in with the corresponding quickapp variable. 

[SmartHomeEddy 814]

23 minutes ago, Merlin said:

Also when I installed it; the QA, didn’t automatically use my HC location of set the Language, these issues I have sorted by setting the variables.

 

In de .fqa file the quickapp variables are already there. But they are not the lat/lon from your HC3. I don't know how to prevent that. I will add a warning in the debug logging, if the HC3 lat/lon are different with the quickapp variables. 

 

(btw if you delete the quickapp variables, they will be generated with the right default values)

 

 

Edited October 29, 2022 by SmartHomeEddy

[Merlin 2]

Hi,

 

Is there a way to make this device appear in the list of devices available in the alarm panel?

[SmartHomeEddy 814]

Not that I know.

 

You want it to notify?

[Merlin 2]

Yes, I’d like to create an alarm and notification if levels reach a certain point.

[SmartHomeEddy 814]

You could create a simple blockscene to check the measurement and give a warning when between 0.3-0.8 and a different warning above 0.8. 

[Merlin 2]

That’s a good work around, thank you.

 

FYI: I do have another QA for my Davis weather station that @tinman created and it has a device=rain detected and this device appears in the alarm panel. I just don’t know how somethings do appear and others don’t.

 

Thanks again.

[SmartHomeEddy 814]

It will depend on the device type if it will show up in the alarm panel. 

[SmartHomeEddy 814]

Busy in testing the new version. I think that will be the final version. 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this image.

/monthly_2022_10/258233399_Schermafbeelding2022-10-30om15_52_57.png.7afb63b18e2ceead8397cdc2eb2a7073.png" />

 

 

 

 

 

Edited October 30, 2022 by SmartHomeEddy

[SmartHomeEddy 814]

The 1.0 version is available for download.

 

Compared to the previous version, these are the differences:

• Added the nearest five reactors to the labels with distance and bearing
• Added a button to refresh the list of (five nearest) reactors
• Added a warning at startup if the latitude or longitude differs from the setup of your HC3
• Replaced the creation of the dots ??? to the labels, so no longer for all sensors
• Added some extra notifications to the labels in case the website is down
• Extended the http timeout a bit, to give the reverse geocoding some more time to respond
• Added translations for new functions
• Added translation to the Reverse API geocoding response (city and country)
• Changed calculation of the bearings only for the 7 selected sensors, not all sensors
• Optimised the code and added more structure by using multi file code (main, childs and i18n)

Because there are many changes, please use the .fqa file to upload to a new version (and delete the old QuickApp).

Also remember to change the longitude and latitude settings, the numbers of your icons and prefered language. 

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this image.

/monthly_2022_11/radiation-monitor-1c.png.762783dcc152d2602bb666ee45869ef9.png" />

 

 

Edited November 5, 2022 by SmartHomeEddy

[ppeterr 202]

It works great, good job!

 

What I do wonder, and that has nothing to do with your quickapp. When I look at the positions of the sensors, they are all quite far away from the reactors. The Netherlands does not even have its own sensor. I would have placed one near Borsele

[SmartHomeEddy 814]

There is a sensor near Utrecht, but it is offline for two weeks now. I also looked what is needed to build a sensor setup, but haven’t figured that one out. 

[ppeterr 202]

2 minutes ago, SmartHomeEddy said:

There is a sensor near Utrecht, but it is offline for two weeks now. I also looked what is needed to build a sensor setup, but haven’t figured that one out. 

 

Seems the website for radioactive@home is outdated, but 10 years ago much more

active. They sold a kit for 25 euro  

[SmartHomeEddy 814]

 

There is a different map from the EU, with more sensors. But I can’t find a way to get the measurement from that site. I asked if they have an API, the don’t. And the way the site build up, is different. 
 

Please login or register to see this link.

 

 

1 minute ago, ppeterr said:

Seems the website for radioactive@home is outdated, but 10 years ago much more

active. They sold a kit for 25 euro  

indeed, it looks like that. But the site still works and is maintained. But the kit I can’t find anywhere. 

[ppeterr 202]

2 minutes ago, SmartHomeEddy said:

 

There is a different map from the EU, with more sensors. But I can’t find a way to get the measurement from that site. I asked if they have an API, the don’t. And the way the site build up, is different. 
 

Please login or register to see this link.

 

 

 

Ah, 164 sensors in the netherlands.

[SmartHomeEddy 814]

Please login or register to see this attachment.

 

 

a lot of sensors ?

 

But how to get them from the web page source?

 

 

 

The site also has a subscription feature, with RSS. But can’t get that to works either. 
 

 

 

Edited November 6, 2022 by SmartHomeEddy

[ppeterr 202]

Well, there is a RSS feed for registered users. But then again, maybe a little overkill

 

Your app functions wonderfull.

[SmartHomeEddy 814]

1 minute ago, ppeterr said:

Well, there is a RSS feed for registered users.

Everone can register, I have, but can’t get the RSS feed to work. If I could only get the measurements from that site, it could turn it into (another) quickapp.