steadramon / espgeiger Goto Github PK

It would be great if there is a possibility to set up the GPIO pin(s) for input impulses and for output impulses (testing mode) in teh web UI interface.

First nice job!
It would be nice to have the possible switch between 24h and am/pm in the graph.
My Access Point SSID is not readable in menu Info,
It would be nice if switch/display of summertime/wintertime is automated.
It would also be nice if current date/time is included in ESPGeiger-XXXXXX/tele/status
Have you seen the dial presentation of https://github.com/mkgeiger/geiger-counter-iot it would be nice if that could be included.

What's the best way to disable all output other than Serial? I see a SERIALOUT flag but nothing for disabling MQTT, Thingspeak, etc.

Ello there!

I've been using ESPGeiger on a cheap BR-6 Geiger-Counter for the past week,
But i've noticed an issue with the home-assistant MQTT Stuff

I have it send its data over to my HASS, which works fine, sometimes for multiple days, sometimes only for a few hours
it then just, stops (in HASS) and doesnt report anything, it even goes into "Unavailable"

the notable thing is that when i connect directly to the MQTT server, over the same network, i can see the ESP reporting its data just fine, without any issues

To get it back up and running, without rebooting the ESP, i go to the settings page, and simply press "SAVE"
This triggers a new "Auto-discovery" cycle, and fixes the connection again

I'm unsure how to debug this further, so i hope this helps out alot

Tiny things i tried

Stable 5v Input to the ESPBoard (Using its own 3.3v regulator)
Stable 3.3v Input
Different networks (Never know!)
Different usernames (ofc shouldnt matter, but still worth a try)
Reflashing ESP from clear

Just got a cajoe esp32-gc board and the image v0.6.1 is not working in PCNT. However NO_PCNT is working.

Since I never used espgeiger before I don't know if it worked in releases before 0.6.1

Waiting for you to upload the pcb file :)

I am trying to setup CAJOE IOT-GM-v1.1 counter.
Pulses from counter are connected to the ESP32 GPIO26.

My setup:
platformio.ini: default_envs = esp32oled_pulse
counter.h: #define GEIGER_RXPIN 26

After the start, the GPIO stays HIGH (3.3V). Because of that ESP can not detect pulses from detector.

Schematic here

Photos of device

How can I configure the code so GPIO defined as INPUT stays LOW?

It would be very handy to be able to configure the logging interval for external services such as MQTT and radmon.org, and possibly the others.

I would like the ability to send data to MQTT every 10 seconds and some radmon.org users/stations submit readings at intervals other than 1 minute. The minimum submission interval for radmon.org is 30 seconds as any submissions sooner than 30 seconds are dropped by radmon core.

I'm not sure about the other services (HA, Thingspeak and GMC) as I have no working knowledge of them, and a configurable interval may or may not be useful to them.

I also understand that if just one submission timer is used in ESPGeiger then implementing this would be quite a job.

Cheers

(Simomax @ radmon.org)

hi, I've just installed ESPGeiger on my ESP8266 connected to a J305B tube.
I can't get the OLED display to work.
It worked perfectly with my old sketch, using the address 0x3c (it seems to me that you're using this very same address in your config file).
do you have any suggestion?
my sketch uses this command to initialize the display:
display.begin(SSD1306_SWITCHCAPVCC, 0x3c)
thank you.

When the ESP8266 looses connection to the MQTT broker it causes the MCU to lockup/lag and then reboot after what appears to be an arbitrary length of time. With this the status web page goes very slow (see timestamps on the chart of the attached image.) Similar can be seen with the OLED and red LED on the ESPGeiger HW. Every so often the OLED will update and the red LED will light for a longer time than the regular count blink. The log window on the status web page seems unaffected.

This affects v0.5.3 and v0.5.4. Attached is a log text file copied from the status page log window and a screen grab of the status web page. v0.5.3 was in use at first, then updated to v0.5.4.

Hardware/software:
ESPGeiger HW (v0.5.3/064bca6 & v0.5.4/3066e12
Mosquitto MQTT Broker, running on Windows 10 Pro

Steps to reproduce:

1. Setup/configure an MQTT broker (Mosquitto in my case)
2. Configure ESPGeiger to use the MQTT server
3. Observe normal operation
4. Break the connection to the MQTT broker (in my case I stopped the Mosqitto service on Windows)
5. Observe the ESPGeiger slow down/lockup and after some time (around 10-15 minutes in my tests) the unit will reboot

If the MQTT broker connection is restored normal operation resumes, however if the connection is not restored the MCU will reboot. The first reboot occurred around 17 minutes after the connection was lost. After restoring the connection normal operation resumed. I then updated to v0.5.4. Observed normal operation and then broke the MQTT connection again. The reboot occurred after 13 minutes and then again 12 minutes later. This can be seen in the log file attached.

Please let me know if you would like any further information or testing.

Thanks.

ESPGeiger-4e4aee.txt

Hello!

First of all I want to say congrats on the amazing work you've done on this project. It is really complete and has awesome features. That is way I really want to use it to power my geiger counter.

The issue I'm experiencing is the display not clearing.

I am compiling my own version due to different pins used for the I2C interface. I've tested the screen with the Adafruit_SSD1306 and the screen is working as expected.

Would you have any idea what might be the issue and how to resolve it?

When viewing the status page the time that is shown in the CPM chart is a different timezone to the time shown in the log window.

I suspect the chart time is using my local timezone (currently BST) and the log time is UTC.

Please see attached screen grab.

Thanks