Customers don’t care or maybe they just called support when they are having problems. This is also a self service portal where there are handfuls of users in and out as regulars.
The users are asked to:
- Own their infrastructure
- Diagnose their own problems
- Correct their own problems
All with the goal of self monitoring. Right now, I don’t trust the bridge. I have had two bridges act “intermittently” according to support. So here I am, opening and closing doors/windows at random to make sure the system is operating (in the dead of winter no less).
If the App just gave me the last known timestamp of good communication, all that diagnosing is not required. App says it’s closed, let communication was 10 minutes ago. Good to go.
Right now, door opened not recognized. App gives me the last time it says it was opened (which is then useless because it is no longer accurate). The app says the last KNOWN signal strength (which is hugely misleading). On top of the fact that their “offline” detection obviously has some known bugs (which, tell me the last communication and I don’t care what the offline indicator says).
So, in a fully self service product, if I am spending more time proving the product is working compared to trusting the product works, then the self-service IoT strategy is a failure.
Our customers say thing same thing to us. If I have to expend manpower to prove what your product tells me is true, then the product has failed.
All I am proposing is adding information to AID in diagnosing; I am not even asking for a long term solution. And given the AWS IoT provides this easily (as well as other similar off the shelf cloud products), exposing it to the user is a non-issue.
Also, thanks for pointing that out about Lutron, I’ll know to steer clear from their product.