Red Series mmWave Firmware Changelog | VZW32-SN

The switch currently has no load on it and is only using the local motion to turn itself on an off. I was going to use it as a sensor for the room it is in but I sit just out of range, so it is constantly detecting then not detecting me. So there were no changes being made or commands sent to it when it locked up. That is why I think it may be a memory leak that is probably related to motion detection.

I have not made any changes to the switch after air gaping it and can leave it untouched for a few weeks to see if it happens again.

@cfoos1 I’ll open an issue with the engineer and we can keep an eye on it. Let me know how your testing goes.

Will do. May take a while but I’ll leave it un-touched so we know it was not something else that caused it.

I configured some automation based on double/triple up and down. It is becoming very obvious that the switch is getting more and more delayed every day. When I double tap on the mmwave switch, it can take at least 5-10 seconds for the automation to start. Something that is instantly on my other switches and seems to be isolated to the mmwave switches only.

Let me know if you need me to pull any specific information.

I’d love to buy like 20 more of these for my home if you can get them working.