FIbaro temp implant error since [2.3.3.123]

@christi999
Not sure if this is maintained anymore but just in case.
Seems like it happened on the C7 update.

dev:12482022-09-27 14:32:08.486warnNeed to handle this cmd.notificationType: 9

dev:12482022-09-27 08:02:26.598errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 828 (method configure)

Notification type 9 is a hardware failure, see link. Some people have that with external temperature sensor (endpoint>=8) that are not 100% compatible and just comment out the corresponding line in the driver code. Maybe turn debug logging ON to get more info and know which endpoint it is.

The other error, I have no clue. Looks like something is corrupted in the state variables. I updated to 2.3.3.125 and I didn't encounter problems. Did you do a "save preferences" before "configure".

Thanks for the info.
I have another one that's not complaining at all.
I rebooted the device and did a config. Turned on the logs.
Using the standard DS18B20. Seems to be giving me the temp fine with regular events.
I'll monitor and "play" with it.

1 Like

I think I know what's going on. I changed to your driver for both my Implants and I was left with a legacy Child from the built in driver that does not report anymore.
It's probably that causing the error. I can't delete it so I'm not sure what to do except just delete and reinstall the devices. I tried disabling them but I still get the error.
HE fun.

Bit of a dumb question but I don't remember how to add a Child now that the Parent has been discovered.
I reinstalled the device and all is well; errant Child is gone and 4 Generic children have been added.
If I add an input later how do I discover it and use your driver? Or, do I just have to exclude/include the device and have it auto-discover the new hardware config?

I know this is a "my problem" not yours :slight_smile:
I have reinstalled your driver and checked my hardware.
I always get this WARN but not with the internal driver.
I assume that the HE guys just don't handle all the messages; your driver is more complete and the reason for my initial change.
Can you tell me where I could comment out the handling of this one error?
Not really a Groovy expert.
I just don't like to see errors in the logs :wink: Again, my OCD problem. :wink:

dev:20342022-10-09 07:51:57.590warnNeed to handle this cmd.notificationType: 9

I didn't get an email notification so I didn't answer before...I see this messages on line 550, 581, 612 of the code of the "smart implant" driver file. Comment-out the three of them. You can also comment-out the line directly following, it updates the device event log.

Hey, thanks for the insight.
I'll try the comment out. I don't know what triggers it but it's only once a dayish for both devices.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.