Using Openhab 2.5.5 and the paperui installed homekit addon dimmable lights are only switchable.
Feeeback of brightness value works. But setting brightness through ios Home is not possible. I’ve tried this:
with the old tags
light as a group with seperate switch
with color instead of dimmer.
Does anybody here know if i did something wrong? Or is it a bug in the latest version?
In openhab log i can find:
[WARN ] [ssories.HomekitCharacteristicFactory] - Item type Dimmer is not supported for FF_LivingRoom_Haard. Only Color type is supported.
Hey H102. My case is slightly different.
The thing is… my dimmer is correctly found and shown in iOS home app. I can use the slider, but when i set it to eg 50% only ON command is sent to the item. The percentage value is not sent as a command. Although a value update of the dimmer item to 50% is logged.
habpanel and paperui function correctly. Have dropped google assistant and axexa in favor of Homekit (like it best, fastest solution for me with a very high wife acceptance factor)
I believed so, but upon further testing: no this is not the case. When the Brightness is updated in the Home app, this does not have any impact on the openhab Item. Aside from the ‘ON’ command.
When i change the value through PaperUI, the (%) value of the dimmer is updated in the Home app, when the item state is refreshed (swithing screens in the Home app).
A log of chaning the brightness value in the Home app:
2020-05-11 19:08:14.646 [DEBUG] [.server.impl.http.impl.BinaryHandler] - Received data [/10.0.1.62:51886]:
PUT /characteristics HTTP/1.1
Host: openHAB._hap._tcp.local
Content-Length: 94
Content-Type: application/hap+json
{"characteristics":[{"aid":608082418,"iid":9,"value":1},{"aid":608082418,"iid":10,"value":4}]}
2020-05-11 19:08:14.652 [WARN ] [ssories.HomekitCharacteristicFactory] - Item type Dimmer is not supported for FF_LivingRoom_Haard. Only Color type is supported.
2020-05-11 19:08:14.654 [INFO ] [er.impl.http.HomekitClientConnection] - 204 /characteristics
2020-05-11 19:08:14.658 [DEBUG] [.server.impl.http.impl.BinaryHandler] - Sending data [/10.0.1.62:51886]:
HTTP/1.1 204 No Content
Content-type: application/hap+json
Connection: keep-alive
2020-05-11 19:08:14.660 [TRACE] [server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 105, cap: 256) [/10.0.1.62:51886]:
57003C0701461DB7FE45219AC4A3F4A4AF70CDC544B0D551AB9E882D1B2D0C56AFD2B71606F1A984FF91ECC83536D9875E8ED14530555529853046A28C202A53EC900F6B5EADD15DBDF957E9C00FC30FB032694A3BDAF3E0EE66186F8D3886272052ABE5DBA0287FC0
==> /var/log/openhab2/events.log <==
2020-05-11 19:08:14.670 [ome.event.ItemCommandEvent] - Item 'FF_LivingRoom_Haard' received command ON
==> /var/log/openhab2/openhab.log <==
2020-05-11 19:08:14.711 [DEBUG] [nx.internal.client.AbstractKNXClient] - Wrote value 'ON' to datapoint 'command DP 1/0/4 'knx:ip:bridge', DPT id 1.001, low priority' (0. attempt).
What is the dimmer you are using?
I use Lutron Caseta with the Lutron Caseta Hub Pro.
Lutron Caseta devices and pro hub are directly accessible from Homekit, and, with the Lutron plugin, Openhab.
Lutron hub keeps both Homekit and Openhab updated with the latest status of a device.
While I use the Openhab Homekit plugin, I neither need it nor use it for my Lutron devices.
If I change a light’s brightness using the Homekit Home App, it is immediately reflected in the OpenHab paper ui.
If I change a light’s brightness using the OpenHab paper ui, it is immediately reflected in the Homekit Home App.
The only downside to Lutron Caseta is it’s expensive. Prices range from $45 to $90 for a dimmer, depending on where you buy it.
@yfre Thank you again !
Color does the trick - thought i tried it as a part of a complex item (with the new style meta data) but must have done something wrong.
I must say - comparing to the homebridge-openhab2-complete - the addon is now really gaining ground. It is much faster, support for thermostat item is better. Some items are missing but none that i need at the moment.
Movement, lock, moterised locks, light, dimmer, contact and temperature sensors are all working.
I’ve experienced two pairing failures, a lot of reïnitializations because item file typo’s (which for 68 homekit accessories is a lot of work to assign room, type, status, etc). But in all: very nice work!
When you say “fix is on the way” – what repo / branch would that be? I’ve cloned the openhab addons 2.5.4
@smitopher most of my devices use knx protocol/standard. In all 38 dimmers, most of them 1-10v from Gira. Then 30 knx switches (outlets, non dimmable lighting, locks), a thermostat in every room, about 48 contactsensors, 6 heating/cooling inverters, 12 motorized blinds/curtains…
The only non-knx items are from Buderus (solar/gas heating) - integrated via km200 gateway wich translates buderus bus items to opanhab items, doorbird (http integration), …
regarding assigning accessories to a room, status. i know your pain. i have around 60 accessories and i had to do this exercises few times as well. but there is nothing we can do from server side.
do you want to have 2 lights or 2 lights + group that controls both lights?
btw, you probably dont need name as item. it is only fo the case the item name can change.
try following configurations.
2 lights (remove homekit from group):
it looks like multiple services linked to one accessory.
im afraid, this is not supported by openHAB binding yet.
how you define it in homebridge? are there examples/description in internet?
!
