Let's Control It

Hi,
I've got a question about the implementation of the pulse counter.

I wanted to use it to read in an analog energy meter with ferraris disc.
My sensor is working fine and the total count value seems to be correct.

The part which seems off is the time. The disc takes at least 10 sec or more to turn arround once. But sometimes I get readings with 400 ms, which is just not possible.
I've set the delay to 60 and also tried 600 seconds. Is the time set to 0 when the data is pushed to the controller? Debounce should be fine too, I also have led's on the sensor to show the state, and that part seems reliable.

My understanding was, that time displays the time in ms between the last count? Is that right? Or is it between the last two counts? There has to be some error, and the reading is sent when it doesn't display a full circle.

Screenshot showing time differences with a 3 minute period (delay 300 in esp)


ESP Info:

Another question??

Sometimes the web interface does not respond. As it seems offline or disconnected (ping not working too).
BUT, (I use the FHEM HTTP controller), fhem shows me the device is present and I get readings. WiFi signal is good to. I installed an access point in the next room.

Yep, sometimes the unit is busy doing stuff and doesn't "hear" the request. This is something we're improving continuously but if you have a lot of devices rolling on the unit it will be more likely to miss these request. If this is the case you might want to rethink how the unit is built and perhaps disable some devices prior to accessing the unit over the web interface.

Ah, ok. This will explain that behavior. Regards the devices, I had this problem even with no devices configured. Network access is only via fhem. And sometimes http GUI when I want to look something up.

anyone?