Rooms Manager: Smarter Rooms: Personalized home automation with Occupancy

New error:

:6552018-08-04 10:19:07.648:debugGreat Room processCoolHeat: rule: null

app:6552018-08-04 10:19:07.630:infoGreat Room processCoolHeat

app:6552018-08-04 10:18:33.233:errorjava.lang.NullPointerException: Cannot get property '16' on null object on line 5125 (checkAndTurnOnOffSwitchesC)

app:6552018-08-04 10:18:33.178:infoGreat Room turnSwitchesOnAndOff

@patrick, here's my experience on MacOSX 10.13.6 in Chrome Version 67.0.3396.99: the dashboard page locks up completely when adding the attribute tile. Any attempt to open the same dashboard throws the same error.

Meanwhile this is going on with the dashboard timing out, the main hub page is glacially slow and control isn't released for quite a while after closing the dashboard page.

still having an issue after this?

all good … night lights working for you? :slight_smile:

Yes its fixed!

1 Like

If you have a dashboard that does this, can you PM me the layout from the side menu "i" in the bottom right that pops up?

I can see if I can recreate it.

I noticed the same issue (assigning button numbers). For ABC I have to manually tell the app how many buttons my switches have since it doesn’t seem to automatically detect it. Would it be possible to have the same option here?

which button device is this? what driver does it use?

please post a screenshot of the device details:

It’s a Zlink z-wave switch. Basically a rebranded Homeseer. It supports press, hold, and double tap on the on or off buttons.

ok. which driver? (just want to confirm its the inbuilt one and not one named like that. :slight_smile:)

It’s the Generic Z-Wave CentralScene Switch driver. Or, if it’s a dimmer switch it’s Generic Z-Wave CentralScene Dimmer. They’re built in to the Hubitat.

thanks … now that we have confirmed that …

@mike.maxwell the driver seems to show push button support for this device but does not publish the number of buttons. would this be a driver fix?

thank you.

1 Like

Yeah, my mistake, not saving after I loaded the parent app, before I put a room child.

this is my current error:

:6552018-08-04 10:19:07.648:debugGreat Room processCoolHeat: rule: null

app:6552018-08-04 10:19:07.630:infoGreat Room processCoolHeat

app:6552018-08-04 10:18:33.233:errorjava.lang.NullPointerException: Cannot get property '16' on null object on line 5125 (checkAndTurnOnOffSwitchesC)

app:6552018-08-04 10:18:33.178:infoGreat Room turnSwitchesOnAndOff

numberOfButtons is set when the driver is installed, since this driver was replaced manually, installed didn't run...
I can add it to configure...
@murray.sean.d can you send me the fingerprint info on both the switch and dimmer?
I'd like to get that added to these drivers.

I did have to manually change the driver since it didn’t detect it originally. Is the fingerprint something I can view in device status somewhere, or do I need to exclude and re-pair a switch and dimmer to get it?

its at the very bottom of the driver details:

Ahh, ok. Thanks. Below is the fingerprints for the switch and dimmer. Also, when I just did a quick search on how to find the fingerprint (before seeing your reply) I saw a post mentioning the need to hit the configure button in the device status after changing a driver. That’s not something I was aware of, and I don’t believe I did it for any of my switches and dimmers. Should I go back at this point and press that button for each one?

Switch

  • deviceType: 17479
  • inClusters: 0x5E,0x86,0x72,0x5A,0x85,0x59,0x73,0x55,0x25,0x70,0x2C,0x2B,0x9F,0x6C,0x5B,0x7A
  • outClusters: 0x5B
  • deviceId: 12339
  • manufacturer: 789

Dimmer

  • deviceType: 17479
  • inClusters: 0x5E,0x86,0x72,0x5A,0x85,0x59,0x55,0x73,0x26,0x70,0x2C,0x2B,0x5B,0x7A,0x9F,0x6C
  • outClusters: 0x5B
  • deviceId: 12340
  • manufacturer: 789

that is the best practice when changing drivers manually, most drivers have settings that should be applied in order to interact with the device properly.
This happens automatically when the device pairs with a matching driver, but needs to be done manually anytime you replace the driver with a different one.

The button count issue however won't be fixed until the next release comes out, when it does you should click configure again, and the buttonCount attribute will be set.

1 Like

Thanks Mike, much appreciated.

1 Like

ok. great that that is fixed.

since the installs have happened a little out of order from apps:

  1. click on rooms manager and click done all the way thru till the settings for rooms manager are saved
  2. click on each room then click done till the settings for each of the rooms are saved again.

after that if the error is still happening … post a snapshot of the view all settings page for the room that error is logged.