I saw this in paperUi but I always linked items to channels with .items files. I noticed that each items that not working doesn’t have a type on paperui and I thought it maybe related.
Because Trigger channels are stateless they cannot be bound to a switch. You would need a pushbutton thingy instead, but that’s not existing yet to my knowledge. I have no idea how trigger channels are supposed to be used by the graphical interfaces tbh, and paperui doesn’t know either therefore it doesn’t autolink those channels.
Ok, If I understand correctly you tell me that is just a PaperUI issue, but I don’t use it anyway. I speak about PaperUI because you told us before that was the better way to configure it, so I tested this way too.
I declared my items like I showed before but in my rules a sendCommand(ML_SALONZ1_NM, ON) doesn’t work anymore.
Thoses rules worked for a long time, and with the last build, they suddendty stop working.
No offence but please respect the volunteers free time here and use your brain!
I said the channel is stateless. No state. NADA. You cannot assign on or off, 1 or 0, or anything else to it. It is a trigger channel. I said this before. Read the documentation. Trigger channels cannot be triggered with sendcommand. It’s a different command.
And yes it worked before, because it WAS a switch channel before, by accident. Night mode on milight is not stateful, you can’t turn it on or off (or did you find an off button for nightmode on your remote?). It is an action that can be triggered, and we corrected the binding to reflect this.
And again although I repeat myself: no GUI, neither android app nor iOS app nor classicui or paperui support “Button” at the moment, only switches. So to make it very clear: you cannot use nightmode at this time, there is no GUI support for trigger channels. It’s not my fault as a binding developer, the GUI guys need to implement that.
Please read carefully and respect others free time.
Sorry for my misunderstanding and thanks you for your trigger channel explanation, I wasn’t aware about it. I will try to find how trigger a trigger channel in a rule.
Sorry to pop here like that but I’m having the exact same issue that MacFly have. Since last update I can’t use nightmode anymore. I triple read what you said to him, your documentation (which isn’t up to date ?).
I can say that I’m quite afraid to ask you but :
I said the channel is stateless. No state. NADA. You cannot assign on or off, 1 or 0, or anything else to it. It is a trigger channel. I said this before. Read the documentation. Trigger channels cannot be triggered with sendcommand. It’s a different command.
I’m not able to find that “different command”, may you please tell me / us which one is it ? I never encountered that kind of stuff and maybe don’t have the good keyword to find what I want over the web.
Hi Guys. I am not quite sure it this is good place for this but ill give it a try. So i got that new Mi Light router (ibox) and as well just got for a test RGBW_CCT mi light GU10. My problem is, when i am trying to pair the Ibox with my UPC router through Android app ( v 3.0 ) it just saying all the time connection fail. I had try to pair it with so many ways in many orders but it just does not work. The wifi password is correct. I can get acces to ibox from my phone only if ill connect to MI Light Ibox wifi. Therefore i am able to change the colours of the router but i still cant even link the bulb GU10 with it. So the question is whats wrong? Is it Ibox , or maybe my router from UPC provider? I had tryed to look in to UPC router settings and assign some IP’s and stuff for ibox but it doesnt even appear to try to connect to the router. Any solutions? I will be very happy for any help. Regards.
Regarding the trigger channels. I tried to find out how to use them and I realized that I misunderstood the concept. At the moment nightmode etc cannot be used. I opened an issue on Eclipse Smarthome to improve the documentation for binding developers or to extend the trigger channel to be used like I used it.
Depending on the outcome of that issue, the binding either stays like it is and we need to wait for the UIs and rules engine to get support for trigger channels, or the binding will need to be changed.
Thank You very much. This actually helped. My router worked in 2.4 and 5 at the same time, so i switched off just 5 and Ibox maneged to connect. But still i have an issue with Milight 4W RGB+CCT bulb, cant connect or sync it to the zone, no respond at all. Should I move ibox close to the celling in order to force it, or is there any other solution ? Regards. I hope this will work too…
Is anyone using the whitemode on the rgbLed type? I have the v3 bridge and the command is sent (according to the logs) but nothing happens. The color thing works for general control and color, but I cannot get the bulb to go white with a whitemode thing linked to a switch. Any suggestions will be appreciated! thanks
But should this not work programmatically? I.e through the whitemode thing linked to a switch? Just asking as it’s in the readme but doesn’t seem to work. For now I’m using the HSB type to turn the saturation down. And thanks for all the hard work keeping the binding up to date, awesome job!!
Hi, I’m trying out openhab for the first time as a way of controlling my limitlessled bulbs via an iBox2.
I’m on Windows 10 64 bit and have tried Milight binding with both Stable Version 2.1.0 and Snapshot Version 2.2.0.
In both cases I get the following error:
Exception in thread "SessionThread" java.lang.IllegalArgumentException: Port out of range:-1
at java.net.DatagramPacket.setPort(Unknown Source)
at org.openhab.binding.milight.internal.protocol.MilightV6SessionManager.send_search_for_broadcast(MilightV6SessionManager.java:256)
at org.openhab.binding.milight.internal.protocol.MilightV6SessionManager.session_handshake_process(MilightV6SessionManager.java:364)
at org.openhab.binding.milight.internal.protocol.MilightV6SessionManager.run(MilightV6SessionManager.java:435)
at java.lang.Thread.run(Unknown Source)
This error appears multiple time in my console when I start openhab and when I do a Search for things.
Does anyone have a reliable link or experience themselves on the different Milight options?
I have a lot of GU10 bulbs, marked as 4W (bought most about 2 years ago). As far as the web goes their brightness seems they are about 250lm (but then some say 400+ lumens…?). Some listing also say 5W for some GU10 models…
I see the newer 4W GU10 RGB+CCT bulbs are 250->280lm, but now I’m hesitant to buy them as I cannot get a definitive answer as to the brightness compared to my existing bulbs. I cannot go for a weaker bulb as I don’t want to add more to get the same lighting. Can anyone share some personal experience on the different options (GU10 4W RGBWW, GU10 4W CCT, 5W RGBWW, and the newer 4W RGB CCT) regarding their brightness? thanks!!
And sorry if this is off topic, just thought we all have these bulbs in common
Hi, I am experiencing exactly the same issue… everything worked fine with Version 2.0 but upgrading to 2.2 caused this issue with the Port being out of range… any ideas?
I have now manually installed org.openhab.binding.milight_2.1.0.ref-rc9 and the issue has stopped and everything is working normally.
David, first of all, thanks for the amazing Job, I am too happy integrating my MiLights with your binding that I cannot begin to explain. I am experiencing the consequences of the Whitemode change. With bulbs supporting saturation, I have no problem pulling saturation down to 0 as you suggested to enable white mode. Do you have any suggestion with RGBW ones that do not support Saturation?
Thanks a lot in advance for your answer and infinite thanks for the work in the binding!
