Yes that works. I donât have a login + password configured for my hub.
{"admin_username":"","admin_password":"","ce_pin":4,"csn_pin":15,"reset_pin":0,"led_pin":-2,"radio_interface_type":"nRF24","packet_repeats":160,"http_repeat_factor":1,"auto_restart_period":0,"mqtt_server":"10.0.0.153:1883","mqtt_username":"milighthub_zolder","mqtt_password":"MiLight1234","mqtt_topic_pattern":"milight/commands/:device_id/:device_type/:group_id","mqtt_update_topic_pattern":"","mqtt_state_topic_pattern":"milight/states/:device_id/:device_type/:group_id","mqtt_client_status_topic":"","simple_mqtt_client_status":false,"discovery_port":48899,"listen_repeats":3,"state_flush_interval":10000,"mqtt_state_rate_limit":600,"packet_repeat_throttle_sensitivity":0,"packet_repeat_throttle_threshold":200,"packet_repeat_minimum":3,"enable_automatic_mode_switching":true,"led_mode_wifi_config":"Fast toggle","led_mode_wifi_failed":"Fast blip","led_mode_operating":"Slow blip","led_mode_packet":"Flicker","led_mode_packet_count":3,"hostname":"milight-hub-zolder","rf24_power_level":"MAX","rf24_listen_channel":"HIGH","wifi_static_ip":"10.0.2.229","wifi_static_ip_gateway":"10.0.0.2","wifi_static_ip_netmask":"255.255.0.0","packet_repeats_per_loop":10,"home_assistant_discovery_prefix":"","wifi_mode":"n","default_transition_period":500,"rf24_channels":["HIGH"],"device_ids":[1,2,3,4,5],"gateway_configs":[],"group_state_fields":["state","level","hue","saturation","mode","color_temp","bulb_mode"],"group_id_aliases":{}}
Since Iâm using POWERFAILS_TO_MINDIM=true
Iâve found another issue. I have some non-MiLights turn ON or OFFwith these rules:
rule "Switch Lights Trapgat Beneden OFF"
when
Item gHalLightsLevel changed to OFF or
Item gHalLightsLevel changed to 0
then
//logInfo("tasmota.rules", "Tasmota Turning lights OFF")
gTrapgatBenedenLights.sendCommand(OFF)
end
rule "Switch Lights Trapgat Beneden ON"
when
Item gHalLightsLevel changed from OFF to ON or
Item gHalLightsLevel changed to 90 // or
//Item gOverloopLightsLevel changed from OFF to ON or
//Item gOverloopLightsLevel changed to 90
then
//logInfo("tasmota.rules", "Tasmota Turning lights ON")
gTrapgatBenedenLights.sendCommand(ON)
end
Somehow the lights first receive the command ON at level 73. Then they receive the command ON at level 0, and then again ON at level 73:
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/commands/0x2/rgb_cct/3', ... (25 bytes))
milight/commands/0x2/rgb_cct/3 {"state":"ON","level":73}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (61 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":0,"color_temp":296,"bulb_mode":"white"}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (61 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":0,"color_temp":296,"bulb_mode":"white"}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (61 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":0,"color_temp":296,"bulb_mode":"white"}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (62 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":73,"color_temp":296,"bulb_mode":"white"}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (62 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":73,"color_temp":296,"bulb_mode":"white"}
Client mosqsub/9236-openhab received PUBLISH (d0, q0, r0, m0, 'milight/states/0x2/rgb_cct/3', ... (62 bytes))
milight/states/0x2/rgb_cct/3 {"state":"ON","level":73,"color_temp":296,"bulb_mode":"white"}
NB the states are updated 3 times each because I have 3 hubs in my house. 1 on every floor.
Corresponding openhab.log:
2019-12-08 11:39:24.963 [ome.event.ItemCommandEvent] - Item 'Milight_ID0x2_G3_Level' received command 73
2019-12-08 11:39:24.987 [nt.ItemStatePredictedEvent] - Milight_ID0x2_G3_Level predicted to become 73
2019-12-08 11:39:25.018 [GroupItemStateChangedEvent] - gHalLightsLevel changed from 0.00000000 to 73.00000000 through Milight_ID0x2_G3_Level
2019-12-08 11:39:25.020 [vent.ItemStateChangedEvent] - Milight_ID0x2_G3_Level changed from 0 to 73
2019-12-08 11:39:25.222 [GroupItemStateChangedEvent] - gHalLightsLevel changed from 73.00000000 to 0.00000000 through Milight_ID0x2_G3_Level
2019-12-08 11:39:25.227 [vent.ItemStateChangedEvent] - Milight_ID0x2_G3_Level changed from 73 to 0
2019-12-08 11:39:25.822 [vent.ItemStateChangedEvent] - Milight_ID0x2_G3_Level changed from 0 to 73
2019-12-08 11:39:25.832 [vent.ItemStateChangedEvent] - Milight_ID0x2_G3_State changed from OFF to ON
2019-12-08 11:39:25.837 [GroupItemStateChangedEvent] - gHalLightsLevel changed from 0.00000000 to 73.00000000 through Milight_ID0x2_G3_Level
2019-12-08 11:39:25.843 [GroupItemStateChangedEvent] - gHalLights changed from OFF to ON through Milight_ID0x2_G3_State
2019-12-08 11:39:25.845 [GroupItemStateChangedEvent] - gBeganeGrondLights changed from OFF to ON through gHalLights
It happens too fast to see the MiLights flash, but the other lights do turn ON, OFF, ON. This doesnât happen when POWERFAILS_TO_MINDIM=false
.
Is this a bug?