Open earlthesquirrel opened 1 year ago
I haven't made any changes to this driver since posting it.
On Thu, Apr 20, 2023, 12:49 earlthesquirrel @.***> wrote:
I'm trying to find out if there are any outstanding updates to the driver.
See: https://community.hubitat.com/t/problem-with-quirky-overflow-driver-with-latest-homekit-add/117540 for my existing logs, but basically I'm getting a null pointer exception in the Hubitat log coming from the Overflow devices when they interact with the Homekit app (that's the best that I can debug it)
dev:4192023-04-10 07:18:54.364 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) dev:4192023-04-10 07:18:53.376 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) dev:4192023-04-10 07:18:52.911 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) dev:4192023-04-10 07:18:51.875 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) sys:12023-04-10 07:18:51.134 PMinfoZigbee Discovery Stopped dev:4192023-04-10 07:18:50.805 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) dev:4192023-04-10 07:18:50.395 PMerrorjava.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse) sys:12023-04-10 07:18:50.247 PMinfoCreated Zigbee Device Quirky Moisture Sensor sys:12023-04-10 07:18:48.798 PMinfoInitializing Zigbee Device 7CE5240000098FD5, 3AD7 sys:12023-04-10 07:18:45.099 PMinfoZigbee Discovery Running
— Reply to this email directly, view it on GitHub https://github.com/dbgalur/dbgalur-hubitat/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/APWLCKPZZ7GMSYPGDVYF2TTXCGHLFANCNFSM6AAAAAAXF6SVTY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
So, do you still use it in the current Hubitat? Is anyone maintaining it?
I still use it. Anyone should feel free to maintain it :)
On Thu, Apr 20, 2023 at 2:48 PM earlthesquirrel @.***> wrote:
So, do you still use it in the current Hubitat? Is anyone maintaining it?
— Reply to this email directly, view it on GitHub https://github.com/dbgalur/dbgalur-hubitat/issues/1#issuecomment-1516985091, or unsubscribe https://github.com/notifications/unsubscribe-auth/APWLCKJLEMDJ43QCGZWN3I3XCGVKDANCNFSM6AAAAAAXF6SVTY . You are receiving this because you commented.Message ID: @.***>
Have you used it with the Homekit app?
I've got an "test" C-7 hub to try to debug this stuff. I've onboarded one Overflow and then enabled the Homekit app. What the error I'm getting is : java.lang.NullPointerException: Cannot get property 'profileId' on null object on line 79 (method parse)
So, if I'm interpreting this correctly, it's the bold line below, which would be that the "cluster" object is null. I'm not a groovy expert, but reviewing the code, I don't see where the "cluster" is set.
private boolean shouldProcessMessage(descMap) { // 0x0B is default response indicating message got through // 0x07 is bind message boolean ignoredMessage = cluster.profileId != 0x0104 || cluster.command == 0x0B || cluster.command == 0x07 || (cluster.data.size() > 0 && cluster.data.first() == 0x3e) return !ignoredMessage }
Any ideas?
I would love to get these working but I don't understand how the cluster object could be null. Any pointers on how I might be able to debug this? This is my first time working on a plugin like this....
Also, are you running the latest Hubitat code on your devices? And are they C-7's or C-8's? (yes, it's been a bit since I originally posted this issue... but I've finally got some time to work on this project :-) )
I'm trying to find out if there are any outstanding updates to the driver.
See: https://community.hubitat.com/t/problem-with-quirky-overflow-driver-with-latest-homekit-add/117540 for my existing logs, but basically I'm getting a null pointer exception in the Hubitat log coming from the Overflow devices when they interact with the Homekit app (that's the best that I can debug it)