you need to mark the group as homekit item, otherwise it considers every item in the group as separate homekit add.
please try to add to group homekit="Lighting"
Thanks for the response. I just tried your suggestion but when I save the file the log shows this:
2020-09-28 10:26:37.782 [WARN ] [.accessories.HomekitAccessoryFactory] - Accessory of type Lighting must have following characteristics [ON_STATE]. Found only []
2020-09-28 10:26:37.784 [WARN ] [mekit.internal.HomekitChangeListener] - Could not add device WallDownlights: Missing mandatory characteristics
The bulb has also disappeared completely from the home app. Do you know what this could be?
This does not result in any errors in the log but all my devices have disappeared from the home app. Only the openHAB server itself is showing but says “Not Supported”?
and check in logs whether openHAB get any requests from iphone.
another things that helps sometimes - if you have apple tv or ipad then disable homekit bridge there to ensure that iphone communicates directly with openhab and not via the bridge.
Yes, I’m using iOS 14 on iPhone X. I don’t have an Apple TV or iPad set up as a bridge. I will try enabling the logs and see if there is any clues and I’ll come back and let you know. Thanks.
I’ve had the logs active for a few days now and can’t spot anything obvious that would be causing this issue.
Everything works perfectly (apart from no CT control via HomeKit) with:
Group WallDownlightsT "Wall Downlights Test" {alexa="Light", homekit="Lighting"}
Color WallDownlightsColorT "Wall Downlights Color Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:color", alexa="BrightnessController.brightness, PowerController.powerState, ColorController.color", homekit="Lighting.onState, Lighting.Hue, Lighting.Brightness, Lighting.Saturation"}
Dimmer WallDownlightsColorTemperatureT "Wall Downlights Color temperature Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:color_temperature", alexa="ColorTemperatureController.colorTemperatureInKelvin"}
String WallDownlightsAlertT "Wall Downlights Alert Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:alert"}
Switch WallDownlightsEffectT "Wall Downlights Color loop Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:effect"}
But as soon as I add homekit=“Lighting.ColorTemperature” to the ColorTemperature item, all my HomeKit devices turn to “No Response”:
Group WallDownlightsT "Wall Downlights Test" {alexa="Light", homekit="Lighting"}
Color WallDownlightsColorT "Wall Downlights Color Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:color", alexa="BrightnessController.brightness, PowerController.powerState, ColorController.color", homekit="Lighting.onState, Lighting.Hue, Lighting.Brightness, Lighting.Saturation"}
Dimmer WallDownlightsColorTemperatureT "Wall Downlights Color temperature Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:color_temperature", alexa="ColorTemperatureController.colorTemperatureInKelvin", homekit="Lighting.ColorTemperature"}
String WallDownlightsAlertT "Wall Downlights Alert Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:alert"}
Switch WallDownlightsEffectT "Wall Downlights Color loop Test" (WallDownlightsT) {channel="hue:0210:0017887862a1:5:effect"}
I can’t understand why this is happening and would really love some inspiration as to where to start debugging / fixing this. I have tried creating a mock color temperature only bulb but as soon as I add the homekit="Lighting.ColorTemperature" metadata anywhere, HomeKit breaks entirely. Thanks in advance.
9.21 Color Temperature
If this characteristic is included in the ”8.23 Light Bulb” (page 147), ”9.44 Hue” (page 179) and ”9.82 Saturation”
(page 197) must not be included as optional characteristics in ”8.23 Light Bulb” (page 147). This characteristic must
not be used for lamps which support color.
basically, it says, either hue and saturation or color temperature, but not both at the same time.
could you verify whether color temperature would work without hue and saturation
Hmmm, that’s interesting since when I connect my hue bridge to HomeKit natively it can control both colour and colour temperature. In OpenHAB, if I leave out the colour temperature metadata, the colour temperature selector in the home app does work but the colours are very bad as I mentioned before. It uses the RGB channels of the bulb to simulate colour temperature rather than using the actual CCT channels / LEDs. This results in very pink looking warm whites and very blue looking cool whites. Out of curiosity I did try the colour temperature tag on it’s own on a separate mock bulb item without color but the result was the same (“No Response” in the home app). It’s strange since Alexa works perfectly.
i can report same Problem. As soon as you add the Colortemperature Number item Homekit is not responding anymore and there is no device in Home App available.
i could reproduce it.
the data openhab sends to home app looks ok and according to latest public apple specification, but home app reject it with the error “Out of compliance”. it needs further investigation. maybe we need to wait for next specification release to understand how to fix.
Java-HAP library used by openHAB always sends one optional parameters as part of accessory description. It looks like this parameter accepted/ignored for all accessories but not for color temperature.
HAP-Node used by Node-RED never sends this parameter.
this parameter has not special meaning in the communication from bridge to home app.
it is difficult to say whether it is a bug of home app or of the lib. on one hand, we dont need to send it. on another hand, home app could just ignore it as it does for all other accessories.
Just found this conversation cause I experienced the same issue when setting up a new openhan 3 server with homekit. Could not get CCT function to run in homekit (Lighting.ColorTemperature issue as described above) . Is there any solution available or in progress?
Right now i am using latest snapshot 3.1 for test system.
Just tried - it’s working OK: take a look at proper items config. I have some issues related to mired / kalvin conversion but it’s not related to this issue