I have some of the older Leviton Scene controllers identified by Hubitat as VRSC4. The catalog number on the device is RZCS4 - I can provide a photo if needed. The devices install just fine and Hubitat seems to do okay when a button is pressed "On", but when you press the button to put it into the off state, there's a NullPointerExcpetions that is generated. I set up a simple rule with some logging to verify this. A copy of the log is below.
Thanks,
Stacy
Log:
dev:472020-08-08 09:53:43.867 pm errorjava.lang.NullPointerException: Cannot invoke method currentValue() on null object (parse)
dev:472020-08-08 09:53:43.822 pm infoBreakfast Area Scene Controller button 1 was pushed [physical]
app:1522020-08-08 09:53:41.246 pm infoMessage from device ------> Breakfast Area Scene Controller:1 on
dev:2142020-08-08 09:53:41.073 pm infoBreakfast Area Scene Controller:1 was turned on [physical]
dev:472020-08-08 09:53:41.035 pm infoBreakfast Area Scene Controller button 1 was pushed [physical]
Are you able to post a screenshot of the device setup screen?
I saw this same error recently with another community member where they were putting a tile on a dashboard for a virtual button and forgot to allocate a button number for the tile. Perhaps there has not been a button number allocated to the off button for your device?
Wow! Quick update. I just noticed something really odd. When I press the button that I'm testing, the following sequence happens:
Press the button. The indictor on the button lights up. On message in the log.
Press the button. The indicator on the button turns off. nullPointerException in the log.
Press the button. The indicator turns on. Off message in the log!
Fourth press. The indicator turns off. nullPointerException in the log.
Note that each button on the controller has it's own indicator. I'm not controlling any devices with the controller yet, I'm only logging messages.
So the exception is happening on every other button press! The On/Off messages are every other press as well. Hopefully this will give a clue to the device driver author. By the way, I am willing to test code. I'm a software developer, so I know it can help to have multiple test environments.
Hmm, that is weird, sadly not the same as the button controller issue I mentioned earlier. I might look at it a bit more later today, hut hopefully support may be able to help as well.
I've been telling all my geek friends about Hubitat. I think I may have sold a few for you. Customer support like this coupled with a fantastic product and a great community is a true winning combination. Thanks very much!
