question on optimizing groups

Moderator: leecollings

Post Reply
snellejellep
Posts: 241
Joined: Tuesday 16 May 2017 13:05
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: The Neterlands
Contact:

question on optimizing groups

Post by snellejellep »

Hi all,

i have a group which controls 8 philips hue spot lights using zigbee2mqtt and the plugin.
now i have the following issue(s):
- the lights do not turn on all at once, they turn on one after the other and it takes about 3 seconds for them all to turn on. using the hue bridge they all turned on at once which makes this a strange thing because i would assume that they all would be activated at once using a group in domoticz.
- sometimes not all of the lights turn on or off using the group. occasionally the group forgets one which is really frustrating because then none of my scripts work since the group state is then mixed and i use the on/off states. also one light will not turn on or will stay on for no reason.

any suggestions on how to fix this issue?

i am using V4.11506
raspberry pi | xiaomi vacuum | yeelight | philips hue | zwave | ubiquiti unifi | harmony | sonoff | zigbee2mqtt | https://www.youtube.com/channel/UC2Zidl ... m1OLuNldfQ
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: question on optimizing groups

Post by waaren »

snellejellep wrote: Monday 25 November 2019 21:20 I have a group which controls 8 philips hue spot lights using zigbee2mqtt and the plugin....
Did some tests with 9 Phillips Hue lights on V4.11533 (dzVents 2.5.1)
  • domoticz Group 0.7 seconds
  • domoticz Scene 0.6 seconds
  • dzVents script 0.2 seconds
Measured times are from the domoticz log because I have no tools to measure the time on the lights themselves.
Would be interresting to see the same type of data with zigbee2mqtt.

test script below.

Code: Select all

--[[
        group on /off 0.7 seconds
        scene on / off 0.6 seconds
        dzVents on / Off 0.2 seconds
]]--

return 
{
    on =
    {  
        devices = { 'hueTrigger' },
    },
    
    logging = { level = domoticz.LOG_DEBUG },
    
    execute = function(dz, item)
         _G.logMarker =  _G.moduleLabel
        local myGroup = {
                            'Hue slaapkamer',
                            'Kantoor hanglamp',
                            'LM46 staand rechts',
                            'LM46 tafel links',
                            'LM46 tafel rechts',
                            'LM46 staand links',
                            'LM46 lightstrip',
                            'HueGo',
                            'staande kantoorlamp',
                        }
                        
        for _, deviceName in ipairs(myGroup) do
            if item.active then dz.devices(deviceName).switchOff()
            else dz.devices(deviceName).switchOn() end     
        end    
    end     
}
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
snellejellep
Posts: 241
Joined: Tuesday 16 May 2017 13:05
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: The Neterlands
Contact:

Re: question on optimizing groups

Post by snellejellep »

waaren wrote: Monday 25 November 2019 22:30
Measured times are from the domoticz log because I have no tools to measure the time on the lights themselves.
Would be interresting to see the same type of data with zigbee2mqtt.
my log shows this:

Code: Select all

2019-11-27 16:21:30.216 Activating Scene/Group: [Tuinkamer licht]
2019-11-27 16:21:30.228 Activating Scene/Group Device: Tuinkamer spot 1 (On)
2019-11-27 16:21:30.281 Activating Scene/Group Device: Tuinkamer spot 2 (On)
2019-11-27 16:21:30.334 Activating Scene/Group Device: Tuinkamer spot 3 (On)
2019-11-27 16:21:30.386 Activating Scene/Group Device: Tuinkamer spot 4 (On)
2019-11-27 16:21:30.438 Activating Scene/Group Device: Tuinkamer spot 5 (On)
2019-11-27 16:21:30.537 Activating Scene/Group Device: Tuinkamer spot 6 (On)
2019-11-27 16:21:30.591 Activating Scene/Group Device: Tuinkamer spot 7 (On)
2019-11-27 16:21:30.645 Activating Scene/Group Device: Tuinkamer spot 8 (On)
so that is a second of delay which is not much so it seems to be in the communication between domoticz and zigbee2mqtt where the slow down occurs?
raspberry pi | xiaomi vacuum | yeelight | philips hue | zwave | ubiquiti unifi | harmony | sonoff | zigbee2mqtt | https://www.youtube.com/channel/UC2Zidl ... m1OLuNldfQ
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: question on optimizing groups

Post by waaren »

snellejellep wrote: Wednesday 27 November 2019 16:23 so that is a second of delay which is not much so it seems to be in the communication between domoticz and zigbee2mqtt where the slow down occurs?
Could be, I don't have zigbee2mqtt and don't know if you can switch on debug log there ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
snellejellep
Posts: 241
Joined: Tuesday 16 May 2017 13:05
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: The Neterlands
Contact:

Re: question on optimizing groups

Post by snellejellep »

waaren wrote: Wednesday 27 November 2019 17:35 Could be, I don't have zigbee2mqtt and don't know if you can switch on debug log there ?
yes, zigbee2mqtt has a debug mode, when all goes well i get this:

Code: Select all

2019-11-27 18:12:41.452 (zigbee2mqtt1) MqttClient::ping
2019-11-27 18:12:43.733 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":81,"g":0,"m":2,"r":0,"t":174,"ww":174}
2019-11-27 18:12:43.735 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f2e/set ({"brightness": 255, "color_temp": 341, "state": "ON"})
2019-11-27 18:12:43.786 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":75,"g":0,"m":2,"r":0,"t":180,"ww":180}
2019-11-27 18:12:43.794 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880102eb0546/set ({"brightness": 255, "color_temp": 352, "state": "ON"})
2019-11-27 18:12:43.845 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":72,"g":0,"m":2,"r":0,"t":183,"ww":183}
2019-11-27 18:12:43.846 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880102eb09e5/set ({"brightness": 255, "color_temp": 358, "state": "ON"})
2019-11-27 18:12:43.917 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":78,"g":0,"m":2,"r":0,"t":177,"ww":177}
2019-11-27 18:12:43.920 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103517b16/set ({"brightness": 255, "color_temp": 347, "state": "ON"})
2019-11-27 18:12:43.988 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":84,"g":0,"m":2,"r":0,"t":171,"ww":171}
2019-11-27 18:12:43.991 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f7d/set ({"brightness": 255, "color_temp": 335, "state": "ON"})
2019-11-27 18:12:43.994 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb0546 {'brightness': 255, 'color_temp': 352, 'state': 'ON'}
2019-11-27 18:12:44.074 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":81,"g":0,"m":2,"r":0,"t":174,"ww":174}
2019-11-27 18:12:44.074 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f53/set ({"brightness": 255, "color_temp": 341, "state": "ON"})
2019-11-27 18:12:44.075 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":85,"g":0,"m":2,"r":0,"t":170,"ww":170}
2019-11-27 18:12:44.075 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f7f/set ({"brightness": 255, "color_temp": 333, "state": "ON"})
2019-11-27 18:12:44.127 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":74,"g":0,"m":2,"r":0,"t":181,"ww":181}
2019-11-27 18:12:44.128 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f5e/set ({"brightness": 255, "color_temp": 354, "state": "ON"})
2019-11-27 18:12:44.303 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f2e {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:12:44.828 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103517b16 {'brightness': 255, 'color_temp': 347, 'state': 'ON'}
2019-11-27 18:12:44.952 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb0546 {'brightness': 255, 'color_temp': 352, 'state': 'ON'}
2019-11-27 18:12:45.158 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb09e5 {'brightness': 255, 'color_temp': 358, 'state': 'ON'}
2019-11-27 18:12:45.261 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f7d {'brightness': 255, 'color_temp': 335, 'state': 'ON'}
2019-11-27 18:12:45.392 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f53 {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:12:46.039 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f5e {'brightness': 255, 'color_temp': 354, 'state': 'ON'}
2019-11-27 18:12:46.193 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103517b16 {'brightness': 255, 'color_temp': 347, 'state': 'ON'}
2019-11-27 18:12:46.270 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb09e5 {'brightness': 255, 'color_temp': 358, 'state': 'ON'}
2019-11-27 18:12:46.390 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f7d {'brightness': 255, 'color_temp': 335, 'state': 'ON'}
2019-11-27 18:12:46.510 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f53 {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:12:46.669 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f7f {'brightness': 255, 'color_temp': 333, 'state': 'ON'}
2019-11-27 18:12:46.756 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f5e {'brightness': 255, 'color_temp': 354, 'state': 'ON'}
but when it goes wrong i get this:

Code: Select all

2019-11-27 18:14:29.064 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":81,"g":0,"m":2,"r":0,"t":174,"ww":174}
2019-11-27 18:14:29.065 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f2e/set ({"brightness": 255, "color_temp": 341, "state": "ON"})
2019-11-27 18:14:29.116 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":75,"g":0,"m":2,"r":0,"t":180,"ww":180}
2019-11-27 18:14:29.117 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880102eb0546/set ({"brightness": 255, "color_temp": 352, "state": "ON"})
2019-11-27 18:14:29.168 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":72,"g":0,"m":2,"r":0,"t":183,"ww":183}
2019-11-27 18:14:29.170 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880102eb09e5/set ({"brightness": 255, "color_temp": 358, "state": "ON"})
2019-11-27 18:14:29.280 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":78,"g":0,"m":2,"r":0,"t":177,"ww":177}
2019-11-27 18:14:29.282 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103517b16/set ({"brightness": 255, "color_temp": 347, "state": "ON"})
2019-11-27 18:14:29.339 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":84,"g":0,"m":2,"r":0,"t":171,"ww":171}
2019-11-27 18:14:29.341 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f7d/set ({"brightness": 255, "color_temp": 335, "state": "ON"})
2019-11-27 18:14:29.341 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb0546 {'brightness': 255, 'color_temp': 352, 'state': 'ON'}
2019-11-27 18:14:29.417 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":81,"g":0,"m":2,"r":0,"t":174,"ww":174}
2019-11-27 18:14:29.417 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f53/set ({"brightness": 255, "color_temp": 341, "state": "ON"})
2019-11-27 18:14:29.418 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":85,"g":0,"m":2,"r":0,"t":170,"ww":170}
2019-11-27 18:14:29.418 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f7f/set ({"brightness": 255, "color_temp": 333, "state": "ON"})
2019-11-27 18:14:29.484 (zigbee2mqtt1) onCommand: Set Color, level (100) Color:{"b":0,"cw":74,"g":0,"m":2,"r":0,"t":181,"ww":181}
2019-11-27 18:14:29.487 (zigbee2mqtt1) MqttClient::publish zigbee2mqtt/0x0017880103516f5e/set ({"brightness": 255, "color_temp": 354, "state": "ON"})
2019-11-27 18:14:29.489 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f2e {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:14:29.643 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb0546 {'brightness': 255, 'color_temp': 352, 'state': 'ON'}
2019-11-27 18:14:29.763 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb09e5 {'brightness': 255, 'color_temp': 358, 'state': 'ON'}
2019-11-27 18:14:30.106 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f7d {'brightness': 255, 'color_temp': 335, 'state': 'ON'}
2019-11-27 18:14:30.264 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103517b16 {'brightness': 255, 'color_temp': 347, 'state': 'ON'}
2019-11-27 18:14:30.335 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f2e {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:14:30.401 (zigbee2mqtt1) MQTT message: zigbee2mqtt/bridge/log {'meta': {'friendly_name': '0x0017880103516f7f'}, 'message': "Publish 'set' 'brightness' to '0x0017880103516f7f' failed: 'Error: Data request failed with error: 'No network route' (205)'", 'type': 'zigbee_publish_error'}
2019-11-27 18:14:30.401 (zigbee2mqtt1) MQTT message: zigbee2mqtt/bridge/log {'meta': {'friendly_name': '0x0017880103516f5e'}, 'message': "Publish 'set' 'brightness' to '0x0017880103516f5e' failed: 'Error: Data request failed with error: 'No network route' (205)'", 'type': 'zigbee_publish_error'}
2019-11-27 18:14:30.453 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x00158d000200ce7c {'battery': 100, 'illuminance': 0, 'linkquality': 42, 'voltage': 3015, 'occupancy': False}
2019-11-27 18:14:30.562 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f53 {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:14:30.631 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f7d {'brightness': 255, 'color_temp': 335, 'state': 'ON'}
2019-11-27 18:14:30.702 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880102eb09e5 {'brightness': 255, 'color_temp': 358, 'state': 'ON'}
2019-11-27 18:14:31.248 (zigbee2mqtt1) MQTT message: zigbee2mqtt/bridge/log {'meta': {'friendly_name': '0x0017880103516f7f'}, 'message': "Publish 'set' 'color_temp' to '0x0017880103516f7f' failed: 'Error: Data request failed with error: 'No network route' (205)'", 'type': 'zigbee_publish_error'}
2019-11-27 18:14:31.349 (zigbee2mqtt1) MQTT message: zigbee2mqtt/bridge/log {'meta': {'friendly_name': '0x0017880103516f5e'}, 'message': "Publish 'set' 'color_temp' to '0x0017880103516f5e' failed: 'Error: Data request failed with error: 'No network route' (205)'", 'type': 'zigbee_publish_error'}
2019-11-27 18:14:31.750 (zigbee2mqtt1) MQTT message: zigbee2mqtt/0x0017880103516f53 {'brightness': 255, 'color_temp': 341, 'state': 'ON'}
2019-11-27 18:14:32.997 (zigbee2mqtt1) MqttClient::ping
some sort of network thing seems to start acting up if i read this?
raspberry pi | xiaomi vacuum | yeelight | philips hue | zwave | ubiquiti unifi | harmony | sonoff | zigbee2mqtt | https://www.youtube.com/channel/UC2Zidl ... m1OLuNldfQ
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest