These bulbs need CIE XY color space for adjustment. The current driver won't do it. However, these do work on Hue, but again the driver would need modification. What would actually be quite nice would be way to speak to the CoAP interface on the Trådfri bridge. That would allow for low cost Trådfri lighting in your home, without the higher cost of a Hue Bridge. Although the $20 difference isn't much, and arguably worth it. Hue already works with HE, the Hue Bridge has a much better interface, and support for many great third-party apps that can run on the bridge and the bridge can still interface with Hubitat without issue.
[Edit] This looks like an interesting project. I bought a Trådfri bridge in the AS-IS section for $25 CAD. I may toy with this at some point. I'm sure it would run on a Pi Zero W, but wouldn't be practical to buy a Pi just to do this. It's more one of those "have a Pi laying around doing nothing" kind of projects.
I'm not sure exactly where to put that. If I make it: import com.hubitat.zigbee.DataType, I get an error
"Expression [MethodCallExpression] is not allowed: com.hubitat.zigbee.DataType.isVariableLength(attrType)"
Taking out the "import" line makes the driver save, but the bulb doesn't appear to change color. Perhaps somebody with actual coding knowledge knows what's wrong here?
It's safe to take that line out. The reason the bulbs don't change color is the HE drivers are not compatible with the CIE XY color space the IKEA Trådfri bulbs use. There needs to be a mapping between HSL and XY that isn't there right now.
You can use them with Hue Bridge. They support the mapping, but the Hubitat Hue Integration driver unfortunately needs the same change, so the color can only be changed by the Hue bridge. I'm controlling color from Hubitat by using Google Assistant Relay to sending color names silently to the Hue bridge. It's hacky, but works.
Ah, I see. Some miscommunication here. Let me clarify.
aaron posted a link to a ST DTH driver for the RGBW bulbs. This driver looks to translate CIE XY to hue/satuarion. The problem when he tried to use that driver was the import line on the ZigBee info. This line: import physicalgraph.zigbee.zcl.DataType
I searched for that line and found the thread on the Iris smart button, where it was mentioned that instead of import physicalgraph.zigbee.zcl.DataType one needs to instead use com.hubitat.zigbee.DataType. When I tried to use that, it gave me the error I mentioned above. I'm hoping somebody with more knowledge on all these things can figure out what the problem is, because it seems to be really close.
try import hubitat.zigbee.zcl.DataType again. Previously it was giving an error, but I used it yesterday when installing a ST driver and thought I would leave it in just to see what happened. I didn't get an error this time. Maybe a change to the HE platform was made to accept that now.
I bought the 403.652.67 400 lumen E12 bulb, and also the 204.115.62 600 lumen E26 bulb.
Both paired with no issues, and using generic zigbee drivers I was able to get both to perform on/off/dimming.
The E12 bulb is really bright for a E12 bulb!
The E26, no matter what driver I did, I could not get RGB functionality. I didnt see this post until after I bought them, but its a bummer that they dont have any out of the box RGB functionality. I returned them today, but can confirm they both work! Minus rgb on the E26.
The CIEXY color space isn't supported at this time. They only work with a Hue Bridge, but the color cannot be controlled via the Hue Integration because that driver also doesn't support that color space. I have one and change color from HE in a very round about way. Randomly.
I have a rule that has all the possible colors in the speech dialogue and randomized. They're prefixed with [CC] so my Google Assistant Relay integration tells the Hue Bridge to change to a random color. The same thing is possible with a single color of course.
Ive not tried all the IKEA bulbs, however the full color ones I have tried aren't capable of rendering anything close to a decent green, so due to this and also not providing commands for hue, saturation and color temperature, they are at the bottom of the list to deal with.
It's obvious that the inexpensive price of these is associated with the lack of a typical color control command set...
