- Remove back cover with philips scredriver and instert provided battery
- In home assistant select a ZHA always-on zigbee device - such as a powered light or signal repeater in the same room the shortcut button will end up in
- Select "Add device via this device"
- Press the pair button 4 times on the back of the shortcut button
- Wait
- If using an On/Off switch and you want to bind it to a bulb for non-controller dependant control (i.e will work if home assistant is down)
For firmware versions 2.3.0.75 or greater.
Before version 2.3.075 The IKEA on/off switches only bind to zigbee groups After they only bind to individual devices: The most reliable method seems to be: In ZHA for me that process is bring up the device page for the switch, 3 dots the the right of the reconfigure button, manage ZigBee device, bindings.
- Consider updating to the latest firmware, as updates alter this functionality.
- Unbind the switch from all devices including the co-ordinator
- Unbind from all groups (check all clusters) <-- not sure if necessary
- Reconfigure the device from the ZHA UI <-- not sure if necessary.
Unbind from the coordinator again<-- not sure if necessary- Bind with the desired lights
- Re-bind with the coordinator (
This ensures the homeassistant UI acutally shows the state changes) - If the lights do not update their status in the UI when turned on or off by the switch, then click
RECONFIGURE DEVICE
for each light, making sure to refresh the page between each device
At software version number 2.3.015 they have 3 possible comands "on"
(triggered with a short press) "move_with_on_off"
triggered by a long press and "stop"
triggered by a release of a long press. Each message may also be duplicated many times (apparently this is within the zigbee spec, but you may have to control for it in node-red (this node is helpful)
Somewhere between 2.3.015 and 2.3.80 the gain the "off"
function which is tiggered by a double click. The message duplication is also improved ?completeley resolved?
- Device page of the device in question
- Manage Clusters
- "Basic (Endpoint id: 1, Id: 0x0000, Type: in)"
- Cluster Attributes -> "sw_build_id (id: 0x4000)"
- Click "Get Zigbee Attribute"
- If device is battery powered, trigger it somehow
- The version should appear in the "Value" box
I think updating software is generally a good idea, but IKEA often changes functionality with little warning and so it may break some of you systems. ZHA way of managing updates (if enables) is to silently update your devices in the background. Which may mean that things can silently break.
This post on reddit by u/Wwalltt is currently a good overview of how updates work in ZHA
Version info is as follows from the IKEA server (no changelog): http://fw.ota.homesmart.ikea.net/feed/version_info.json
Tradfri changelog https://ww8.ikea.com/ikeahomesmart/releasenotes/releasenotes.html
Or official docs are a little better than they were: https://www.home-assistant.io/integrations/zha/#ota-firmware-updates
- As of 2.3.075 or later on switches they go from being able to bind groups and not devices to the opposite
- For the shortcut buttons as of 2.3.0.75, they gain the
off
command on double press and the duplicaiton problem is fixed.
In ZHA:
- Ensure you have OTA updates enabled in ZHA (see above)
- In my experience devices begin updating soon after joining the network anyway - you can skip to step 8/9 to check
- Select the device you want to update
- Select
Manage Clusters
- Select
Ota (Endpoint id: 1, Id: 0x0019, Type: out)
- In the
Cluster Commands
drop-down, (not Cluster Attributes) selectimage_notify (id: 0x0000)
- Click
ISSUE ZIGBEE COMMAND
whilst waking the device - Wait One device took approx 2 hours(!)
- there is no obvious way to tell if the update has started except to SSH into the HA and run
tail -f home-assistant.log | egrep zigpy
which should show an increasing upgrade percentage if you have DEBUG level logging for zigpy/ZHA.
- there is no obvious way to tell if the update has started except to SSH into the HA and run
- You can track the progress with
tail -f home-assistant.log | egrep "OTA upgrade progress:"
Same for me. Thats probably the reason the author advises us to use the switch with the bulbs directly and only have light updates in HA.