The case 3d-model for the GGreg20_V3 module for personal use
The company IoT-devices, LLC has shared the case a 3D model for the GGreg20_V3 module for personal use by anyone. You can order such a case as an option together…
The company IoT-devices, LLC has shared the case a 3D model for the GGreg20_V3 module for personal use by anyone. You can order such a case as an option together…
Exemption from liability The company IoT-devices, LLC does not bear any responsibility for possible direct or indirect damage or costs that may be incurred by anyone in the process of…
If you have a controller with a GGreg20_V3 radiation detector module that periodically sends data to the ThingSpeak server, you can also easily connect it to your Home Assistant server…
Indeed, why not add such a convenient interface to the module? Here is our next article where we discuss the advantages and disadvantages of equipping the GGreg20_V3 ionizing radiation detector…
Kyiv. Ukraine. The IoT-devices LLC team has developed and made available on GitHub an example in Lua for its GGreg20_V3 product, which can be used for ESP8266 and ESP32 controllers…
може сховати лістинг у акордеон?
####### ggreg20_esp8266_esphome.yaml #####
esphome:
name: esphome_node1 # Controller Unique Name
platform: ESP8266 # Platform type you have to select when creating new yaml-config in ESP Home
board: nodemcuv2 # Controller type you have to select when creating new yaml-config in ESP Home
wifi:
ssid: "YourWiFiSSID"
password: "SSIDPassword"
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esphome Node1 Fallback Hotspot"
password: "Cpxg9hRIBU7M"
captive_portal:
# Enable logging
logger:
# Enable Home Assistant API
api:
password: "APIpassword"
ota:
password: "OTApassword"
# Just embedded test D3 (GPIO0) button on every ESP8266 Devboard
# You can press D3 button several times to simulate incoming GGreg pulses
binary_sensor:
- platform: gpio
name: "D3 Input Button"
pin:
number: 0
inverted: True
mode: INPUT_PULLUP
# Here we calc and include to the firmware a power and doze values of ionizing radiation as sensor outputs
sensor:
- platform: pulse_counter
pin: D3
unit_of_measurement: 'mkSv/Hour'
name: 'Ionizing Radiation Power'
count_mode:
rising_edge: DISABLE
falling_edge: INCREMENT
update_interval: 60s
accuracy_decimals: 3
id: my_doze_meter
filters:
- sliding_window_moving_average: # 5-minutes moving average (MA5) here
window_size: 5
send_every: 5
- multiply: 0.0054 # SBM20 tube conversion factor of pulses into mkSv/Hour
- platform: integration
name: "Total Ionizing Radiation Doze"
unit_of_measurement: "mkSv"
sensor: my_doze_meter # link entity id to the pulse_counter values above
icon: "mdi:radioactive"
accuracy_decimals: 5
time_unit: min # integrate values every next minute
filters:
- multiply: 0.00009 # obtained doze (from mkSv/hour into mkSv/minute) conversion factor: 0.0054 / 60 minutes = 0.00009; so pulses * 0.00009 = doze every next minute, mkSv.
####### END of ggreg20_esp8266_esphome.yaml #####