we are looking into the firmware changes log. to see if firmware might be causing any issues.
what’s the pulse duration ?
Thanks
Hi @Bhaskar , I believe the pulse width is at minimum 50 msec but the meter installer might have increased it to 100 msec for us. I don’t have the exact information at the moment.
Let me know what you find.
Hi @Bhaskar any updates on this? Should we send the sensors back and swap them with a 2-Channel? Thank You
The V6 firmware supports debunce time ( minimum pulse). change this value to 50msec
The command this this 7E 00 14 10 00 00 00 00 00 00 00 FF FF FF FE 00 00 F4 42 00 00 02 32 8A
if you can use node red then use that to set it.
The default value is 30msec. so if the meter is sending at 50se,c or 100msec it should read it.
Hi Bhaskar, OK we can attempt this. Do you have any instructions or videos on how to set this via node red? Thank You.
Right now its on node red test branch, we should have it live tomorrow or early next week.
This issue was fixed by reducing the debounce time.
Correct, @Bhaskar and team worked quickly to update the firmware and allow us to modfiy the debounce rate, which solved the issue instantly! Thank You!!