Hallo liebe Community
Ich habe hier zuhause einen Thermostaten der Firma EQ3 AG (eqiva) Bluetooth. Heute dachte ich mir vielleicht kann ich ihn ja auch in Homekit einbinden.
Es gibt auch ein paar Plugins dafür
https://www.npmjs.com/package/homebridge-platform-eq3btsmart
https://github.com/maxnowack/homebridge-eq3ble
doch leider sind diese mit Problemen und mangelnder Pflege belasstet. Wie auch hier im Forum zu lesen ist hier und hier
Dann bin ich auf ein Shell Script gestoßen.
https://github.com/Heckie75/eQ-3-radiator-thermostat
Ich habe dann alles befolgt wie beschrieben
$ sudo apt install expect usw...
Nun kann ich also mit dem Befehl expect ./eq3/eq3.exp 00:1A:22:11:1D:21 status folgendes bekommen
Nun möchte ich mit einem cmdswitch2 Schalter die boost funktion der Heizung aktivieren. Der Befehl wäre expect ./eq3/eq3.exp 00:1A:22:11:1D:21 boost
Dazu habe ich mir in meiner Config einen Schalter angelegt
{
"name": "Thermostat-Boost",
"polling": true,
"on_cmd": "expect ./eq3/eq3.exp 00:1A:22:11:1D:21 boost",
"manufacturer": "EQ-3 AG",
"model": "CC-RT-BLE-EQ",
"serial": "XXXXXXXXXXXX"
}
Nach dem neustart der Homebridge war dieser Schalter auch sichtbar. Wenn ich ihn nun betätige stürzt Homebridge mit folgender meldung im log ab.
Apr 05 17:35:37 raspberrypi homebridge[15665]: [2019-4-5 17:35:37] [CMD Switch] Thermostat-Boost is off.
Apr 05 17:35:45 raspberrypi homebridge[15665]: [2019-4-5 17:35:45] [CMD Switch] Thermostat-Boost is off.
Apr 05 17:35:46 raspberrypi homebridge[15665]: [2019-4-5 17:35:46] [CMD Switch] Failed to turn on Thermostat-Boost
Apr 05 17:35:46 raspberrypi homebridge[15665]: [2019-4-5 17:35:46] [CMD Switch] couldn't read file "./eq3/eq3.exp": no such file or directory
Apr 05 17:35:47 raspberrypi homebridge[15665]: internal/validators.js:125
Apr 05 17:35:47 raspberrypi homebridge[15665]: throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
Apr 05 17:35:47 raspberrypi homebridge[15665]: ^
Apr 05 17:35:47 raspberrypi homebridge[15665]: TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received type undefined
Apr 05 17:35:47 raspberrypi homebridge[15665]: at validateString (internal/validators.js:125:11)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at normalizeSpawnArguments (child_process.js:414:3)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at spawn (child_process.js:553:16)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at Object.execFile (child_process.js:224:15)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at exec (child_process.js:152:18)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at cmdSwitchPlatform.setPowerState (/usr/local/lib/node_modules/homebridge-cmdswitch2/index.js:222:3)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at Characteristic.On.emit (events.js:193:13)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at Characteristic.On.Characteristic.setValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:321:10)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at Service.Switch.Service.setCharacteristic (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Service.js:183:32)
Apr 05 17:35:47 raspberrypi homebridge[15665]: at Timeout._onTimeout (/usr/local/lib/node_modules/homebridge-cmdswitch2/index.js:237:12)
Apr 05 17:35:47 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=1/FAILURE
Apr 05 17:35:47 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
Apr 05 17:35:47 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
Apr 05 17:35:57 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
Alles anzeigen
und nun bleibt die Homebridge in einem reboot loop hängen bis ich den Schalter wieder aus der Config entferne.
Apr 05 17:36:03 raspberrypi homebridge[17358]: [2019-4-5 17:36:03] [CMD Switch] Initializing platform accessory 'Thermostat-Boost'...
Apr 05 17:36:03 raspberrypi homebridge[17358]: /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:266
Apr 05 17:36:03 raspberrypi homebridge[17358]: throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
Apr 05 17:36:03 raspberrypi homebridge[17358]: ^
Apr 05 17:36:03 raspberrypi homebridge[17358]: Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 56817a95-623a-496e-ace3-f8d4b4dd17d9
Apr 05 17:36:03 raspberrypi homebridge[17358]: at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:266:13)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at Bridge.Accessory.addBridgedAccessories (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:292:10)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at Server._handleRegisterPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:483:16)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:41:10)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at API.emit (events.js:193:13)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at API.registerPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/api.js:171:8)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at cmdSwitchPlatform.addAccessory (/usr/local/lib/node_modules/homebridge-cmdswitch2/index.js:67:14)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at cmdSwitchPlatform.didFinishLaunching (/usr/local/lib/node_modules/homebridge-cmdswitch2/index.js:36:37)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at API.emit (events.js:198:15)
Apr 05 17:36:03 raspberrypi homebridge[17358]: at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:102:13)
Apr 05 17:36:03 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=1/FAILURE
Apr 05 17:36:03 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
Apr 05 17:36:03 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
Apr 05 17:36:13 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
Apr 05 17:36:13 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
Alles anzeigen
Wie bekomme ich nun diesen schalter ans laufen?