errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object

[disruptivepatternmaterial]

Describe the bug

dev:2272021-06-29 07:50:46.134 errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 404 (setAssociations) dev:2272021-06-29 07:50:21.060 debugSetting param 113, size 4, value 3600 dev:2272021-06-29 07:50:21.057 debugSetting param 112, size 4, value 3600 dev:2272021-06-29 07:50:21.054 debugSetting param 111, size 4, value 60 dev:2272021-06-29 07:50:21.051 debugSetting param 103, size 4, value 0 dev:2272021-06-29 07:50:21.048 debugSetting param 102, size 4, value 0 dev:2272021-06-29 07:50:21.046 debugSetting param 101, size 4, value 454761279 dev:2272021-06-29 07:50:21.043 debugSetting param 10, size 1, value 10 dev:2272021-06-29 07:50:21.040 debugSetting param 9, size 1, value 10 dev:2272021-06-29 07:50:21.037 debugSetting param 8, size 1, value 10 dev:2272021-06-29 07:50:21.034 debugSetting param 6, size 2, value 50 dev:2272021-06-29 07:50:21.032 debugSetting param 5, size 2, value 50 dev:2272021-06-29 07:50:21.029 debugSetting param 4, size 2, value 50 dev:2272021-06-29 07:50:21.026 debugSetting param 2, size 1, value 1 dev:2272021-06-29 07:50:21.022 debugSetting param 13, size 1, value 0 dev:2272021-06-29 07:50:21.018 debugSetting param 3, size 1, value 0 dev:2272021-06-29 07:50:21.015 debugGenerating configuration command list

The device stops working (not sure if it is the device or the hub)

To Reproduce Change settings, or click "configure"

Expected behavior No error and continue to report.

Hub: Hubitat Elevation® Platform Version 2.2.7.128 Hardware Version Rev C-7 Device - HEM firmware: 1.37, 2 phase, USA

Additional context I tried commenting out that code, since I am not sure what it is doing, and I see the same error on 413 and 422

[disruptivepatternmaterial]

Never seems to enter this

def zwaveEvent(hubitat.zwave.commands.associationv2.AssociationReport cmd) {
    logTrace 'hubitat.zwave.commands.associationv2.AssociationReport'
    cmd.properties.each{ logTrace "${it.key} => ${it.value}" }
    if (!state.associatedNodes) {
        state.associatedNodes = []
    }
    state.associatedNodes[cmd.groupingIdentifier] = cmd.nodeId
    logTrace "associationv2 done"
}

so state.associatedNodes is never created and this causes the error at line 404, but why would this happen in my setup and not others...so curious.

[viertaxa]

Interesting. I'm not actively using Hubitat at the moment, but I can load up the hub and see if the API changed or something. Thanks for reporting!

[disruptivepatternmaterial]

thanks, I've been trying to figure this one out (I can and do write code all day) but the APIs are so specific/unfamiliar, so it is slow going for me.

what are you using to track your energy? I'd be happy to ditch my hubitat (I dont find it to work very well) and I only bought it to use the HEM to track my solar panel system output/consumption. If there were a wifi or even wired ethernet device that gave the same data as the HEM I'd buy it in a second. I looked at sense, but it has no true APIs and people dont give it good ratings. I have this entire home monitoring data board system that has been SO helpful and finding issues in the house and I dont want to ditch it!