Closed kaikreuzer closed 7 years ago
I will take a look. It seems to happen when initializing z-wave things. As you said it would be interesting to know in which cases the resolv fails.
According to this comment, it is most likely due to an invalid thing type definition (having channels that are of a non-declared type). So even if it is an error situation, we should harden the code here and not throw an NPE.
@kaikreuzer Do you think the root cause of this issue is the same root cause that's causing the REST API calls to fail as described here.
@mhilbush Yes, very likely as it seems that the REST response simply states that an unexpected NPE has happened.
I vote for a "critical bug" label because since #1024 openHAB is not fully usable anymore:
https://community.openhab.org/t/bug-items-category-missing-paperui-error-500-on-build-1029-on-openhabian/33824 https://community.openhab.org/t/oh-2-2-0-snapshots-1025-1028-zwave-npe/33711/40
To be closed, my PR fixing it was merged today.
my PR fixing it was merged today.
Thx @lolodomo (and all others) for your hard work, appreciate that.
FTR, the latest openHAB distro 1030 includes this fix.
An NPE has been reported here:
It looks to me as if no channel type can be resolved, which leads to the NPE. @lolodomo Should we add a safe-guard here? I am not sure, in which situations we can fail to resolve the channel type, but it seems to happen...