As I further diagnose odd ST behavior … starting with this thread… Possible physicalgraph.device.HubAction bug
I found another one today. I don’t fully know yet all the conditions that cause this but…
- Create a new custom handler. insert logging in parse and refresh methods to denote today’s date.
- change an existing device that has an existing custom handler to the new custom handler.
- Watch live logging. Notice these two things:
a. refresh method log prints today’s date.
b. parse method log doesn’t, and reflects logging of previous custom handler.
It’s as if the parse method logic is disconnected from the device. given other troubleshooting I have done in the above referenced thread, I expect it will rectify itself in 24 hours.
I will report back.
If you have any issues with custom handler’s not taking your parsing code, test whether the parse code is actually being processed, or whether it’s phantomed for 24 hours.