Homebridge-Adapter: Funktionierende Plugins und Beispiele

[apollon77]

@martiman I think for this you need to tell a bit more in detail what you setup and how. Which mode you use the adapter in and such

[MartiMan]

@apollon77 Thanks for your answer.

These are the settings I'm using:

[apollon77]

@martiman Ok, so Wrapper Mode ... so you have added the homebridge started by the adapter to our Apple Home and then the states are not provided? The a more complete log (as text from disk logfile) would be helpful

[MartiMan]

@apollon77
From what I understand from the manual, the plugin will create the link to the Home app.

"homebridge-eosstb is a Homebridge plugin allowing you to control your set-top box (typically an ARRIS DCX960 / VIP5002W or HUMAX EOS1008R / 2008C) running on the Magenta AT / Telenet BE / Sunrise CH / Virgin Media GB & IE / Ziggo NL Horizon TV platform with Apple HomeKit using the Home app and the Apple TV Remote in the Control Center."

This is the full log after a restart of the plugin.

iobroker.2023-12-06.log.html

[MartiMan]

@apollon77 I assume the objects of the Homebridge plugin should be added as a ham subfolder?

[apollon77]

@martiman Butall this do nt happen automatically ... you need to go into the Apple home and click the "+" and then scan ender the pin you defined in the config to add the bridge to youe apple home. Did you do that?

[MartiMan]

@apollon77 Late reply, new system running on bookworm now which took me some time...

Well I'm using yahka for all my lights and gates combined with the S7 adapter so I'm familiar with that.

From my understanding Homebridge supplies the Homekit bridge that makes that Homebridge plugins will be recognised by the Home app.

According to the ham README.md the wrapper mode does not support this (I had a RTFM moment lol):

"IMPORTANT: This mode allows to use the device integrations of the provided homebridge plugins. No "bridge" is provided that can be used by the Home App!"

So then I should get at least some variables in objects that I can connect to yahka using enum no?
Or how should I interpret the "device integrations" mentioned above?

I really don't want to also have Homebridge running for just this plugin.

UPDATE:

After installing "homebridge-seasons", as it was tested and confirmed working, I suddenly started getting log errors which I didn't get with homebridge-eosstb plugin alone!?

Now the ham folder in objects gets a 0 folder with all necessary variables of the seasons plugin.
Still no eosstb variables.

2023-12-10 10:10:31.217 - debug: ham.0 (9301) setState Season.Season.Season-Name: set value = Winter
2023-12-10 10:10:31.219 - error: ham.0 (9301) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-12-10 10:10:31.220 - error: ham.0 (9301) unhandled promise rejection: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 25ec2c37-426c-4b8e-a20f-976770fa1af5
2023-12-10 10:10:31.347 - error: ham.0 (9301) Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 25ec2c37-426c-4b8e-a20f-976770fa1af5
at WrapperBridge.Accessory.addBridgedAccessory (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/src/lib/Accessory.ts:594:15)
at WrapperBridge.addBridgedAccessory (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/index.js:299:55)
at /opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/src/bridgeService.ts:554:11
at Array.forEach ()
at /opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/src/bridgeService.ts:542:19
at /opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/src/lib/util/once.ts:10:18
at SeasonsPlatform.accessories (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-seasons/index.js:64:3)
at /opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/src/bridgeService.ts:537:17
at new Promise ()
at BridgeService.loadPlatformAccessories (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/homebridge/bridgeService.js:400:16)
2023-12-10 10:10:31.348 - error: ham.0 (9301) Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 25ec2c37-426c-4b8e-a20f-976770fa1af5
2023-12-10 10:10:31.374 - info: ham.0 (9301) cleaned everything up...
2023-12-10 10:10:31.394 - info: ham.0 (9301) terminating
2023-12-10 10:10:31.396 - warn: ham.0 (9301) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-12-10 10:10:31.397 - debug: ham.0 (9301) [10/12/2023, 10:10:31] [EOSSTB] Goodbye
2023-12-10 10:10:31.898 - info: ham.0 (9301) terminating
2023-12-10 10:10:31.969 - error: host.rpi4 Caught by controller[1]: [10/12/2023, 10:10:30] Plugin /opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper package.json does not contain the keyword 'homebridge-plugin'.
2023-12-10 10:10:31.970 - error: host.rpi4 Caught by controller[2]: [10/12/2023, 10:10:30] Plugin /opt/iobroker/node_modules/homebridge-plugin-wrapper package.json does not contain the keyword 'homebridge-plugin'.
2023-12-10 10:10:31.970 - error: host.rpi4 Caught by controller[3]: [10/12/2023, 10:10:30] The plugin "homebridge-eosstb" requires a Homebridge version of >=1.6.0 which does not satisfy the current Homebridge version of 1.5.0. You may need to update this plugin (or Homebridge) to a newer version. You may face unexpected issues or stability problems running this plugin.
2023-12-10 10:10:31.970 - error: host.rpi4 instance system.adapter.ham.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-12-10 10:10:31.971 - info: host.rpi4 Restart adapter system.adapter.ham.0 because enabled
2023-12-10 10:11:02.013 - info: host.rpi4 instance system.adapter.ham.0 started with pid 9342

So apparently eosstb needs at least homebridge V1.6.0 and ham apparently still runs V1.5.0.

[apollon77]

@martiman sagte in Homebridge-Adapter: Funktionierende Plugins und Beispiele:

"IMPORTANT: This mode allows to use the device integrations of the provided homebridge plugins. No "bridge" is provided that can be used by the Home App!"

hehe ... jooo ... Wrapper mode ist genau das ... und keine Bridge.. Nimm den Local Mode, dann startet er eine Bridge

[MartiMan]

@apollon77 I installed homebridge for this one and also android plugin for Shield TV. I don’t really need to automate these so Siri access is enough

[dfrozen1977]

@apollon77
@alexeimotkoff/homebridge-daichi-comfort-conditioner

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"
  },
  "platforms": [
    {
      "name": "Daichi Comfort",
      "username": "************",
      "password": "************",
      "platform": "DaichiComfortConditioner"
    }
  ]
}
![HAM.png](/assets/uploads/files/1712289853797-ham.png) ```

[eugenmayer]

homebridge-thermotek

• wrapper mode

{
  "description": "Add configuration for your accessories or platforms according to the docs of the plugins.",
  "accessories": [],
  "platforms": [
    {
      "host": "zz.xx.yy.cc",
      "port": "6653",
      "platform": "ThermotecRadiatorControl"
    }
  ]
}

[haselchen]

@eugenmayer
Dieser Post soll uns was sagen?

[oFbEQnpoLKKl6mbY5e13]

@haselchen

Dass es ein funktionierendes Plugin ist?

[haselchen]

@ofbeqnpolkkl6mby5e13

Okay, vielleicht hatte ich das einfach nur vermisst

Bitte packt auf jeden Fall Pluginname, Version des Plugins, die Version des ham Adapters und EUre nodejs Version mit rein. Danke!

Danke Ingo

[oFbEQnpoLKKl6mbY5e13]

@eugenmayer

Trage die Infos -siehe den Hinweis von @haselchen- bitte noch nach.

[tob111]

Hallo habe den ham 5.3.1 und versuche gerade über homebridge-ring mein Ring Alarm System einzubinden. An die Sensoren komme ich schön ran, die sind auch alle gelistet. Das Problem ist die Kamera. Da werden zwar auch Infos gelistet, ich würde aber gerne auf die Snapshots zugreifen. Wo finde ich die?

[haselchen]

@tob111

Und der Ring Adapter ist keine Alternative?

[tob111]

@haselchen über den bekomm ich halt nur die kamera bilder. das ginge natürlich auch aber fände es schöner es über einen adapter zu lösen

[Gregor P]

erledigt