I bought a bunch of z-wave energy monitoring outlets for prime day and 2 of them (1 mostly) keep giving bad kWh readings according to the energy dashboard. (The watts are correct, its just the kWh)
I’ve been fixing these over and over using the developer tools and sqllite but I would like a more permanent solution.
Is there some way to fix this device or do I need to exchange it?
A couple of them failed to include with S2 but now that I think of it, this device was one of them. Didn’t even think of that. I’ll exclude and re-include.
Side Note: I never know why that happens… some devices will just never ask for the pin and just join saying “failed to include securely”
Insecure messages can be corrupted, but still pass the simple checksum. This is often apparent in energy sensor values, for some reason. S2 doesn’t have this problem because of the encryption being used.
The S2 security bootstrapping requires a lot of back-and-forth messaging between the device and controller. If there are network issues that cause any kind of timeouts or errors (e.g. device is close to out of range, bad routing, etc), the secure inclusion must be aborted and the device included insecurely.
A off topic question: can 1 device be paired secure and rest not? I have neo coolcam wall switches and give some high negative values. Maybe this will solved when try to unpaid and pair again secure also…
You can pair devices with security or without, however you like, mixed or not. Not every device even supports security. If you plan to use group association to let devices talk to each other, those need to be on the same security level.
If you’re talking about a certain infamous Neo Coolcam device, those are just plain broken. Doubtful you can fix it with secure inclusion as it doesn’t appear to be an RF corruption problem. You can find the numerous issues regarding that device on all the HA, OZW and Z-Wave JS GitHub projects.