I don’t think it’s a hub model problem, v2 should work fine.
The process that you see when you execute an On command in the app has three stages for different networks and it is convenient to identify where the problem may be:
1. External Internet network:
- when you press On in the app the command is sent to the smartthings cloud
- The cloud sends the On command to the corresponding hub.
- The button begins to rotate, starting a timer waiting for the On state in response. If the response is not received within the time set in the App, then a network error appears and the App status returns to Off.
2. Local network and zigbee:
- The Hub receives the On command via internet, router.
- ElHub forwards it already decoded to the corresponding driver.
- The driver converts the received On command into a zigbee On command sent to the destination device.
- The device receives the On command and executes it
- The device sends one or more messages to the hub with the acknowledgment of receipt of the message and the final status of the device On and level.
- The hub receives the message from the device and sends it decoded to the driver
- The driver interprets the message and emits the device status event to the platform.
3. External Internet network
- The smartthings cloud receives the event and sends it to the app
- The App will update the On and level status of the device.
To determine which process the delays may be in, you can run local routines, it does not need external internet network, and see if it works better or the same.
If it works just as bad it could be:
- Your Wi-Fi network is interfering with your Zigbee network: You can try changing the channel on your Wi-Fi network or your Zigbee network.
- Your zigbee network loses messages due to saturation or devices that are far from the hub and make several hops. It may be that the 15 bulbs are acting as a repeater for each other, producing excessive Zigbee messages and overlapping or losing them.
This process is for one bulb, multiply this by the number of bulbs you want to control simultaneously.
There is a problem with some hub firmware, which can only be seen in the CLI:
- When the device sends the response message to the Hub with the status of the corresponding cluster, it also sends two useless ZDO messages from the basic cluster. We started seeing this in the first 52.x versions and then they removed it, but some devices do not reconfigure themselves again and I have had to re-pair each device so that it stops sending those two useless ZDO messages that could increase traffic. the zigbee network in some cases.