New Dome Range Extender


#21

Also, if you try the driver I made click configure, wait 5 seconds, then click refresh (after changing to the driver of course).


#22

That doesn't make sense to me. Basic Z-Wave Tool is just a driver. It has to be applied to a REAL device to do anything.

So you would change your dome device driver from whatever it is to Basic Z-Wave Tool and click save.


#23

Ok, I set the dome to a generic repeater and saved. Then did the command class report. Where is the report?


#24

In the logs. It isn't the most important info, but would be handy. Thanks.


#25

Getting this error still.
2019-03-08 02:32:41.150 pm errorjava.lang.NullPointerException: Cannot invoke method split() on null object on line 122 (getCommandClassReport)


#26

Using your driver I get this on the right side.

Current States

  • Night light OFF Threshold : 0
  • Night light ON Threshold : 0

I did set them to 0 by the way and saved


#27

Ok. That's about all there is to the driver. :smile:

Could try changing the thresholds, but there isn't really anything else you can do with the device from the hub.

Also, as when adding all repeating Z-Wave devices, you should wait 8+ hours and then do a zwave repair to make sure the mesh gets rebuilt.


#28

OK, I will play with the thresholds to see if the light changes and I will do a z-wave repair tonight. Thanks for all your help and I will let you know.


#29

This popped up in the log.
2019-03-08 02:45:36.879 pm debugParse returned null for zw device: 5A, command: 7006, payload: 02 01 00

dev:7422019-03-08 02:45:36.877 pm debug---CONFIGURATION REPORT V2--- Formal Dining Room Dome Range Extender sent ConfigurationReport(configurationValue:[0], parameterNumber:2, size:1)

dev:7422019-03-08 02:45:36.876 pm debugcmd: ConfigurationReport(configurationValue:[0], parameterNumber:2, size:1)

dev:7422019-03-08 02:45:36.874 pm debugparse() >> zwave.parse(zw device: 5A, command: 7006, payload: 02 01 00 )

dev:7422019-03-08 02:45:35.835 pm debugParse returned null for zw device: 5A, command: 7006, payload: 01 01 00

dev:7422019-03-08 02:45:35.826 pm debug---CONFIGURATION REPORT V2--- Formal Dining Room Dome Range Extender sent ConfigurationReport(configurationValue:[0], parameterNumber:1, size:1)


#30

Command class report can't come from the Generic Z-wave repeater driver. Do you mean you changed to the Basic Z-wave tool driver?


#31

I have his driver selected. Is that incorrect?


#32

That's fine, those messages will go away after debug logging turns itself off (automatically does that 30 min after being turned on).


#33

Did you read what I wrote? You cannot do "get command class report" from the Generic Z-wave Repeater driver. The option isn't there. So, I couldn't follow what you were talking about.


#34

Yes I read what you said and I guess I didn't explain it enough, my bad. When I selected the get command class report I had Jason's driver he created selected.


#35

OK, thanks Jason. I am getting a signal way out at the mailbox from a ecolink door/window sensor so I guess the repeater is working.


#36

Good deal. For the record, the device should have worked even with the generic "device" driver - you just wouldn't have been able to tweak the night light settings.


#37

Understood. I like having the capability though because it is attached to my front window via the suction cup so I don't want the neighbors to think there is a weird mysterious light in the window.


#38

I tested the device and those configuration parameters didn't appear to do anything so I spoke with Dome and it turns out they don't actually do anything and shouldn't have been included in the manual.

The physical button on the device changes the LED mode which determines whether the LED automatically turns on/off based on the light level or if it can be turned on/off like a light.


#39

Interesting. I couldn't get them to do anything either. I was able to change the night light as you said. Thanks for the reply!


#40

So using this device Iā€™m seeing this log a lot and Iā€™m trying to troubleshoot why my hub is slowing down. Any ideas?

returned null for zw device: 86, command: 2503, payload: FF , isMulticast: false

[dev:2498](http://192.168.7.201/logs#dev2498)2019-05-08 08:12:45.205 pm[warn](http://192.168.7.201/device/edit/2498)Device received unhandled command: SwitchBinaryReport(value:255)

[dev:2498](http://192.168.7.201/logs#dev2498)2019-05-08 08:12:45.203 pm[debug](http://192.168.7.201/device/edit/2498)cmd: SwitchBinaryReport(value:255)

[dev:2498](http://192.168.7.201/logs#dev2498)2019-05-08 08:12:45.201 pm[debug](http://192.168.7.201/device/edit/2498)parse() >> zwave.parse(zw device: 86, command: 2503, payload: FF , isMulticast: false)

[dev:2498](http://192.168.7.201/logs#dev2498)2019-05-08 08:12:44.659 pm[debug](http://192.168.7.201/device/edit/2498)Parse returned null for zw device: 86, command: 2503, payload: 00 , isMulticast: false

[dev:2498](http://192.168.7.201/logs#dev2498)2019-05-08 08:12:44.657 pm