Help with milight

Add-ons Bindings
22

Ok, here are the detailed information.

Hardware = Desktop-PC with AMD Phenom II X4 CPU, 16GB RAM
OS = Ubuntu 16.04.01 64 bit
Java = java version “1.8.0_101” / Java™ SE Runtime Environment (build 1.8.0_101-b13)
OH version is as mentioned above 1.8.3

As this is my test system, I removed everything (bindings, rules, items, …) except the milight related parts.
Then started OH and did exactly the same

  • Turned on switch for milight strip controler -> Switch Light_Party2 (gMilight) {milight=“bridge1;5”}
  • Turned off switch
  • Turned on switch again
  • Changed color with Colorpicker item -> Color Light_Party (gMilight) {milight=“bridge1;5;rgb”}
  • Changed brightness with Colorpicker item

Here is the debug log with 1.7.1 binding (everythings works fine)

18:07:00.637 [DEBUG] [.s.internal.SchedulerActivator:36   ] - Scheduler has been started.
18:07:00.670 [INFO ] [uartz.impl.StdSchedulerFactory:1175 ] - Using default implementation for ThreadExecutor
18:07:00.686 [INFO ] [rtz.core.SchedulerSignalerImpl:61   ] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
18:07:00.687 [INFO ] [rg.quartz.core.QuartzScheduler:243  ] - Quartz Scheduler v.2.1.7 created.
18:07:00.688 [INFO ] [org.quartz.simpl.RAMJobStore  :154  ] - RAMJobStore initialized.
18:07:00.689 [INFO ] [rg.quartz.core.QuartzScheduler:268  ] - Scheduler meta-data: Quartz Scheduler (v2.1.7) 'openHAB-job-scheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 2 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

18:07:00.690 [INFO ] [uartz.impl.StdSchedulerFactory:1324 ] - Quartz scheduler 'openHAB-job-scheduler' initialized from specified file: './etc/quartz.properties'
18:07:00.690 [INFO ] [uartz.impl.StdSchedulerFactory:1328 ] - Quartz scheduler version: 2.1.7
18:07:00.690 [INFO ] [rg.quartz.core.QuartzScheduler:534  ] - Scheduler openHAB-job-scheduler_$_NON_CLUSTERED started.
18:07:00.693 [DEBUG] [o.config.core.ConfigDispatcher:146  ] - Processing openHAB default configuration file '/opt/openhab/openhab/configurations/openhab_default.cfg'.
18:07:00.955 [DEBUG] [o.config.core.ConfigDispatcher:168  ] - Processing openHAB main configuration file '/opt/openhab/openhab/configurations/openhab.cfg'.
18:07:01.182 [DEBUG] [.o.core.internal.CoreActivator:93   ] - UUID file already exists at '/opt/openhab/openhab/webapps/static/uuid' with content '53e6ce57-3afb-4ea7-93f2-7685a83c16be'
18:07:01.183 [DEBUG] [.o.core.internal.CoreActivator:115  ] - Created file '/opt/openhab/openhab/webapps/static/version' with content '1.8.3'
18:07:01.184 [INFO ] [.o.core.internal.CoreActivator:61   ] - openHAB runtime has been started (v1.8.3).
18:07:01.206 [DEBUG] [a.internal.AutoUpdateActivator:31   ] - AutoUpdate binding has been started.
18:07:01.944 [DEBUG] [.p.i.PersistenceModelActivator:23   ] - Registered 'persistence' configuration parser
18:07:01.962 [DEBUG] [.c.t.i.TransformationActivator:38   ] - Transformation Service has been started.
18:07:02.007 [DEBUG] [m.internal.MultimediaActivator:34   ] - Multimedia I/O bundle has been started.
18:07:02.046 [DEBUG] [.s.i.DiscoveryServiceActivator:27   ] - Discovery service has been started.
18:07:02.057 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:93   ] - mDNS service has been started
18:07:02.100 [DEBUG] [.io.transport.mqtt.MqttService:123  ] - Starting MQTT Service...
18:07:02.122 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:53   ] - Service Discovery initialization completed.
18:07:02.215 [DEBUG] [.i.internal.ItemModelActivator:24   ] - Registered 'item' configuration parser
18:07:02.322 [DEBUG] [o.o.c.i.items.ItemRegistryImpl:137  ] - Item provider 'GenericItemProvider' has been added.
18:07:03.032 [DEBUG] [.o.m.s.i.SitemapModelActivator:23   ] - Registered 'sitemap' configuration parser
18:07:03.096 [DEBUG] [io.rest.internal.RESTActivator:33   ] - REST API has been started.
18:07:04.160 [INFO ] [penhab.io.rest.RESTApplication:144  ] - Started REST API at /rest
18:07:04.161 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66   ] - Registering new service _openhab-server._tcp.local. at port 8080
18:07:09.862 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66   ] - Registering new service _openhab-server-ssl._tcp.local. at port 8443
18:07:11.734 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'default.sitemap'
18:07:11.922 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'test.items'
18:07:11.955 [DEBUG] [i.internal.GenericItemProvider:154  ] - Processing binding configs for items from model 'test.items'
18:07:11.960 [DEBUG] [i.internal.GenericItemProvider:133  ] - Read items from model 'test.items'
18:07:12.534 [INFO ] [.o.u.w.i.servlet.WebAppServlet:80   ] - Started Classic UI at /classicui/openhab.app
18:07:12.845 [DEBUG] [.r.internal.RuleModelActivator:42   ] - Registered 'rules' configuration parser
18:07:12.856 [DEBUG] [m.r.internal.engine.RuleEngine:77   ] - Started rule engine
18:07:15.376 [DEBUG] [.b.m.internal.MilightActivator:34   ] - Milight binding has been started.
18:07:15.385 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'Light_Party2 (Type=SwitchItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:07:15.386 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'Light_Party (Type=ColorItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:07:15.387 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'DiscoMode (Type=DimmerItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:07:15.387 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'DiscoSpeed (Type=DimmerItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:07:22.008 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'test.rules'
18:07:58.119 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:07:58.120 [DEBUG] [.o.b.m.internal.MilightBinding:608  ] - milight: sendOn
18:07:58.120 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '22:00:55'
18:07:58.121 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:22.150 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:08:22.151 [DEBUG] [.o.b.m.internal.MilightBinding:660  ] - milight: sendOff
18:08:22.151 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '21:00:55'
18:08:22.151 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '21:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:40.364 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:08:40.364 [DEBUG] [.o.b.m.internal.MilightBinding:608  ] - milight: sendOn
18:08:40.364 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '22:00:55'
18:08:40.365 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.459 [DEBUG] [.o.b.m.internal.MilightBinding:178  ] - milight: item is of type rgb
18:08:52.459 [DEBUG] [.o.b.m.internal.MilightBinding:721  ] - milight: sendColor
18:08:52.459 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '20:5c:55'
18:08:52.460 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '20:5c:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.460 [DEBUG] [.o.b.m.internal.MilightBinding:192  ] - milight: sendPercent
18:08:52.460 [DEBUG] [.o.b.m.internal.MilightBinding:608  ] - milight: sendOn
18:08:52.461 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '22:00:55'
18:08:52.461 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.561 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:52.562 [DEBUG] [.o.b.m.internal.MilightBinding:608  ] - milight: sendOn
18:08:52.562 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '22:00:55'
18:08:52.562 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.663 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:52.664 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.764 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:52.765 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:52.765 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.866 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:52.866 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:52.867 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:52.967 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:52.968 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:52.968 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.069 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.070 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.070 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.170 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.171 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.172 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.272 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.273 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.273 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.374 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.374 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.375 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.475 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.476 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.476 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:08:53.577 [DEBUG] [.o.b.m.internal.MilightBinding:304  ] - milight: sendIncrease
18:08:53.578 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '23:00:55'
18:08:53.579 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '23:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.569 [DEBUG] [.o.b.m.internal.MilightBinding:178  ] - milight: item is of type rgb
18:09:11.569 [DEBUG] [.o.b.m.internal.MilightBinding:721  ] - milight: sendColor
18:09:11.569 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '20:5c:55'
18:09:11.570 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '20:5c:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.570 [DEBUG] [.o.b.m.internal.MilightBinding:192  ] - milight: sendPercent
18:09:11.570 [DEBUG] [.o.b.m.internal.MilightBinding:608  ] - milight: sendOn
18:09:11.571 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '22:00:55'
18:09:11.571 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.672 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:11.672 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:11.673 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.773 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:11.774 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:11.777 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.878 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:11.878 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:11.879 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:11.979 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:11.980 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:11.981 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:12.081 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:12.082 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:12.082 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:12.183 [DEBUG] [.o.b.m.internal.MilightBinding:348  ] - milight: sendDecrease
18:09:12.183 [DEBUG] [.o.b.m.internal.MilightBinding:780  ] - milight: messageBytes to transform: '24:00:55'
18:09:12.184 [DEBUG] [.o.b.m.internal.MilightBinding:771  ] - Sent packet '24:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:09:29.232 [INFO ] [penhab.io.rest.RESTApplication:160  ] - Stopped REST API
18:09:29.232 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:80   ] - Unregistering service _openhab-server._tcp.local. at port 8080
18:09:31.235 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:80   ] - Unregistering service _openhab-server-ssl._tcp.local. at port 8443

And this is the log for 1.8.3 binding (switch and colorchange are ok, but no brightness change)

18:13:14.823 [DEBUG] [.s.internal.SchedulerActivator:36   ] - Scheduler has been started.
18:13:14.855 [INFO ] [uartz.impl.StdSchedulerFactory:1175 ] - Using default implementation for ThreadExecutor
18:13:14.872 [INFO ] [rtz.core.SchedulerSignalerImpl:61   ] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
18:13:14.872 [INFO ] [rg.quartz.core.QuartzScheduler:243  ] - Quartz Scheduler v.2.1.7 created.
18:13:14.873 [INFO ] [org.quartz.simpl.RAMJobStore  :154  ] - RAMJobStore initialized.
18:13:14.874 [INFO ] [rg.quartz.core.QuartzScheduler:268  ] - Scheduler meta-data: Quartz Scheduler (v2.1.7) 'openHAB-job-scheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 2 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

18:13:14.875 [INFO ] [uartz.impl.StdSchedulerFactory:1324 ] - Quartz scheduler 'openHAB-job-scheduler' initialized from specified file: './etc/quartz.properties'
18:13:14.875 [INFO ] [uartz.impl.StdSchedulerFactory:1328 ] - Quartz scheduler version: 2.1.7
18:13:14.875 [INFO ] [rg.quartz.core.QuartzScheduler:534  ] - Scheduler openHAB-job-scheduler_$_NON_CLUSTERED started.
18:13:14.878 [DEBUG] [o.config.core.ConfigDispatcher:146  ] - Processing openHAB default configuration file '/opt/openhab/openhab/configurations/openhab_default.cfg'.
18:13:15.136 [DEBUG] [o.config.core.ConfigDispatcher:168  ] - Processing openHAB main configuration file '/opt/openhab/openhab/configurations/openhab.cfg'.
18:13:15.376 [DEBUG] [.o.core.internal.CoreActivator:93   ] - UUID file already exists at '/opt/openhab/openhab/webapps/static/uuid' with content '53e6ce57-3afb-4ea7-93f2-7685a83c16be'
18:13:15.377 [DEBUG] [.o.core.internal.CoreActivator:115  ] - Created file '/opt/openhab/openhab/webapps/static/version' with content '1.8.3'
18:13:15.378 [INFO ] [.o.core.internal.CoreActivator:61   ] - openHAB runtime has been started (v1.8.3).
18:13:15.398 [DEBUG] [a.internal.AutoUpdateActivator:31   ] - AutoUpdate binding has been started.
18:13:16.136 [DEBUG] [.p.i.PersistenceModelActivator:23   ] - Registered 'persistence' configuration parser
18:13:16.150 [DEBUG] [.c.t.i.TransformationActivator:38   ] - Transformation Service has been started.
18:13:16.234 [DEBUG] [m.internal.MultimediaActivator:34   ] - Multimedia I/O bundle has been started.
18:13:16.262 [DEBUG] [.s.i.DiscoveryServiceActivator:27   ] - Discovery service has been started.
18:13:16.282 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:93   ] - mDNS service has been started
18:13:16.302 [DEBUG] [.io.transport.mqtt.MqttService:123  ] - Starting MQTT Service...
18:13:16.337 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:53   ] - Service Discovery initialization completed.
18:13:16.417 [DEBUG] [.i.internal.ItemModelActivator:24   ] - Registered 'item' configuration parser
18:13:16.531 [DEBUG] [o.o.c.i.items.ItemRegistryImpl:137  ] - Item provider 'GenericItemProvider' has been added.
18:13:17.323 [DEBUG] [.o.m.s.i.SitemapModelActivator:23   ] - Registered 'sitemap' configuration parser
18:13:17.395 [DEBUG] [io.rest.internal.RESTActivator:33   ] - REST API has been started.
18:13:18.456 [INFO ] [penhab.io.rest.RESTApplication:144  ] - Started REST API at /rest
18:13:18.457 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66   ] - Registering new service _openhab-server._tcp.local. at port 8080
18:13:23.944 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66   ] - Registering new service _openhab-server-ssl._tcp.local. at port 8443
18:13:25.985 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'default.sitemap'
18:13:26.137 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'test.items'
18:13:26.178 [DEBUG] [i.internal.GenericItemProvider:154  ] - Processing binding configs for items from model 'test.items'
18:13:26.184 [DEBUG] [i.internal.GenericItemProvider:133  ] - Read items from model 'test.items'
18:13:26.601 [INFO ] [.o.u.w.i.servlet.WebAppServlet:80   ] - Started Classic UI at /classicui/openhab.app
18:13:26.827 [DEBUG] [.r.internal.RuleModelActivator:42   ] - Registered 'rules' configuration parser
18:13:26.848 [DEBUG] [m.r.internal.engine.RuleEngine:77   ] - Started rule engine
18:13:29.633 [DEBUG] [.b.m.internal.MilightActivator:34   ] - Milight binding has been started.
18:13:29.672 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'Light_Party2 (Type=SwitchItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:13:29.676 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'Light_Party (Type=ColorItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:13:29.677 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'DiscoMode (Type=DimmerItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:13:29.677 [DEBUG] [i.internal.GenericItemProvider:341  ] - Start processing binding configuration of Item 'DiscoSpeed (Type=DimmerItem, State=Uninitialized)' with 'MilightGenericBindingProvider' reader.
18:13:36.237 [INFO ] [c.internal.ModelRepositoryImpl:80   ] - Loading model 'test.rules'
18:14:01.057 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:14:01.058 [DEBUG] [.o.b.m.internal.MilightBinding:612  ] - milight: sendOn
18:14:01.058 [DEBUG] [.o.b.m.internal.MilightBinding:786  ] - milight: messageBytes to transform: '22:00:55'
18:14:01.059 [DEBUG] [.o.b.m.internal.MilightBinding:778  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:14:04.017 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:14:04.017 [DEBUG] [.o.b.m.internal.MilightBinding:664  ] - milight: sendOff
18:14:04.018 [DEBUG] [.o.b.m.internal.MilightBinding:786  ] - milight: messageBytes to transform: '21:00:55'
18:14:04.018 [DEBUG] [.o.b.m.internal.MilightBinding:778  ] - Sent packet '21:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:14:08.118 [DEBUG] [.o.b.m.internal.MilightBinding:96   ] - milight: item is of type brightness
18:14:08.118 [DEBUG] [.o.b.m.internal.MilightBinding:612  ] - milight: sendOn
18:14:08.118 [DEBUG] [.o.b.m.internal.MilightBinding:786  ] - milight: messageBytes to transform: '22:00:55'
18:14:08.119 [DEBUG] [.o.b.m.internal.MilightBinding:778  ] - Sent packet '22:00:55' to bridge 'bridge1' (192.168.178.40:8899)
18:14:30.058 [DEBUG] [.o.b.m.internal.MilightBinding:170  ] - milight: item is of type rgb
18:14:30.059 [DEBUG] [.o.b.m.internal.MilightBinding:728  ] - milight: sendColor
18:14:30.059 [DEBUG] [.o.b.m.internal.MilightBinding:786  ] - milight: messageBytes to transform: '20:b:55'
18:14:30.060 [DEBUG] [.o.b.m.internal.MilightBinding:778  ] - Sent packet '20:b:55' to bridge 'bridge1' (192.168.178.40:8899)
18:14:37.019 [DEBUG] [.o.b.m.internal.MilightBinding:170  ] - milight: item is of type rgb
18:14:37.019 [DEBUG] [.o.b.m.internal.MilightBinding:728  ] - milight: sendColor
18:14:37.020 [DEBUG] [.o.b.m.internal.MilightBinding:786  ] - milight: messageBytes to transform: '20:d:55'
18:14:37.020 [DEBUG] [.o.b.m.internal.MilightBinding:778  ] - Sent packet '20:d:55' to bridge 'bridge1' (192.168.178.40:8899)
18:14:49.341 [INFO ] [penhab.io.rest.RESTApplication:160  ] - Stopped REST API
18:14:49.341 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:80   ] - Unregistering service _openhab-server._tcp.local. at port 8080
18:14:51.345 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:80   ] - Unregistering service _openhab-server-ssl._tcp.local. at port 8443

I also did already a comparison of the milight related parts of both logs milight_compare.pdf (21.3 KB)

It is obvious that there a are fewer command sent to the bridge with the 1.8.3 binding.
I hope this is enough information to have a look at the binding code. I’m not really a java programmer to do this on my one.
Thanks for your support.

23

Thank for this absolutely great summary.
I will have to take a bit time to analyse.

24

Thanks.

Sure. Just let me know if there’s something I can do…

Mfg Sebastian

25

Hi, thanks for providing the binding,https://github.com/openhab/openhab/wiki/Milight-Binding
So I decided to try out Milight, and will now try to order some lights.

So if I read this thread correctly I can not use this controller for ledstrip?

blob.jpg1000×1000 138 KB

Also wall switches does not work?

blob.jpg800×800 69.5 KB

https://www.aliexpress.com/item/Mi-light-2-4G-4-Zone-Touch-Screen-RGB-RGBW-Led-Controller-Wireless-RF-Remote-Controller/32711904507.html?spm=2114.01010208.3.19.oE1yX6&ws_ab_test=searchweb0_0,searchweb201602_2,searchweb201603_1&btsid=7d71c4ec-44f2-4672-8354-73dcce024fb3

But this should work right?

blob.jpg960×605 123 KB

Dont I need a hub aswell?
https://www.aliexpress.com/item/Mi-light-Wifi-Controller-Wi-Fi-Controller-Hub-Wifi-Adaptor-for-Milight-Smart-Remote-Control-Bulbs/1000001048989.html?spm=2114.01010208.3.33.M3Vbyw&ws_ab_test=searchweb0_0,searchweb201602_2,searchweb201603_1&btsid=6baf35b5-4265-43f1-be5a-2206c104a8b4

blob.jpg800×438 86.7 KB

If I read you all correct, then milight is a good and cheaper alternative to Phillips hue right?

26

The Binding was never intended to work with LED-Strips, so no, you can’t

No, as the is only a one way communication possible. openHAB is not able to read the state of any MiLight.

Yes.

Of course. This is the part openHAB talks to :slight_smile:

27

Thanks, for the feedback. Pitty that the ledstrip can not be used:(
Are you satisfied with the quality and color representation of milight?

I have tried to google a little bit to see if there is some api out there that reads data send from the hub, so far no luck:(




https://hackaday.io/project/5888/logs

28

Any news regarding this issue?

29

@skatun
I bought the MiLights cause of the price, meanwhile, I switched over to HUE.

@hannibal29
Sorry mate, did not find time for it. Day-Job keeps me too busy. Hope to find some time soon.

Best
Hans-Jörg

1 Like
30

IMO this doesn’t solve the problem. The bulbs nor the hub report their state so you’ll never know (without a visual check) whether the bulbs actually received your command (even if you know the command that was sent from the hub).

I have a couple of MiLights myself, there were good for a while but I would recommend something with two-way communication like Phillips Hue or LIFX etc. I didn’t find the RGB bulbs that great in terms of white brightness either.

31

So it seems like i should skip investing my money in milights and rather go for hue or lifx, even though they are expensive…

32

I’m having the exact same problem as the original poster in this thread, I can’t seem to communicate with the hub even though I have identical settings to his. Does anyone have a copy of his items, sitemap, and cfg. I was able to make this work on home assistant but I much prefer openHab. If there is any info you want let me know, I’ll be more than happy to supply whatever. Thanks in Advance.

33

What is the reason why you can’t control LED stripes?
Is there a technical limitation?
I hoped that I can use openhab as a single system to control my home automation and the stripes too.
Is it planned to include the stripes in our binding?

best regards
Frank

34

That LED strip controller should work fine, it uses the same protocol as the RGBW lightbulbs. I have a couple here.

35

There is a new milight variant (iBox) which finally has a confirmation for send commands. That doesn’t help anyone with the old bulbs of course.

36

Hi…

I want to share something that stumbled me, and is VERY ambuguous in the openhab2 instructions here:

http://docs.openhab.org/addons/bindings/milight1/readme.html

Here was my start:
-Integrated the Mighlight into my network just fine, plus a remote working the bulb- Everything great, can get to the http://ipofcontroller web page to configure.
-Tried manually to set it up using the method described in the openhab readme, via milight.cfg and a things.
-kept running into the dead end “cannot delegate to item” error message nonsense in the logs
-as I usually do, I stared simple with just an on off switch, so I had this in my items file:

{channel=“milight:rgbLed:ACCF2391469A:7”}

and this part of the instructions implied I could do that:
Switch Light_Groundfloor {milight=“bridge1;0”} #Switch for all white bulbs on bridge1

by just changing it to:
{channel=“milight:rgbLed:ACCF2391469A:7”}

…because this line in the instructions implies that is the correct id:

Dimmer RGBW_LivingroomB {milight=“bridge1;7;brightness;27”} #Dimmer changing brightness for RGBW bulb1 on bridge1 with 27 dimming steps

and logically if this is for all white bulbs on bridge 1

Switch Light_Groundfloor {milight=“bridge1;0”} #Switch for all white bulbs on bridge1

this should be for RGB bulb 1 on bridge 1:

Switch Light_Groundfloor {milight=“bridge1;7”}

So I gave up for a while, and tried the autodetection on a seperate installation. Everything worked ok from the paperUI including on/off. What could be wrong with what I was doing?

I stumbled onto this guy:

Who put a note that I found NOWHERE ELSE:

“Note: the MiLight binding does not expose and on/off state for the
bulbs, rather you need to define a switch for the brightness to control
the on/off and a dimmer for the brightness adjustment both using the
same channel”

So this is the .items file for on/off:
{channel="milight:rgbLed:ACCF2391469A:7:ledbrightness}

The long and short is that just stopping at the bulb id is not the “on/off” as the instructions imply! Maybe that works for white bulbs, but I dont have any to try it.

…and by the way, the RGB bulbs DO support changing their saturation.

So the README is a good start but not very thorough…

Hope it helps save someone some time!

37

Out of your sample configs it looks like you are mixing configuration of milight 1.x and 2.x binding versions.

38

Hey @jimkernsjr,

thanks for sharing this. Just a few additional notes:

  • The documentation of the first milight binding will probably not be updated to point out that there exists a new binding.
  • The configuration of both bindings is quite different.
  • I provided the successor of the first milight binding, but personally I only use the PaperUI way of configuring. I’m really bad at keeping the readme up to date, to be honest. Openhab should stop offering two totally different ways of configuration, in my opinion, but that’s just me.

@hmerk:

39

@David_Graeff
Don’t really know, but will check and provide a PR to mark it as legacy.

40

Hi,

Do you work with RGB or RGBW bulb? As far as I remember, the channels are
different.

41

@David_Graeff

PR to mark MiLight1 binding as legacy created :