Brandon Blake

I had a similar issue, which I could fix by commenting out the following lines in `indicator.lua`: ``` 35 if args.skipvpncheck == nil or args.skiproutes or args.skipcmdline then 36 args.skipvpncheck...

> Is this going anywhere? I shelved my own pulse meter due to not being able to run deep sleep in September, then came across this last month! Pretty keen...

@zane-lazare I'm not sure that this is what's going wrong, and I'll try replicating with the external component system, but I'm sorry to say this component won't work with the...

@lboue looks like I need to add S3 specific sdkconfig options to turn on the ULP Coprocessor (CONFIG_ESP32S3_ULP_COPROC_ENABLE). I don't suppose you have any insight into why S3 is special?...

@zane-lazare Actually, the larger restriction will be the run-counter, which is also a uint16_t. So the max time between reads would be approximately sleep_duration * 65535. At the default 20ms...

@lboue I've pushed additional sdkconfig parameters and a unit test that appear to test and remedy the failure when building for an ESP32-S3. Please pull and try again at your...

@zane-lazare I have updated the documentation to address maximum deep sleep time. Please let me know if it is sufficiently clear: https://deploy-preview-4307--esphome.netlify.app/components/sensor/pulse_counter_ulp Out of curiosity, is the limit problematic for...

@zane-lazare I haven't had a chance to try to replicate but I should be able to in the next couple of days. If you have a chance in the meantime,...

@michaelt88 it sends a rate rather than a total count, but otherwise that's correct, and your yaml looks fine. What output are you seeing?

@michaelt88 I have successfully replicated your issue. I was not seeing that behaviour before as I have been using "fast_connect" on the wifi configuration, which seems to set-up fast enough...