I created a new plugin to control IKEA Tradfri light bulbs and outlets using an IKEA Tradfri Gateway. You can:
Switch light bulbs on and off
Set the dimming level
Set the color temperature for lights that support it
Switch outlets on and off
To a limited extend, it also updates the status of Tradfri devices.
It unfortunately does not use Veras Zigbee interface, but requires an IKEA Tradfri Gateway. In contrary to ALTHue, it does not work with nor support Philips Hue.
I posted this plugin in the openLuup category, because this plugin for now only works on a Linux system running openLuup. The reason is that Tradfi Gateway communication is based on CoAP. The plugin requires luacoap. Iām working on getting this to work on Vera as well, but that is rather difficult because its Linux distribution and openssl in particular is very outdated.
Installation instructions (as available in the Github repo):
Copy or upload D_TradfriGW.json , D_TradfriGW.xml , I_TradfriGW.xml and L_TradfriGW.lua.
Get D_DimmableLight1.xml , D_DimmableRGBLight1.xml and D_BinaryLight1.xml files plus the .json variants from your Vera and copy or upload these when you use openLuup .
Add a new device by clicking Create on the Devices page. Use D_TradfriGW.xml as the definition filename and I_TradfriGW.xml as the implementation filename.
Wait for the new device to appear.
Configure the IP of your Tradfri Gateway in the ip attribute.
Lookup the SecurityCode on the bottom for your Tradfri Gateway and enter the code in the corresponding variable of the created device
Restart Luup and your devices should appear after a short while. The SecurityCode attribute will be cleared after successful authentication to the gateway.
You will only see light bulbs and outlets. Other devices, such as remotes or motion sensors can be detected by the plugin, but due to limitations (or design decisions) by IKEA, it is not possible to get state notifications from these devices. It therefore has no use to add them as device in Vera or openLuup.
Device that are not supported (I might add support in the future):
Itās been a while! Thanks for that contribution. I must say that I know nothing about COaP. This sounds like an alternative to, say, MQTT, in the HA context. I struggle to see why they chose this rather than plain HTTP (albeit the protocol is lighter-weight.)
It is what it is, but CoAP has some advantages. Itās server is probably more lightweight than MQTT. It supports observer patterns (would also be possible with WebSockets). And it uses UDP. CoAP wouldnāt be that much of an issue if only the Vera toolchain was a bit less ancient. Thatās where my main struggle is.
I donāt own any either⦠Iām not so familiar with openluup and programming either⦠The Fyrtur is on my future list so if I buy them I defenently will PM you⦠Maybe someone in The Swedish FB vera forum has⦠I can give it a tryā¦
Symfonisk is controlled by the SONOS plugins⦠I have one.
I am thinking more broadly of using a unified zigbee network instead of two (one on vera, one on the philibs hue hub) which would mean that it would have to support both the LL and HA stacks. It seems like Home Assistant is capable of doing just that with the zha component or zigbee2mqtt. Not sure if it could be ported to openluup.
@rafale77 there is actually a smal āTrĆ„dfriā remote that can be used for controlling the SONOS speakers through the TrĆ„dfri GW. It can control any sonos speaker.
I asked to include your package on the repo. Maybe we could get it in the coming weeks. I want to buy their blinds as well, so a native integration is interesting to me as well.
I had a cross compilation setup prepared for a configuration that was probably similar to 7.0.29 firmware. In the latest firmware (7.0.31) multiple things have been updated, which is great. Drawback is that I can start all over again.
Besides that, several bugs were discovered in both the plugin and the required library (thanks to some users that are trying to use the plugin on openLuup). Development and specifically debugging is significantly easier or a āregularā pc-based linux installation.
Multiple enhancements have been added to the plugin since my first post, such as (experimental) support for blinds, storing device names used in openLuup on Tradfri as well and multiple small fixes. But unfortunately you can still only use it on openLuup and it is not stable yet.
I already wrote a blind (phun intented) implementation for the Fyrtur devices. A recent version of the plugin should detect the blinds. Iām curious to see the results of that lucky shot.
You have an old version of the plugin. Be sure to get the latest files from Github.
You should see a āDebuggingā (switch it on!) and āUpdate devicesā (set to āpollā) switch.