Support "Show as" for Plugs?

[jan666]

Hi,

(sorry if this is a duplicate or already supported. #566 and #63 did not really help.)

I'm using deCONZ with a few OSRAM plugs. They're exposed as /lights via the API, so they're shown as "Light" in HomeKit and work as expected. But I dont use them for lights.

I have an old Eve Energy Plug (native HomeKit support via bluetooth). In the HomeApp you can specify how HomeKit should show it (it's called "Anzeigen als" in german). It's possible to select Light, Fan or Outlet.

Is this already possible with homebridge-hue? If not, is it possible to add this?

I already have the "outlet" resourcelink:

{
  "classid": 1,
  "description": "outlet",
  "links": [
    "/lights/3",
    "/lights/4",
    "/lights/5",
    "/lights/11",
    "/lights/14"
  ],
  "name": "homebridge-hue",
  "owner": "...",
  "recycle": false,
  "type": "Link"
}

[ebaauw]

That setting is accessible only to HomeKit apps similar to accessory and service names, rooms, groups, scenes, and automations. It's not exposed over HAP, so there's nothing homebridge-hue can do.

[jan666]

hm, are you sure about this?

I have a homematic plug thats added in fhem. I just added it to homebridge via homebridge-fhem (https://www.npmjs.com/package/homebridge-fhem) and it just works like on the eve:

there is no native homekit support for homematic or fhem

[jan666]

Uh, WTF.

I wanted to test the deCONZ -> FHEM -> homebridge-fhem route. Added my osram plug to fhem via deCONZ REST API, added it to my homebridge-fhem room, restartet homebridge and it worked like I wanted. But now all the deCONZ -> homebridge-hue plugs do it, too. It still works after removing it from homebrige-fhem. How is that even possible? I'm really confused.