I have knocked-up a dimmable-light plugin for the new MiLight RGB+W lamps with the V3 WiFi Bridge. This is very alpha-level code. I don’t have the hardware to test it but it installs on Vera and I have verified that it is sending the commands as per the documentation provided by Hamish.
If anyone has the new hardware and fancies being a test-pilot, the plugin and instructions are available here: MiLightRGBW
You will need to set your router’s DHCP to always give the V3 bridge the same IP address and then enter that address into MiLightRGBW’s IPaddr field on the Advanced tab.
You can now relax put your feet up and enjoy the night.[/quote]
Last time I replaced an rtf with a pdf, you suggested a cold-one. Are you now concerned about my alcohol intake?
I just had a few moments to play with the updated (v3) plugin and it does seem to mostly work … thanks Rex. Enroll worked. I do notice some problems with the brightness setting whilst in white mode where the dimmest setting seems to be in the centre of the slider and just adjacent to ‘-’ is the brightest, + is mid level, but I’ll report back later on that after I’ve had more time. The Hue value does set different colours OK. BTW this is using the 6W RGBW (not the newer 9W)
I’ve uploaded a new version of MiLightRGBW. This has been adjusted to match the subtleties of the RGBW lamp and V3 bridge. The included PDF reflects the changes but, briefly:
[ul][li]SetDiscoMode now requires newDiscoMode argument (1-9)[/li]
[li]Disco button replaced by SetMode with input field for DiscoMode (1-9)[/li]
[li]SetDiscoRate newDiscoRate range is now 1-8[/li]
[li]Dim level scaling changed to suit lamp characteristics[/li]
[li]Several configuration options changed[/li][/ul]
The disco effects mode is a real challenge with this lamp. When engaged, it sets the lamp to full brightness and overwrites the previous stored levels for both white and colour modes. It also behaves differently if the previous mode was white or colour. I have chosen to let disco mode run at full brightness unless the configuration option RDL is set. The plugin will restore the previously set dim level when the lamp is switched to white or colour modes.
There is similar fun and games with the disco effects rate. The lamp switches to rate 6 whenever the disco mode is changed. By default the plugin resets the lamp to the previously set value. If you set configuration option NRR then the plugin will leave the lamp running at its default rate and set the state-variable accordingly.
I’ve measured the white-light output of the RGB+W lamp. Test results are here. It is considerably better than the old RGB lamp but still not as bright as the dedicated White version.
My lamp is labelled 6W - I have not been able to find the 9W version mentioned by Hamish. If you are seeing this, Hamish, what’s the story?
Thanks @markrosssmith. I think they just added that 'cos it wasn’t there two days ago. ??? I don’t think I want to spend another 20 quid just so I can measure it and test it on the plugin. I’ll let someone else be the guinea-pig. I already have two lamps I don’t use 'cos they’re too dim.
If the 820 lumens output is true, it should be brighter than the white lamp. Hopefully they haven’t changed the way it responds to commands relative to the 6W version and it will work with the MiLightRGBW plugin. I shall await comments…
I’ve been experimenting with ways to remove a lamp from a group/zone. As far as I can tell, this is not possible with the Android app and I have also not been able to achieve it from a Vera plugin. I can’t even get it to work by sending timed UDP packets from a PC. I’m more or less convinced that the V3 bridge doesn’t support it.
This means that you may need to buy the appropriate hardware remote to allow you to manage your groups. The remote allows you to remove a lamp from all its associations in one go. To do this, you turn the lamp power off then turn it back on and, within three seconds, hit the Group On button (to which it was associated) five times. If successful, the lamp will flash about six times.
I was having similar problems with a 9W dual white led but read in the RGBW controler manual that you need to connect the lamp to power and within 3 seconds press the on button with which the lamp was associated 5 times. That did it for me (from the Android app using a V3 bridge).
[quote=“intveltr, post:94, topic:175037”]How does the RGBW plugin work? I don’t have one of these lamps, but I’d like to support the color stuff in the HomeWave app.
Does the plugin / bulb support both colored (hue) and white w/ adjustable color temp?
If so, how can a hue or color temp be sent to the plugin?
Is there a parameter in the plugin to switch the lamp from white to color and vice versa?
Thanks :)[/quote]
Hi @intveltr,
The hue setting is exactly the same as for the MiLightCU plugin we discussed a while back. The action is:
The action to set white is: urn:dcineco-com:serviceId:MiLightRGBW1 SetWhiteMode
White is 2700K and not adjustable. The lamp is either in RGB mode (actually only a mix of two colours) or white. There is also a Disco mode but you are probably better staying away from that. ;D
I’ve attached the documentation in case it is some help.
I was having similar problems with a 9W dual white led but read in the RGBW controler manual that you need to connect the lamp to power and within 3 seconds press the on button with which the lamp was associated 5 times. That did it for me (from the Android app using a V3 bridge).[/quote]
It’s good to know that it works for someone. I tried many times without success. Maybe it depends on the Android platform… I really don’t see how this fits in with the Granny-friendly intent of this system. :
[quote=“RexBeckett, post:95, topic:175037”]Hi @intveltr,
The hue setting is exactly the same as for the MiLightCU plugin we discussed a while back. The action is: urn:dcineco-com:serviceId:MiLightRGBW1 SetHue newHue = <0-255>
The action to set white is: urn:dcineco-com:serviceId:MiLightRGBW1 SetWhiteMode[/quote]
Thanks for that. Does the plugin also report the current mode (white / RGB)? That would make it easy to support this in HomeWave.
the reason why iam asking is … if i set NightLight (also via luup) … the lamp status change to OFF (which is fine for me)
the SetTarget newTargetValue=0 does not have any effect if the lamp is in this state (nightLight stays on)
but if i press the OFF Button on the UI … it always turns off
[quote=“rickysuper”]for V3 web login is different from V2:
milight IP/home.html
PS: since the device will use DHCP to get the IP, you have to look for the device IP named “Link_Wi-Fi” from your DHCP table of your router.
After login, you can then change the mode settings, IP and port settings… etc.
I decided to use back the “wifi controller” to remote control the device because the app “Milight” always not work when out of home.[/quote]
Thank you @rickysuper, that is really helpful.
I don’t see much value in being able to control my lamps with the Mi-Light app when away from home. With the aid of the MiLightRGBW plugin, I control my lamps with Vera scenes and PLEG timing logic. I can control all of these remotely if I wish using the AutHomationHD app.
the reason why iam asking is … if i set NightLight (also via luup) … the lamp status change to OFF (which is fine for me)
the SetTarget newTargetValue=0 does not have any effect if the lamp is in this state (nightLight stays on)
but if i press the OFF Button on the UI … it always turns off
an idea ?[/quote]
There is no difference at all. The Off button on MiLightWU1 UI initiates the action SetTarget newTargetValue = 0. I can think of no reason why it would behave differently with a Lua action or the UI button. In either case, I would expect the lamp to turn off.
If you set Debug to 1, the plugin will log its activity.
