homebridge/homekit

EnderPhilipp · 09 Januar 2017, 15:29:04

Wenn die HueBirne unreachable ist bleiben die Readings bri und pct gleich.

Wie kann ich denn jetzt sagen, dass der state unreachable in HomeKit als off angezeigt werden soll ?

Mfg
Philipp

jensenbln · 09 Januar 2017, 20:31:16

wie aktiviere ich die homebridge log dateien? homebridge.err oder homebridge.log. in meinem /var/log ist nichts vorhanden. und googeln hat mir auch nicht wirklich weitergeholfen, da in allen ergebnissen die log vorhanden sind...

danke für hilfe,
jens

MrFisch · 09 Januar 2017, 21:10:10

Hallo Zusammen,

ich hatte mich in den letzten Tagen mit zwei parallel laufenden Homebridge auf eine PI (Raspberry pi 3) beschäftigt.
Mit Hilfe von Arndt (DANKE!!!) habe ich es nun geschafft.
Warum benötigte ich zwei Homebridge-"server":
- Bessere Strukturierung
- mehr als 100 Geräte

Was habe ich gemacht:
1) Homebridge Nr. 1 installieren --> https://wiki.fhem.de/wiki/Homebridge_einrichten

2) Homebridge Nr. 2 installieren:
a) mkdir -p ~/.homebridge2
b) nano ~/.homebridge2/config.json
c) Homebridge2 Server anpassen (ID/Port ändern)

Code Auswählen

{
    "bridge": {
        "name": "Homebridge2",
        "username": "CC:22:3D:E3:CE:31",
        "port": 51830,
        "pin": "031-45-154"
    },
 
    "platforms": [
        {
            "platform": "FHEM",
            "name": "FHEM",
            "server": "127.0.0.1",
            "port": "8083",
            "filter": "room=Homekit2"
        }
     ],
 
    "accessories": []
}

c) Hardlink erstellen: sudo ln /usr/bin/homebridge /usr/bin/homebridge2
d) Autostart in init.d: sudo nano /etc/init.d/homebridge2
e) Init.d für zweite Homebridge anpassen:

Code Auswählen


#!/bin/sh
### BEGIN INIT INFO
# Provides: homebridge
# Required-Start: $network $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time for homebridge
# Description: Enable service provided by daemon.
### END INIT INFO
export PATH=$PATH:/usr/local/bin
export NODE_PATH=$NODE_PATH:/usr/local/lib/node_modules
PID=`pidof homebridge2`
case "$1" in
start)
if ps -p $PID > /dev/null 2>&1; then
        echo "Homebridge2 is already running"
else
        su - pi -c "homebridge2 -U ~/.homebridge2 > /dev/null 2>&1 &"
        echo "Homebridge2 starting"
        $0 status
fi
;;
stop)
if ! ps -p $PID > /dev/null 2>&1; then
        echo "Homebridge2 is not running"
else
        kill $PID
        echo "Homebridge2 closed"
fi
;;
restart)
if ! ps -p $PID > /dev/null 2>&1; then
        $0 start
else
        $0 stop
        $0 start
fi
;;
status)
if ps -p $PID > /dev/null 2>&1; then
        echo "Homebridge2 is running PID $PID"
else
        echo "Homebridge2 is not running"
fi
;;
*)
echo "Usage: $0 {start|stop|status|restart}"
exit 1
;;
esac
exit 0

f) sudo chmod 755 /etc/init.d/homebridge2
g) Soweit alles fertig... zum testen:

iOS Geräte mit homebridge`s übers terminal koppeln:
1) homebridge
2) homebridge2 -U ~/.homebridge2

Zukünftig muss man nur noch:

sudo /etc/init.d/homebridge start --> startet Homebridge 1
sudo /etc/init.d/homebridge2 start --> startet Homebridge 2

Status anzeigen (ob beide laufen):
sudo /etc/init.d/homebridge status

Ergebnis muss sein:
Homebridge is running PID 7499 7428

(Die Nummern dienen nur als Beispiel)
WICHTIG ist, dass neben der PID zwei Nummer-Codes stehen. Jeder Code steht für eine Homebridge...
Somit laufen beide Homebridge...

Hab dies seit ca. 2 Tagen ohne Aussetzer und Problemen am laufen... Auch der sync mit der Cloud über ATV 4 funktioniert.
Getestet an zwei iPhones und iPad...

Viel Spaß...
Ich hoffe ich konnte einigen helfen

-

RaspiLED · 09 Januar 2017, 22:16:20

Ah, super wenn man statt homebridge2 homebridg2 verwendet, dann enthält der Befehl "sudo service homebridge status" (bzw. "pidof homebridge") auch nur die erste Instanz und "sudo service homebridg2 status" auch nur die Zweite. Statt status gehen auch start/stop/restart...

Aber läuft ja auch so

Gruß Arnd

Gesendet von iPhone mit Tapatalk

Hauswart · 10 Januar 2017, 07:57:41

Ich habe gestern mal von homebridge-fhem 0.2.67 auf 0.2.68 geupdatet und kann seitdem homebridge nicht mehr starten und erhalte folgende Fehlermeldung:

Markus M. · 10 Januar 2017, 09:47:55

Ich finde es praktischer, alle Instanzen in einen Service zu packen.
Hat jemand einen Tipp wie man sicherstellt dass FHEM schon läuft bis homebridge gestartet wird?

Sent from my iPhone using Tapatalk

Steffen@Home · 10 Januar 2017, 13:25:18

Hallo Dan, nochmals zu dem Custom Reading.

Der Homebridge Log sieht doch nicht nach einem Fehler für den "GaOstTemp" aus oder?
Die Frage ist auch ob es überhaupt möglich ist in der "Home"App einem generic Device ("Temperature Sensor") außer den Standards Temperatur und rel. Luftfeuchtigkeit ein weiteres "Detail" (in meinem Fall der Taupunkt) beizubringen diesen anzuzeigen.
D.h. ja die Characteristic "Current Temperature" würde 2 mal, jedoch mit anderem Name benutzt.

Code Auswählen

[1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,minValue=-30,name=Temperatur  CurrentTemperature=dew,name=Taupunkt  CurrentRelativeHumidity=humidity
[1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp is thermometer
[1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp has
[1/6/2017, 10:37:46 AM] [FHEM]   Custom Temperatur [temperature]
[1/6/2017, 10:37:46 AM] [FHEM]   Custom Taupunkt [dew]
[1/6/2017, 10:37:46 AM] [FHEM]   CurrentRelativeHumidity [humidity]
  2017-01-06 10:37:46 caching: GaOstTemp-temperature: 6.5�
[1/6/2017, 10:37:46 AM] [FHEM]     caching: Custom Temperatur: 6.5 (as number; from '6.5�')
  2017-01-06 10:37:46 caching: GaOstTemp-dew: -3.87
[1/6/2017, 10:37:46 AM] [FHEM]     caching: Custom Taupunkt: -3.87 (as number; from '-3.87')
  2017-01-06 10:37:46 caching: GaOstTemp-humidity: 47.3�
[1/6/2017, 10:37:46 AM] [FHEM]     caching: CurrentRelativeHumidity: 47 (as number; from '47.3�')

------------------------------------------

Zitat von: Steffen@Home am 06 Januar 2017, 10:44:23
Habe hier die Ausgabe der Homebridge:

Code Auswählen Erweitern
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node> *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister> [1/6/2017, 10:37:45 AM] Loaded plugin: homebridge-fhem homebridge API version: 2.1 [1/6/2017, 10:37:45 AM] Registering platform 'homebridge-fhem.FHEM' [1/6/2017, 10:37:45 AM] --- [1/6/2017, 10:37:45 AM] Loaded config.json with 0 accessories and 1 platforms. [1/6/2017, 10:37:45 AM] --- [1/6/2017, 10:37:45 AM] Loading 1 platforms... [1/6/2017, 10:37:45 AM] [FHEM] Initializing FHEM platform... starting longpoll: http://127.0.0.1:8083/fhem.pl?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1483695466114 [1/6/2017, 10:37:46 AM] [FHEM] Checking genericDeviceType... [1/6/2017, 10:37:46 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1 [1/6/2017, 10:37:46 AM] [FHEM] Fetching FHEM devices... [1/6/2017, 10:37:46 AM] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=Homekit&XHR=1 [1/6/2017, 10:37:46 AM] Loading 0 accessories... Server listening on: http://<ip>:8282 [1/6/2017, 10:37:46 AM] [FHEM] got: 12 results [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: TargetHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:3,cmds=OFF:controlManu+off;HEAT:controlMode+boost;AUTO:controlMode+auto;COOL:controlMode+night CurrentHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:0 [1/6/2017, 10:37:46 AM] [FHEM] BZ_Thermostat_Clima is thermostat [1/6/2017, 10:37:46 AM] [FHEM] BZ_Thermostat_Clima has [1/6/2017, 10:37:46 AM] [FHEM] TargetTemperature [desired-temp] [1/6/2017, 10:37:46 AM] [FHEM] Custom Actuation [ValvePosition] [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature [measured-temp] [1/6/2017, 10:37:46 AM] [FHEM] TargetHeatingCoolingState [heatingState] [1/6/2017, 10:37:46 AM] [FHEM] CurrentHeatingCoolingState [heatingState] 2017-01-06 10:37:46 caching: BZ_Thermostat_Clima-desired-temp: 18.0 [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetTemperature: 18 (as number; from '18.0') 2017-01-06 10:37:46 caching: BZ_Thermostat_Clima-ValvePosition: 3 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Actuation: 3 (as number; from '3') 2017-01-06 10:37:46 caching: BZ_Thermostat_Clima-measured-temp: 19.6 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentTemperature: 19.6 (as number; from '19.6') 2017-01-06 10:37:46 caching: BZ_Thermostat_Clima-heatingState: HEAT [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetHeatingCoolingState: 1 (as number; means HEAT; from 'HEAT') [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'HEAT') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: On=power,valueOn=on,valueOff=off,cmdOn=on,cmdOff=off [1/6/2017, 10:37:46 AM] [FHEM] DenonAVR is switch [1/6/2017, 10:37:46 AM] [FHEM] DenonAVR has [1/6/2017, 10:37:46 AM] [FHEM] Custom Volume [volume;cached] [1/6/2017, 10:37:46 AM] [FHEM] Custom Power [power] [1/6/2017, 10:37:46 AM] [FHEM] On [power;on,off] 2017-01-06 10:37:46 caching: DenonAVR-volume: 19 % [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Volume: 19 (as number; from '19 %') 2017-01-06 10:37:46 caching: DenonAVR-power: on [1/6/2017, 10:37:46 AM] [FHEM] DenonAVR-power not a number: on [1/6/2017, 10:37:46 AM] [FHEM] caching: On: true (as boolean; from 'on') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: On=DenonAVR:playStatus,valueOn=playing,valueOff=stopped,cmdOn=on [1/6/2017, 10:37:46 AM] [FHEM] DenonAVRplayiRadio is switch [1/6/2017, 10:37:46 AM] [FHEM] DenonAVRplayiRadio has [1/6/2017, 10:37:46 AM] [FHEM] On [DenonAVR.playStatus;on,off] [1/6/2017, 10:37:46 AM] [FHEM] query: On for DenonAVR-playStatus [1/6/2017, 10:37:46 AM] [FHEM] not cached [1/6/2017, 10:37:46 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BReadingsVal(%22DenonAVR%22,%22playStatus%22,%22%22)%7D&XHR=1 [1/6/2017, 10:37:46 AM] [FHEM] ignoring FHEM.Homebridge [1/6/2017, 10:37:46 AM] [FHEM] no accessory created for FHEM.Homebridge (dummy) [1/6/2017, 10:37:46 AM] [FHEM] FHEM.Homebridge.DOIF: no service type detected [1/6/2017, 10:37:46 AM] [FHEM] no accessory created for FHEM.Homebridge.DOIF (DOIF) [1/6/2017, 10:37:46 AM] [FHEM] ignoring FHEM.Homebridge.Status [1/6/2017, 10:37:46 AM] [FHEM] no accessory created for FHEM.Homebridge.Status (dummy) [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,minValue=-30,name=Temperatur CurrentTemperature=dew,name=Taupunkt CurrentRelativeHumidity=humidity [1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp is thermometer [1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp has [1/6/2017, 10:37:46 AM] [FHEM] Custom Temperatur [temperature] [1/6/2017, 10:37:46 AM] [FHEM] Custom Taupunkt [dew] [1/6/2017, 10:37:46 AM] [FHEM] CurrentRelativeHumidity [humidity] 2017-01-06 10:37:46 caching: GaOstTemp-temperature: 6.5� [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Temperatur: 6.5 (as number; from '6.5�') 2017-01-06 10:37:46 caching: GaOstTemp-dew: -3.87 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Taupunkt: -3.87 (as number; from '-3.87') 2017-01-06 10:37:46 caching: GaOstTemp-humidity: 47.3� [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentRelativeHumidity: 47 (as number; from '47.3�') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,minValue=-20,name=Temperatur CurrentRelativeHumidity=humidity [1/6/2017, 10:37:46 AM] [FHEM] HM_50310C is thermometer [1/6/2017, 10:37:46 AM] [FHEM] HM_50310C has [1/6/2017, 10:37:46 AM] [FHEM] StatusLowBattery [battery] [1/6/2017, 10:37:46 AM] [FHEM] FirmwareRevision [D-firmware] [1/6/2017, 10:37:46 AM] [FHEM] Custom Temperatur [temperature] [1/6/2017, 10:37:46 AM] [FHEM] CurrentRelativeHumidity [humidity] 2017-01-06 10:37:46 caching: HM_50310C-battery: ok [1/6/2017, 10:37:46 AM] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok') 2017-01-06 10:37:46 caching: HM_50310C-D-firmware: 1.3 [1/6/2017, 10:37:46 AM] [FHEM] caching: FirmwareRevision: 1.3 (as string; from '1.3') 2017-01-06 10:37:46 caching: HM_50310C-temperature: 3.6 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Temperatur: 3.6 (as number; from '3.6') 2017-01-06 10:37:46 caching: HM_50310C-humidity: 34 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentRelativeHumidity: 34 (as number; from '34') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: TargetHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:3,cmds=OFF:controlManu+off;HEAT:controlMode+boost;AUTO:controlMode+auto;COOL:controlMode+night CurrentHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:0 [1/6/2017, 10:37:46 AM] [FHEM] SZ_Thermostat_Clima is thermostat [1/6/2017, 10:37:46 AM] [FHEM] SZ_Thermostat_Clima has [1/6/2017, 10:37:46 AM] [FHEM] TargetTemperature [desired-temp] [1/6/2017, 10:37:46 AM] [FHEM] Custom Actuation [ValvePosition] [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature [measured-temp] [1/6/2017, 10:37:46 AM] [FHEM] TargetHeatingCoolingState [heatingState] [1/6/2017, 10:37:46 AM] [FHEM] CurrentHeatingCoolingState [heatingState] 2017-01-06 10:37:46 caching: SZ_Thermostat_Clima-desired-temp: 18.0 [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetTemperature: 18 (as number; from '18.0') 2017-01-06 10:37:46 caching: SZ_Thermostat_Clima-ValvePosition: 2 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Actuation: 2 (as number; from '2') 2017-01-06 10:37:46 caching: SZ_Thermostat_Clima-measured-temp: 18.7 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentTemperature: 18.7 (as number; from '18.7') 2017-01-06 10:37:46 caching: SZ_Thermostat_Clima-heatingState: HEAT [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetHeatingCoolingState: 1 (as number; means HEAT; from 'HEAT') [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'HEAT') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,CurrentRelativeHumidity=humidity [1/6/2017, 10:37:46 AM] [FHEM] WZTemp is thermometer [1/6/2017, 10:37:46 AM] [FHEM] WZTemp has [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature [temperature] [1/6/2017, 10:37:46 AM] [FHEM] CurrentRelativeHumidity [humidity] 2017-01-06 10:37:46 caching: WZTemp-temperature: 18.0 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentTemperature: 18 (as number; from '18.0') 2017-01-06 10:37:46 caching: WZTemp-humidity: 33.0 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentRelativeHumidity: 33 (as number; from '33.0') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: TargetHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:3,cmds=OFF:controlManu+off;HEAT:controlMode+boost;AUTO:controlMode+auto;COOL:controlMode+night CurrentHeatingCoolingState=heatingState,values=OFF:0;HEAT:1;COOL:2;AUTO:0 [1/6/2017, 10:37:46 AM] [FHEM] WZ_Thermostat_Clima is thermostat [1/6/2017, 10:37:46 AM] [FHEM] WZ_Thermostat_Clima has [1/6/2017, 10:37:46 AM] [FHEM] TargetTemperature [desired-temp] [1/6/2017, 10:37:46 AM] [FHEM] Custom Actuation [ValvePosition] [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature [measured-temp] [1/6/2017, 10:37:46 AM] [FHEM] TargetHeatingCoolingState [heatingState] [1/6/2017, 10:37:46 AM] [FHEM] CurrentHeatingCoolingState [heatingState] 2017-01-06 10:37:46 caching: WZ_Thermostat_Clima-desired-temp: 18.0 [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetTemperature: 18 (as number; from '18.0') 2017-01-06 10:37:46 caching: WZ_Thermostat_Clima-ValvePosition: 0 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Actuation: 0 (as number; from '0') 2017-01-06 10:37:46 caching: WZ_Thermostat_Clima-measured-temp: 20.3 [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentTemperature: 20.3 (as number; from '20.3') 2017-01-06 10:37:46 caching: WZ_Thermostat_Clima-heatingState: AUTO [1/6/2017, 10:37:46 AM] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'AUTO') [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentHeatingCoolingState: 0 (as number; means OFF; from 'AUTO') [1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: On=TV1:state,valueOn=present,valueOff=absent,cmdOff=setOFF [1/6/2017, 10:37:46 AM] [FHEM] wz_tv1_poweroff is contact [1/6/2017, 10:37:46 AM] [FHEM] wz_tv1_poweroff has [1/6/2017, 10:37:46 AM] [FHEM] On [TV1.state;undefined,setOFF] [1/6/2017, 10:37:46 AM] [FHEM] query: On for TV1-state [1/6/2017, 10:37:46 AM] [FHEM] not cached [1/6/2017, 10:37:46 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BReadingsVal(%22TV1%22,%22state%22,%22%22)%7D&XHR=1 [1/6/2017, 10:37:46 AM] [FHEM] Initializing platform accessory 'BZ_Thermostat_Clima'... [1/6/2017, 10:37:46 AM] [FHEM] creating services for BZ_Thermostat_Clima [1/6/2017, 10:37:46 AM] [FHEM] information service for BZ_Thermostat_Clima [1/6/2017, 10:37:46 AM] [FHEM] manufacturer, model and serial number characteristics for BZ_Thermostat_Clima [1/6/2017, 10:37:46 AM] [FHEM] Thermostat service for BZ_Thermostat_Clima [1/6/2017, 10:37:46 AM] [FHEM] TargetTemperature characteristic for BZ_Thermostat_Clima:desired-temp [1/6/2017, 10:37:46 AM] [FHEM] Custom Actuation characteristic for BZ_Thermostat_Clima:ValvePosition [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature characteristic for BZ_Thermostat_Clima:measured-temp [1/6/2017, 10:37:46 AM] [FHEM] TargetHeatingCoolingState characteristic for BZ_Thermostat_Clima:heatingState [1/6/2017, 10:37:46 AM] [FHEM] CurrentHeatingCoolingState characteristic for BZ_Thermostat_Clima:heatingState [1/6/2017, 10:37:46 AM] [FHEM] Initializing platform accessory 'DenonAVR'... [1/6/2017, 10:37:46 AM] [FHEM] creating services for DenonAVR [1/6/2017, 10:37:46 AM] [FHEM] information service for DenonAVR [1/6/2017, 10:37:46 AM] [FHEM] manufacturer, model and serial number characteristics for DenonAVR [1/6/2017, 10:37:46 AM] [FHEM] Switch service for DenonAVR [1/6/2017, 10:37:46 AM] [FHEM] Custom Volume characteristic for DenonAVR:volume [1/6/2017, 10:37:46 AM] [FHEM] Custom Power characteristic for DenonAVR:power [1/6/2017, 10:37:46 AM] [FHEM] On characteristic for DenonAVR:power [1/6/2017, 10:37:46 AM] [FHEM] Initializing platform accessory 'DenonAVRplayiRadio'... [1/6/2017, 10:37:46 AM] [FHEM] creating services for DenonAVRplayiRadio [1/6/2017, 10:37:46 AM] [FHEM] information service for DenonAVRplayiRadio [1/6/2017, 10:37:46 AM] [FHEM] manufacturer, model and serial number characteristics for DenonAVRplayiRadio [1/6/2017, 10:37:46 AM] [FHEM] Switch service for DenonAVRplayiRadio [1/6/2017, 10:37:46 AM] [FHEM] On characteristic for DenonAVR:playStatus [1/6/2017, 10:37:46 AM] [FHEM] Initializing platform accessory 'GaOstTemp'... [1/6/2017, 10:37:46 AM] [FHEM] creating services for GaOstTemp [1/6/2017, 10:37:46 AM] [FHEM] information service for GaOstTemp [1/6/2017, 10:37:46 AM] [FHEM] manufacturer, model and serial number characteristics for GaOstTemp [1/6/2017, 10:37:46 AM] [FHEM] TemperatureSensor service for GaOstTemp [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature characteristic for GaOstTemp:temperature [1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp: CurrentTemperature characteristic already defined for service GaOstTemp and no subtype given [1/6/2017, 10:37:46 AM] [FHEM] TemperatureSensor service for GaOstTemp [1/6/2017, 10:37:46 AM] [FHEM] CurrentTemperature characteristic for GaOstTemp:dew [1/6/2017, 10:37:46 AM] [FHEM] CurrentRelativeHumidity characteristic for GaOstTemp:humidity /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131 throw new Error("Cannot add a Service with the same UUID '" + existing.UUID + "' as another Service in this Accessory without also defining a unique 'subtype' property."); ^ Error: Cannot add a Service with the same UUID '0000008A-0000-1000-8000-0026BB765291' as another Service in this Accessory without also defining a unique 'subtype' property. at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131:15) at /usr/local/lib/node_modules/homebridge/lib/server.js:415:19 at Array.forEach (native) at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:399:14) at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:361:32) at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19 at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-fhem/index.js:994:22) at Request.self.callback (/usr/local/lib/node_modules/homebridge-fhem/node_modules/request/request.js:187:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7)

DeeSPe · 10 Januar 2017, 14:14:45

Zitat von: Steffen@Home am 10 Januar 2017, 13:25:18
Hallo Dan, nochmals zu dem Custom Reading.

Der Homebridge Log sieht doch nicht nach einem Fehler für den "GaOstTemp" aus oder?
Die Frage ist auch ob es überhaupt möglich ist in der "Home"App einem generic Device ("Temperature Sensor") außer den Standards Temperatur und rel. Luftfeuchtigkeit ein weiteres "Detail" (in meinem Fall der Taupunkt) beizubringen diesen anzuzeigen.
D.h. ja die Characteristic "Current Temperature" würde 2 mal, jedoch mit anderem Name benutzt.

Code Auswählen Erweitern
[1/6/2017, 10:37:46 AM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,minValue=-30,name=Temperatur CurrentTemperature=dew,name=Taupunkt CurrentRelativeHumidity=humidity [1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp is thermometer [1/6/2017, 10:37:46 AM] [FHEM] GaOstTemp has [1/6/2017, 10:37:46 AM] [FHEM] Custom Temperatur [temperature] [1/6/2017, 10:37:46 AM] [FHEM] Custom Taupunkt [dew] [1/6/2017, 10:37:46 AM] [FHEM] CurrentRelativeHumidity [humidity] 2017-01-06 10:37:46 caching: GaOstTemp-temperature: 6.5� [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Temperatur: 6.5 (as number; from '6.5�') 2017-01-06 10:37:46 caching: GaOstTemp-dew: -3.87 [1/6/2017, 10:37:46 AM] [FHEM] caching: Custom Taupunkt: -3.87 (as number; from '-3.87') 2017-01-06 10:37:46 caching: GaOstTemp-humidity: 47.3� [1/6/2017, 10:37:46 AM] [FHEM] caching: CurrentRelativeHumidity: 47 (as number; from '47.3�')

------------------------------------------

Die "Home App" kann das in der Tat nicht!
Nimm die "Eve App", die kann mehrere Temperaturen in einem Device anzeigen.

Gruß
Dan

Steffen@Home · 10 Januar 2017, 14:49:08

Zitat von: DeeSPe am 10 Januar 2017, 14:14:45
Die "Home App" kann das in der Tat nicht!
Nimm die "Eve App", die kann mehrere Temperaturen in einem Device anzeigen.

Gruß
Dan

Hallo Dan, die habe ich auch, aber das Problem war ja dass dann die Bridge nicht mehr funktionierte.

DeeSPe · 10 Januar 2017, 14:59:25

Zitat von: Steffen@Home am 10 Januar 2017, 14:49:08
Hallo Dan, die habe ich auch, aber das Problem war ja dass dann die Bridge nicht mehr funktionierte.

Dann lag es sicher an einem nicht richtigen homebridgeMapping.

Gruß
Dan

Steffen@Home · 10 Januar 2017, 22:44:00

Hallo Dan,

habe es nocheinmal versucht mit:

Code Auswählen

CurrentTemperature=temperature,minValue=-20,name=Temperatur CurrentTemperature=dew,minValue=-20,name=Taupunkt CurrentRelativeHumidity=humidity

Die Homebridge bringt folgenden Log:

Code Auswählen

[1/10/2017, 10:39:14 PM] [FHEM] Initializing platform accessory 'GaOstTemp'...
[1/10/2017, 10:39:14 PM] [FHEM] creating services for GaOstTemp
[1/10/2017, 10:39:14 PM] [FHEM]   information service for GaOstTemp
[1/10/2017, 10:39:14 PM] [FHEM]     manufacturer, model and serial number characteristics for GaOstTemp
[1/10/2017, 10:39:14 PM] [FHEM]   TemperatureSensor service for GaOstTemp
[1/10/2017, 10:39:14 PM] [FHEM]     CurrentTemperature characteristic for GaOstTemp:temperature
[1/10/2017, 10:39:14 PM] [FHEM] GaOstTemp: CurrentTemperature characteristic already defined for service GaOstTemp and no subtype given
[1/10/2017, 10:39:14 PM] [FHEM]   TemperatureSensor service for GaOstTemp
[1/10/2017, 10:39:14 PM] [FHEM]     CurrentTemperature characteristic for GaOstTemp:dew
[1/10/2017, 10:39:14 PM] [FHEM]     CurrentRelativeHumidity characteristic for GaOstTemp:humidity
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131
        throw new Error("Cannot add a Service with the same UUID '" + existing.UUID + "' as another Service in this Accessory without also defining a unique 'subtype' p$
        ^

Error: Cannot add a Service with the same UUID '0000008A-0000-1000-8000-0026BB765291' as another Service in this Accessory without also defining a unique 'subtype' prop$
    at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131:15)
    at /usr/local/lib/node_modules/homebridge/lib/server.js:415:19
    at Array.forEach (native)
    at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:399:14)
    at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:361:32)
 at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-fhem/index.js:994:22)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-fhem/node_modules/request/request.js:187:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)

DeeSPe · 10 Januar 2017, 22:53:37

Zitat von: Steffen@Home am 10 Januar 2017, 22:44:00
Hallo Dan,

habe es nocheinmal versucht mit:
Code Auswählen Erweitern
CurrentTemperature=temperature,minValue=-20,name=Temperatur CurrentTemperature=dew,minValue=-20,name=Taupunkt CurrentRelativeHumidity=humidity

Die Homebridge bringt folgenden Log:
Code Auswählen Erweitern
[1/10/2017, 10:39:14 PM] [FHEM] Initializing platform accessory 'GaOstTemp'... [1/10/2017, 10:39:14 PM] [FHEM] creating services for GaOstTemp [1/10/2017, 10:39:14 PM] [FHEM] information service for GaOstTemp [1/10/2017, 10:39:14 PM] [FHEM] manufacturer, model and serial number characteristics for GaOstTemp [1/10/2017, 10:39:14 PM] [FHEM] TemperatureSensor service for GaOstTemp [1/10/2017, 10:39:14 PM] [FHEM] CurrentTemperature characteristic for GaOstTemp:temperature [1/10/2017, 10:39:14 PM] [FHEM] GaOstTemp: CurrentTemperature characteristic already defined for service GaOstTemp and no subtype given [1/10/2017, 10:39:14 PM] [FHEM] TemperatureSensor service for GaOstTemp [1/10/2017, 10:39:14 PM] [FHEM] CurrentTemperature characteristic for GaOstTemp:dew [1/10/2017, 10:39:14 PM] [FHEM] CurrentRelativeHumidity characteristic for GaOstTemp:humidity /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131 throw new Error("Cannot add a Service with the same UUID '" + existing.UUID + "' as another Service in this Accessory without also defining a unique 'subtype' p$ ^ Error: Cannot add a Service with the same UUID '0000008A-0000-1000-8000-0026BB765291' as another Service in this Accessory without also defining a unique 'subtype' prop$ at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:131:15) at /usr/local/lib/node_modules/homebridge/lib/server.js:415:19 at Array.forEach (native) at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:399:14) at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:361:32) at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19 at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-fhem/index.js:994:22) at Request.self.callback (/usr/local/lib/node_modules/homebridge-fhem/node_modules/request/request.js:187:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7)

Statt name musst Du subtype benutzen!

Gruß
Dan

Steffen@Home · 10 Januar 2017, 23:20:48

es klappt Juhu! Danke vielmals

Habe jetzt übrigens zwei Symbole in der Home App: Temperatur wie immer und den Taupunkt extra. Super!

Code Auswählen

CurrentTemperature=temperature,minValue=-20,subtype=Temperatur  CurrentTemperature=dew,minValue=-20,subtype=Taupunkt  CurrentRelativeHumidity=humidity

Code Auswählen

[1/10/2017, 11:08:07 PM] [FHEM] homebridgeMapping: CurrentTemperature=temperature,minValue=-20,subtype=Temperatur  CurrentTemperature=dew,minValue=-20,subtype=Ta$
[1/10/2017, 11:08:07 PM] [FHEM] GaOstTemp is thermometer
[1/10/2017, 11:08:07 PM] [FHEM] GaOstTemp has
[1/10/2017, 11:08:07 PM] [FHEM]   CurrentTemperature [temperature]
[1/10/2017, 11:08:07 PM] [FHEM]   CurrentTemperature [dew]
[1/10/2017, 11:08:07 PM] [FHEM]   CurrentRelativeHumidity [humidity]
  2017-01-10 23:08:07 caching: GaOstTemp-temperature: 7.0^@
[1/10/2017, 11:08:07 PM] [FHEM]     caching: CurrentTemperature:Temperatur: 7 (as number; from '7.0^@')
  2017-01-10 23:08:07 caching: GaOstTemp-dew: -3.10
[1/10/2017, 11:08:07 PM] [FHEM]     caching: CurrentTemperature:Taupunkt: -3.1 (as number; from '-3.10')
  2017-01-10 23:08:07 caching: GaOstTemp-humidity: 48.6^@
[1/10/2017, 11:08:07 PM] [FHEM]     caching: CurrentRelativeHumidity: 48 (as number; from '48.6^@')

Jetzt hab ich nur noch 1ne rote Zeile drin: kann ich das vernachlässigen?

Code Auswählen

[1/10/2017, 11:13:04 PM] [FHEM] DenonAVR-power not a number: off
[1/10/2017, 11:13:04 PM] [FHEM]     caching: On: false (as boolean; from 'off')

Code Auswählen

[1/10/2017, 11:13:05 PM] [FHEM] Initializing platform accessory 'DenonAVR'...
[1/10/2017, 11:13:05 PM] [FHEM] creating services for DenonAVR
[1/10/2017, 11:13:05 PM] [FHEM]   information service for DenonAVR
[1/10/2017, 11:13:05 PM] [FHEM]     manufacturer, model and serial number characteristics for DenonAVR
[1/10/2017, 11:13:05 PM] [FHEM]   Switch service for DenonAVR
[1/10/2017, 11:13:05 PM] [FHEM]     Custom Volume characteristic for DenonAVR:volume
[1/10/2017, 11:13:05 PM] [FHEM]     Custom Power characteristic for DenonAVR:power
[1/10/2017, 11:13:05 PM] [FHEM]     On characteristic for DenonAVR:power

und was hat das hier auf sich? Muss ich etwas ändern?

Code Auswählen

*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>

Hauswart · 11 Januar 2017, 14:02:44

Zitat von: Hauswart am 10 Januar 2017, 07:57:41
Ich habe gestern mal von homebridge-fhem 0.2.67 auf 0.2.68 geupdatet und kann seitdem homebridge nicht mehr starten und erhalte folgende Fehlermeldung:

So ich habe mal ein Device davor als genericType garage definiert und erhalte eine neue Fehlermeldung.

Die Zeile im Code habe ich auch gefunden: https://github.com/justme-1968/homebridge-fhem/blob/master/index.js#L1520

Habe homebridge und homebridge-fhem mit "sudo npm -g install" neu installiert, aber der Fehler bleibt?

justme1968 · 11 Januar 2017, 15:56:11

dein dummy braucht eine setList mit zwei einträgen oder gar keine. zeig mal ein jsonlist2 von dem dummy.

homebridge/homekit

jensenbln

MrFisch