Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
Long time coming, it's finally here and working well. You can now control your ULTI Zigbee Switches from Can2Go. Actually, by this method, you will be able to control any Zigbee device that supports the Zigbee Cluster Library. (Yes, that pretty much includes most of the LifeSpace stuff in APAC and EMEA).
What will you need to do this:
-- 24V. Power Supply
-- 1 UN2/SSL/Can2Go/MPM (or whatever you want to call it)
-- At least one ULTI Zigbee Switch connected to some sort of lighting
First you need to create the Zigbee network on the UN2. Login to the UN (default is admin/admin), select it in the tree, then on the right click on Zigbee Configuration.
You can use the settings bellow and don't worry about the Extended Network ID as we'll overwrite it anyway.
A few comments/highlights:
- Channel: in order for your UN to be compatible with the Zigbee devices out of Schneider EMEA (Denmark), in other words all the eco-system around Wiser, the channel must be one of the following: 11, 15, 20 or 25
- Node Type: must be set as the Coordinator
- Permit Join Broadcast: must be checked ONLY when you are adding devices. Once you are done adding devices to your network, remember to uncheck it. I repeat: KEEP IT UNCHECKED! (unless you are adding new devices to your Zigbee network)
- PAN ID: can't quite remember the limitation, but keep the number low, otherwise adding an SE8000 might be painful (that would be worth another article maybe)
- Stack Profile: select 2 - Zigbee Pro
- Security Profile: make sure to select Home Automation
- Trust Center Link Key: never changed it, not sure what it's for (maybe someone can enlighten us?)
Awesome! Click Save and the network status should change to "formed".
Next, you need to create a Lua script in order to control our ULTI devices.
Click the Add Objects button (first button in the toolbar). In the new windows, set the Filter to "Lua Program". Finally add a Lua Script.
First of all, we'll need to reset the Extended Pan Id in our script.
In order for some of the Schneider products to work with your UN2, they need to have a specific extended Pan Id. It needs to be 0x10,0x5E,0x01,0x04,0x45,0x48,0xYY,0xYY where YY can be any valid hexadecimal value.
So in Lua, it comes to:
if PG1_Init == nil then
ME.ZBC1_Pan_Ext.value = string.char(0x5E,0xD3,0x48,0x45,0x04,0x01,0x5E,0x10)
...
Let's look at the script in details:
1. Declaration
lights = {
{"00124B0001CA0F05", 11, "BV2"}, -- 2-Gang Dimmer
{"00124B00017B19C0", 10, "BV4"}, -- 1-Gang Switch
{"00124B0002925A40", 10, "BV6"} -- 2-Gang Switch
}
This is where you declare all the lights that you want to connect to and control. Each light has three parameters:
- The Extended Id which is clearly marked on your switch. It can also be marked as a MAC Address. It's a long serie of numbers. Note that if you are working on a device where you do not have that number, you can start the Com Log (right click in the tree in Building Expert, and click on Show Com Log. Then check the Zigbee Driver and Stack. As you will power up a new device it will "declare" itself to the network and you can read the extended id there.
- The Destination Id. It can either be 10 or 11 and represents the Channel Id of your switch. If you have a 2 gang switch, then Channel 1 (first gang of your switch) will be represented by 10 and the second one by 11.
- Finally declare a Binary Value that will store the status of your switch.
2. The Lua functions
Next you will need 3 main commands:
- receiveCommands: when the switch wants to communicate with the concentrator, it will send a message. This method will ensure to read and deal with this message. For example, if the user goes and press the switch (manually), the switch will send its status back to the concentrator and be received by this function
- getLightStatus: this function will actually ask the status of the lights. Are you on or off?
- processLight: this will check whether the user has asked to changed the status of a light and will send the command to the switch. Note that it is also used as a generic function to call the two previous commands
3. Start up
At startup, you will have a few declarations. The status array is used to store the current values of the lights while the lastToggle keeps the timestamp of the last time it was turned on/off. This is used to ignore some of the received commands for the lights as all the messaging is asynchronous.
Finally, to make it look nicer, you can actually create a Dashboard using a switch and linking it to your BV value.
As you will notice, the commands are using the standard Zigbee Cluster Library (ZCL). For on/off, we are using the on/off cluster (0x0006). In order to do dimming, you will need to implement another cluster (my guess is the Level Control Cluster?). We are currently trying it and will keep you updated! Just like this post for an update! 🙂
Final thing, you will need to join your device/switch to the Zigbee network. To do so, it's real easy, in the Zigbee Configuration of your UN2, check the "Permit Join Broadcast" box. Then on your switch press the Prog button. Wait a few seconds. The small light indicator on your switch should change from orange to green. Once this is done, make sure to uncheck "Permit Join Broadcast" and if the light is still green on the switch, close the Zigbee network by pressing the Prog button again.
That's it!
If you have any question/comment, don't hesitate!
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.