Fibaro RGBW controller (Hubitat beta driver)

BorrisTheCat · December 29, 2018, 12:27am

@bravenel I'm testing the new driver and I get this error for the white child device.

[dev:3](http://192.168.1.81/logs#dev3)2018-12-29 12:22:16.399 am [error](http://192.168.1.81/device/edit/3)java.lang.NullPointerException: Cannot get property 'warmWhite' on null object (parse)

Off works fine but on doesn't do anything.

Also once the white child is working is this something we could add for the other outputs? It would give full control of the device then one of mine is set up as 2 white loads on W then on R.

JohnRob · December 29, 2018, 5:13am

I created the following rule. It turned on without any errors.

I first renamed the Warm White channel so I could tell it from the RGB channel.

I didn't wait to test OFF.

BorrisTheCat · December 29, 2018, 9:29am

The child device also doesn't report as a off switch state, but you can send it a off. As a work around I take the off state from the parent device in order to evaluate the rule this worked but when I turned it on at 5% it didn't. So it seems it thinks 5% is off

Edit: 8% reported as 9% 6,7 % worked fine and reports a ON state.
5 then worked? There must be some Gremlins ?

Ok it's something to do with dimmer per mode it's not the % that's the issue when you change the mode it seems to lose its state of OFF? If you then call a manual off to it, it works again untill you change the mode again.

BorrisTheCat · December 30, 2018, 12:13pm

@mike.maxwell on one of my devices when using this driver it doesn't report state changes to OFF, ON works fine but it wont go back to OFF. oddly it's only on one of the devices (they are set up the same), but as soon as I go back to the old driver it reports that its off.

BorrisTheCat · December 30, 2018, 12:40pm

@bravenel will/ can things like setRedLevel, setBlueLevel, setGreenLevel and setWarmWhiteLevel be added to Rule Machine?

mike.maxwell · December 30, 2018, 2:58pm

These are not standard commands, this is the only device that uses them.
I understand the current limitation within custom commands of not supporting variables, it may be possible to address this.

But if you're trying to use the 4 channels independently, you're better off writing an application to work directly with this device.

I haven't had a chance to look into the off issue yet.

BorrisTheCat · December 30, 2018, 8:20pm

yeah variable would be a even better idea if it's possible. This would help with a few other drivers as well then.

BorrisTheCat · January 3, 2019, 9:22am

@mike.maxwell is the effects enabled in the driver yet? It looks like there is but I haven't been able to get any working, if it is how do we trigger it?

mike.maxwell · January 3, 2019, 12:47pm

Effects have been there since the first release.
setEffect(id)
I may have missed a configuration parameter in configure or something, I forgot to test this driver with a fresh join.
I may have you run the zwave tool on yours so we can compare parameter settings

BorrisTheCat · January 3, 2019, 12:56pm

when I click configure with the driver you get

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:53:52.066 pm [error](http://192.168.1.81/device/edit/464)java.lang.NullPointerException: Cannot get property 'blue' on null object (parse)

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:53:51.966 pm [error](http://192.168.1.81/device/edit/464)java.lang.NullPointerException: Cannot get property 'green' on null object (parse)

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:53:51.863 pm [error](http://192.168.1.81/device/edit/464)java.lang.NullPointerException: Cannot get property 'red' on null object (parse)

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:53:51.788 pm [error](http://192.168.1.81/device/edit/464)java.lang.NullPointerException: Cannot get property 'warmWhite' on null object (parse)

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:53:48.498 pm [debug](http://192.168.1.81/device/edit/464)configure

if i run get parameter report in BZT i get.

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:44.624 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:255, size:4, value:62520

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:39.613 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:73, size:1, value:0

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:39.544 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:72, size:1, value:9

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:39.526 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:71, size:1, value:1

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.750 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:45, size:1, value:10

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.570 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:44, size:2, value:30

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.550 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:43, size:1, value:5

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.508 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:42, size:1, value:0

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.426 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:39, size:2, value:600

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.391 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:38, size:1, value:10

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:38.042 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:30, size:1, value:3

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.572 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:16, size:1, value:1

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.540 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:15, size:1, value:1

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.489 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:14, size:2, value:4369

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.469 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:13, size:1, value:2

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.427 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:12, size:1, value:-1

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.385 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:11, size:1, value:50

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.360 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:10, size:2, value:10

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.230 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:9, size:1, value:1

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.193 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:8, size:1, value:0

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.135 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:6, size:1, value:4

[dev:464](http://192.168.1.81/logs#dev464)2019-01-03 12:55:37.020 pm [info](http://192.168.1.81/device/edit/464)ConfigurationReport- parameterNumber:1, size:1, value:-1

BorrisTheCat · January 3, 2019, 1:06pm

do you have a list of the effects ID's?

mike.maxwell · January 3, 2019, 1:42pm

they should be listed in device current state.

lightEffects : {"1":"Fire Place","2":"Storm","3":"Deep Fade","4":"Lite Fade","5":"Police"}

is that not the case?

found two parameters that I would like you to change on yours, if this doesn't sort it I'll have to pull mine off the ceiling and join it again...

parameterNumber:6, size:1, value:0
parameterNumber:8, size:1, value:1

BorrisTheCat · January 3, 2019, 1:53pm

nope

mine was already joined before using another driver, could that be the issue?

edit:
also have this

mike.maxwell · January 3, 2019, 2:09pm

in reviewing the code, yes that's the issue, some initialization items are in the drivers installed method.
I've added some code to configure to check and set these items.
There isn't a way to call installed using a custom command, so we can wait for the next build, or you can join the device again.

BorrisTheCat · January 3, 2019, 2:15pm

I don't mind joining it/ them again, it's all in the name of beta testing

once i re-join they should automatically select the RGBW controller (beta) driver, is that correct? just so I know what to look out for.

mike.maxwell · January 3, 2019, 2:17pm

correct

BorrisTheCat · January 3, 2019, 2:25pm

1st time it grabbed the old user driver so i had to delete that and start again (surly the preference should be stock before user?)

edit: effects are working now so good start.
Edit2: will this device not be supported by google? Also the device is still not reporting the OFF unless you refresh for some reason. I will sort the rest and see what happens. I seem to remember having a issue on ST with the devices and had to add a refresh to the end of the WC piston. But i didn't need it before with the ported user driver that was on here.

mike.maxwell · January 3, 2019, 3:25pm

are you using the child device for the white channel?

BorrisTheCat · January 3, 2019, 3:30pm

yes, is that the issue? The OFF status i'm referencing is the parent though (i don't think the switch works at all for the child?)

BorrisTheCat · January 3, 2019, 5:46pm

everything is now installed correctly now but there is definitely a bug with the switch status, all of them don't update correctly. If you use refresh this will correct its status though. @mike.maxwell is there anything i can do to help debug?

I tried to add this to a rule but unfortunately RM doesn't allow you to select the order of the commands that i know off? So a refresh on true is the first thing that gets sent rather than the last @bravenel is this something that could be added to RM?