hallo zusammen,
die ,,Geräte" die ich mit dem Filter des fhem PlugIn der homebridge zuweise, werden in dieser auch angeigt.
In meine Fall sind es Sensoren für die Tür- bzw. Fensterüberwachung.
- natürlich sind auch die Änderungen der Zustände in der homebridge ersichtlich.
Mein Problem ist, das die Geräte nicht an die home-App des iPhones weitergegeben werden.
Geräte bzw. Anzeigen von anderen PlugIns aber sehr wohl.
Hat jemand eine Idee, woran daliegen könnte?
Vielen Dank im Voraus
Gruss Silvio
Das wird dann eher an den Geräten liegen. Manchmal muss man das Attribut genericDeviceType manuell pflegen und wenn es Dumm läuft, dann auch noch homebridgeMapping und die können ziemlich häßlich/umständlich werden.
Bitte mal von einem Gerät ein list hier zeigen.
Hatte meine HomeBridge vor ca. 4 Jahren eingerichtet und da gingen alle Geräte. Jetzt habe ich den Server umgezogen und die HB neu installiert.
Folgende genericType gehen jetzt nicht mehr:
- genericDeviceType contact # für alle meine Fensterkontakte gesetzt
- genericDeviceType TemperatureSensor # Außentemperatur mit Feuchtigkeit
Im log von HB werden diese fehlerfrei erkannt, aber nicht in der HomeApp angezeigt.
Elektrolurch
Meine Fensterkontake habe ich manuell auf 'ContactSensor' gesetzt. Dieser Wert wird zumindest bei meinem Fensterkontakten nicht in der Combobox angeboten, sondern muss manuell gesetzt werden.
setreading <Device> genericDeviceType ContactSensor
Und bei meinen HUEDevices von Lumi, die über deconz eingebunden sind, habe ich manuell gar nichts eingestellt, die erscheinen auch ohne Angabe auf dem iPad/iPhone.
Danke erst einmal für die Antworten.
Ich werde es mit dem
setreading <Device> genericDeviceType ContactSensor
testen
Könnte ich ein Beispiel haben?
hier ein listing von einem Sensor
#
define Tuer_Wohnzimmer CUL_HM 21EB1E
setuuid Tuer_Wohnzimmer 604e3ea5-f33f-252c-4a39-d8fc6a1b9c1e6260
attr Tuer_Wohnzimmer .devInfo 910101
attr Tuer_Wohnzimmer .stc 80
attr Tuer_Wohnzimmer IODev HMLAN1
attr Tuer_Wohnzimmer actCycle 028:00
attr Tuer_Wohnzimmer actStatus unknown
attr Tuer_Wohnzimmer autoReadReg 4_reqStatus
attr Tuer_Wohnzimmer expert defReg,rawReg
attr Tuer_Wohnzimmer firmware 2.1
attr Tuer_Wohnzimmer model HM-SEC-RHS
attr Tuer_Wohnzimmer room SENSOREN
attr Tuer_Wohnzimmer serialNr KEQ0551615
attr Tuer_Wohnzimmer subType threeStateSensor
define FileLog_Tuer_Wohnzimmer FileLog ./log/Tuer_Wohnzimmer-%Y.log Tuer_Wohnzimmer
setuuid FileLog_Tuer_Wohnzimmer 604e3ea5-f33f-252c-d480-8206fd1f89523a86
attr FileLog_Tuer_Wohnzimmer logtype text
attr FileLog_Tuer_Wohnzimmer room SENSOREN
#
Gruss Silvio
Sorry, mein Fehler, hier haben wir ein Attribut, kein Reading.
attr FensterWohnzimmer genericDeviceType ContactSensor
habe nun das listing zum Wohnzimmer:
#
define Tuer_Wohnzimmer CUL_HM 21EB1E
setuuid Tuer_Wohnzimmer 604e3ea5-f33f-252c-4a39-d8fc6a1b9c1e6260
attr Tuer_Wohnzimmer .devInfo 910101
attr Tuer_Wohnzimmer .stc 80
attr Tuer_Wohnzimmer IODev HMLAN1
attr Tuer_Wohnzimmer actCycle 028:00
attr Tuer_Wohnzimmer actStatus unknown
attr Tuer_Wohnzimmer autoReadReg 4_reqStatus
attr Tuer_Wohnzimmer expert defReg,rawReg
attr Tuer_Wohnzimmer firmware 2.1
attr Tuer_Wohnzimmer model HM-SEC-RHS
attr Tuer_Wohnzimmer room SENSOREN
attr Tuer_Wohnzimmer serialNr KEQ0551615
attr Tuer_Wohnzimmer subType threeStateSensor
attr Tuer_Wohnzimmer genericDeviceType ContactSensor
define FileLog_Tuer_Wohnzimmer FileLog ./log/Tuer_Wohnzimmer-%Y.log Tuer_Wohnzimmer
setuuid FileLog_Tuer_Wohnzimmer 604e3ea5-f33f-252c-d480-8206fd1f89523a86
attr FileLog_Tuer_Wohnzimmer logtype text
attr FileLog_Tuer_Wohnzimmer room SENSOREN
#
bringt aber leider keine Änderung
Gruss Silvio
Hast du die Homebridge neu gestartet?
ja, das habe ich gemacht.
Hallo Silvio,
wenn du
attr Tuer_Wohnzimmer genericDeviceType ContactSensor
verwendest, solltest du noch folgendes hinzufügen
attr Tuer_Wohnzimmer homebridgeMapping ContactSensorState=state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTED
wobei der Text bei values=closed/open dem entsprechen muss, welches dein Device unter state anzeigt, wenn der Kontakt besteht/nicht besteht.
Steht übrigens hier (https://wiki.fhem.de/wiki/Homebridge_User_Configs#EnOcean_STM_250_T.C3.BCr-.2FFensterkontakt) ;)
Nach den Änderungen Homebrigde neu starten nicht vergessen.
Hinweis (https://wiki.fhem.de/wiki/Homebridge_einrichten#Hinweis)
Gruß Karsten
Hallo Karsten,
Danke das probiere ich heute Nachmittag aus.
Du meinst das:
attr STM250 genericDeviceType ContactSensor
attr STM250 homebridgeMapping ContactSensorState=state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTED
Wobei... ich glaube das habe ich gestern Abend schon getestet und bekam beim speichern von fhem.cfg eine Fehlermeldung zurück.
Den Wortlaut der Fehlermeldung hab ich nicht mehr im Kopf.
melde mich dann wieder
Gruss Silvio
Ich habe jetzt
attr <Fenster> genericDeviceType ContactSensor
gesetzt und es geht nach Neustart der homebridge trotzdem nicht.
In der Home-App bleibendie Fenster weiterhin unsichtbar.
Da das ja alles mit der älteren Version der homebridge über Jahre alles funktionierte und jetzt erst nach dem Update die beiden Gerätetypen ContactSensoer und TemperaturSensor nicht mehr in der HomeApp angezeigt werden, denke ich, liegt es an der aktuellen VErsion der homebridge.
Das log, welches HB beim Start schreibt, ist bezüglich der o.g. Sensoren fehlerfrei.
Elektrolurch
Hallo Elektrolurch,
du musst zusätzlich auch das Homebridgemapping setzen.
(vorher an dein Device anpassen nicht vergessen)
wenn du das Attribut "ContactSensor" verwendest.
Zu Themperatursensor:
versuch mal
attr <Sensor> genericDeviceType thermometer
und
attr <Sensor> homebridgeMapping CurrentRelativeHumidity=humidity
CurrentTemperature=temperature
BatteryLevel=battery_level
StatusLowBattery=battery,values=ok:BATTERY_LEVEL_NORMAL;/^.*/:BATTERY_LEVEL_LOW
Gruß Karsten
Hallo,
@Elektrolurch, wenn du der Meinung bist, das es an der aktuellen Version liegt (1.33) dann kannst du, sofern du die Homebridge-UI nutzt, ja relativ einfach zurück auf eine vorherige Version, nur in die UI von Homebridge und auf die Versions-Nr tippen, hier also v1.3.3, und eine andere Versionsnummer auswählen.Als Tipp die 1.3.2 funktioniert bei mir einwandfrei, auch ohne das ich bei meinen Homematic Fensterkontakten irgendetwas ändern oder anpassen musste.
Gruß Thomas
An iphone_wolf. Ich sehe gerade, dass dein Türsensor nur im Raum SENSOREN ist. Wenn das nicht dein HomeBridge Raum ist, wird der auch nicht erscheinen, egal, was du sonst machst.
Hallo jhohmann, '
Der Raum SENSOREN ist mit Filter in der homebridge gesetzt.
Dort werden sie ja auch angezeigt, nur nicht in der home-App.
Hallo Karsten
Hier die Fehlermeldung:
Unknown command open:CONTACT_NOT_DETECTED, try help.
Wenn das attr Tuer_Wohnzimmer homebridgeMapping ContactSensorState=state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTED
gesetzt ist.
Ich habe ,,;open:CONTACT_NOT_DETECTED" mal auskommentiert.
Dann gibt es zwar keine Fehlermeldung, aber auch keine Änderung der Anzeige in der home-App des Iphone
Gruss Silvio
@Silvio
Was für ein state hat dein Device wen der Kontakt geschlossen, bzw. geöffnet ist?
Hallo Karsten,
das sind ja threestate Sensoren
open, tilted, closed
Die Hardwarezustände sind gleich der Softwarezustände.
Ich habe aber auch die GaragenSensoren umgeschrieben.
Die haben nur 2 Zustände open und closed.
- also die zusätzlichen attr hinzugefügt.
Hat auch nicht funktioniert.
Jetzt habe ich den room "SENSOREN" in fhem und homebridge auf "HomeKit" umgeschrieben - auch nichts....
Gruss Silvio
Hallo Silvio,
das ist etwas seltsam ???
Kannst du mal bitte einen Switch mappen, und nachsehen ob er in der Homebridge unter Geräte erscheint.
Wenn ja, dann auch mal bitte noch in der Home-App unter deinem angelegten Raum (Standardraum für deine Devices) nachsehen, ob er dort auch vorhanden ist.
Ich habe gerade folgenden Switch bei mir angelegt, und er funktioniert einwandfrei.
RAW-Code
defmod du_test_hb dummy
attr du_test_hb genericDeviceType switch
attr du_test_hb homebridgeMapping On=state,cmdOn=on,cmdOff=off
attr du_test_hb room 04_Homekit,99_Test->Dummy
attr du_test_hb webCmd on:off
Den Kontaktsensor habe ich auch erst heute morgen angelegt, und er funktioniert wie er soll, auch in der App.
RAW-Code
defmod xi_sensor_contact_01 XiaomiMQTTDevice MCCGQ11LM 0x00158d000309bfde xi_sensor_contact_01 zigbee2mqtt
attr xi_sensor_contact_01 IODev Mosquitto
attr xi_sensor_contact_01 devStateIcon open:fts_door_open@red close:fts_door@green
attr xi_sensor_contact_01 event-on-change-reading state
attr xi_sensor_contact_01 genericDeviceType ContactSensor
attr xi_sensor_contact_01 group zone_apartment_general
attr xi_sensor_contact_01 homebridgeMapping ContactSensorState=state,values=close:CONTACT_DETECTED;;open:CONTACT_NOT_DETECTED
attr xi_sensor_contact_01 room 00_Wohnung->Flur,04_Homekit,05_Zigbee2mqtt->Devices
homebridge v1.3.3
homebridge-config-ui-x v4.40.0
homebridge-fhem v0.5.29
Node.js v14.16.0
Npm Version v7.6.3
Wenn das nicht funktionieren sollte, dann stimmt etwas an deiner Homebridge-Installation nicht.
Gruß Karsten
Hallo Karsten,
alle Sensoren sind in der homebridge sichtbar und die Zuständen passen zu der Hardware.
gegebenenfalls stimmt die json nicht
{
"name": "FHEM",
"server": "192.168.178.28",
"port": 8083,
"filter": "room=HomeKit",
"auth": {
"user": "xxxx",
"pass": "xxxx"
},
"platform": "FHEM",
"_bridge": {
"username": "0E:B8:72:80:D7:18",
"port": 33977
}
}
muss dann erst mal wieder weg - melde mich später
Gruss Silvio
@Silvio
Zitat von: Iphone_wolf am 15 März 2021, 14:10:44
Der Raum SENSOREN ist mit Filter in der homebridge gesetzt.
Zitat von: Iphone_wolf am 15 März 2021, 16:52:08
...
"filter": "room=HomeKit",
...
Entweder bleibt dein Filter bei "room=HomeKit" und du musst deine Devices dort reinschieben,
oder du wechselst den Filter auf "room=SENSOREN" und deine Sensoren müssten wieder sichtbar sein.
So wie es jetzt ist, kann es nicht funktionieren.
Beispiel wie die config bei mir aussieht
{
"bridge": {
"name": "Homebridge",
"username": "XX:XX:XX:XX:XX:XX",
"port": 12345,
"pin": "XXX-XX-XXX"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 1234,
"platform": "config"
},
{
"platform": "FHEM",
"name": "FHEM",
"server": "127.0.0.1",
"port": "8083",
"auth": {
"user": "XXX",
"pass": "XXX"
},
"filter": "room=04_Homekit"
}
]
}Gruß Karsten
Edit:
Kann es sein das du deine Homebridge noch garnicht an deiner Home-App angemeldet hast?
Hallo Karsten,
da sind ein paar Sachen durcheinander gekommen.
room(in fhem) und filter(in homebridge) sind gleich - ich habe nur auf HomeKit umgestellt, da ich vermutete, dass die homebridge eventuell braucht - als Schlüsselwort.
Zitat von: jhohmann am 15 März 2021, 11:33:28
An iphone_wolf. Ich sehe gerade, dass dein Türsensor nur im Raum SENSOREN ist. Wenn das nicht dein HomeBridge Raum ist, wird der auch nicht erscheinen, egal, was du sonst machst.
Damit meinst du im fhem:
attr Tuer_Wohnzimmer room HomeKit
und in der homebridge:
"filter": "room=HomeKit",Die homebridge ist in der home-App angemeldet und andere PlugIn's z.B. das deebot zeigt sein Geräte/Sensoren in der der homebridge und in der home-App auf iPhone - Ich kann also den Saugroboter von der home-App oder in der Eve-App steuern.
Gruss Silvio
was andere homebridge plugins machen ist völlig egal.
es nützt nichts in fhem herumzurätseln ohne ins homebridge log zu schauen.
wenn du etwas Über die kommandozeile eingibst müssen ; verdoppelt werden. deshalb ist es einfacher das ganze im webfrontend im dafür vorgesehenen attribut feld einzutragen.
Sorry, jetzt stehe ich etwas auf der Leitung.
Verstehe nicht, was du meinst?
Ich soll im fhem webfrontend befehle eingeben und schauen was dann im log der homebridge steht?
Nein!
Sondern: Eingaben generell (bzw. mind. homebridgeMapping) per Webinterface und dafür vorgesehenen Eingabemethoden beim jeweiligen Device...
Oder eben die Strichpunkte etc. "beachten", wenn du über andere Wege eingibst...
Und auch "generell" im homebridge-Log schauen was dort steht.
Also z.B. die Ausgaben bzgl. "Device-Erkennung" etc.
EDIT: oder halt hier posten, dann können wir (bzw. Andre) drüber schauen...
Gruß, Joachim
ich habe hier mal den log aus der homebridge:
2021-03-15 21:28:23 caching: Tuer_SilviosZimmer-contact: open (to HMLAN1)
[15/03/2021, 21:28:23] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'open (to HMLAN1)')
[15/03/2021, 21:28:23] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'open (to HMLAN1)')
2021-03-15 21:28:25 caching: Tuer_SilviosZimmer-contact: tilted (to HMLAN1)
[15/03/2021, 21:28:25] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'tilted (to HMLAN1)')
[15/03/2021, 21:28:25] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'tilted (to HMLAN1)')
2021-03-15 21:28:28 caching: Tuer_SilviosZimmer-contact: open (to HMLAN1)
[15/03/2021, 21:28:28] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'open (to HMLAN1)')
[15/03/2021, 21:28:28] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'open (to HMLAN1)')
2021-03-15 21:28:30 caching: Tuer_SilviosZimmer-contact: closed (to HMLAN1)
[15/03/2021, 21:28:30] [FHEM] caching: ContactSensorState: 0 (as number; means CONTACT_DETECTED; from 'closed (to HMLAN1)')
[15/03/2021, 21:28:30] [FHEM] caching: CurrentDoorState: 1 (as number; means CLOSED; from 'closed (to HMLAN1)')
ich steh wirklich auf dem Schlauch... :o
ZitatSondern: Eingaben generell (bzw. mind. homebridgeMapping) per Webinterface und dafür vorgesehenen Eingabemethoden beim jeweiligen Device...
muss mich ja in euren Augen ziemlich blöd anstellen - SORRY - Danke für die Geduld mit mir
Besser wären Auszüge aus dem Log wo man auch die Device-Erkennung sieht.
Am besten mal homebridge neu starten und dann das Log ab dem Neustart...
Da sieht man die Erkennung.
(ist zumindest bei alexa-fhem so und sollte hier auch so sein)
Gruß, Joachim
Hallo Silvio,
was hälst du davon das wir einmal folgendes versuchen.
Zuerst in der Homebridge den Filter auf "filter": "room=Homekit" setzen.
Anschliessend einen Dummy in Fhem anlegen.
defmod du_test_hb dummy
attr du_test_hb genericDeviceType switch
attr du_test_hb homebridgeMapping On=state,cmdOn=on,cmdOff=off
attr du_test_hb room Homekit
attr du_test_hb webCmd on:off
Homebridge neu starten.
Nach erfolgtem Neustart das Log der Homebridge (wie es von justme1968/MadMax-FHEM schon geschrieben wurde) hier zur Verfügung stellen.
Dann den Dummy in Fhem ein/ausschalten und in der Homebridge nachsehen ob sich der Schaltzustand dementsprechend ändert.
Um die Ansicht in der Home-App kümmern wir uns erst wenn die Verbindung FHEM <-> Homebridge funktioniert.
Gruß Karsten
Ist es nicht ausreichend beim dummy setList on off zu setzen, dann braucht man doch kein homebridgeMapping!?
(ist zumindest bei alexa-fhem so)
webCmd braucht man doch gar nicht, oder?
Aber egal, der dummy sollte wohl tun...
...und dann halt wie von Karsten (und anderen ;) ) vorgeschlagen vorgehen...
Gruß, Joachim
Hallo Joachim, hallo Karsten,
ich werde den dummy heute Nachmittag testen und mich wieder melden.
Gruss Silvio
so habe den dummy angelegt, musste die erste Anweisung aber in define ändern.
#
define du_test_hb dummy
attr du_test_hb genericDeviceType switch
attr du_test_hb homebridgeMapping On=state,cmdOn=on,cmdOff=off
attr du_test_hb room HomeKit
attr du_test_hb webCmd on:off
#
homebridge-log
Loading logs using native method...
File: /var/lib/homebridge/homebridge.log
[16/03/2021, 13:48:50] [Homebridge UI] Homebridge log truncated by sh_admin.
[16/03/2021, 13:48:56] [Homebridge UI] Homebridge restart request received
[16/03/2021, 13:48:56] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[16/03/2021, 13:48:56] [Homebridge UI] Sending SIGTERM to Homebridge
[16/03/2021, 13:48:56] Got SIGTERM, shutting down Homebridge...
[16/03/2021, 13:48:56] [DeebotEcovacs] INFO - shutdown
[16/03/2021, 13:48:56] Got SIGTERM, shutting down child bridge process...
[16/03/2021, 13:49:01] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[16/03/2021, 13:49:06] [HB Supervisor] Restarting Homebridge...
[16/03/2021, 13:49:06] [HB Supervisor] Starting Homebridge with extra flags: -I
[16/03/2021, 13:49:06] [HB Supervisor] Started Homebridge v1.3.3 with PID: 28481
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 13:49:07] Loaded config.json with 2 accessories and 3 platforms.
[16/03/2021, 13:49:07] Loaded 1 cached accessories from cachedAccessories.
[16/03/2021, 13:49:07] ---
[16/03/2021, 13:49:08] Loaded plugin: homebridge-config-ui-x@4.40.0
[16/03/2021, 13:49:08] Registering platform 'homebridge-config-ui-x.config'
[16/03/2021, 13:49:08] ---
[16/03/2021, 13:49:08] Loaded plugin: homebridge-deebotecovacs@1.4.5-beta.0
[16/03/2021, 13:49:08] Registering platform 'homebridge-deebotecovacs.DeebotEcovacs'
[16/03/2021, 13:49:08] ---
[16/03/2021, 13:49:08] Loaded plugin: homebridge-delay-switch@2.2.6
[16/03/2021, 13:49:08] Registering accessory 'homebridge-delay-switch.DelaySwitch'
[16/03/2021, 13:49:08] ---
[16/03/2021, 13:49:08] Loaded plugin: homebridge-fakebulb@0.0.3
[16/03/2021, 13:49:08] Registering accessory 'homebridge-fakebulb.FakeBulb'
[16/03/2021, 13:49:08] ---
[16/03/2021, 13:49:08] Loaded plugin: homebridge-fhem@0.5.29
homebridge API version: 2.7
this is homebridge-fhem 0.5.29
[16/03/2021, 13:49:10] Registering platform 'homebridge-fhem.FHEM'
[16/03/2021, 13:49:10] ---
[16/03/2021, 13:49:10] Loaded plugin: homebridge-meross@5.0.0
[16/03/2021, 13:49:10] Registering platform 'homebridge-meross.Meross'
[16/03/2021, 13:49:10] ---
[16/03/2021, 13:49:10] Loaded plugin: homebridge-mieleathome@2.8.0
[16/03/2021, 13:49:10] Registering platform 'homebridge-mieleathome.Miele@home'
[16/03/2021, 13:49:10] ---
[16/03/2021, 13:49:11] Loaded plugin: homebridge-rademacher-homepilot@0.8.1
[16/03/2021, 13:49:11] Registering platform 'homebridge-rademacher-homepilot.RademacherHomePilot'
[16/03/2021, 13:49:11] ---
[16/03/2021, 13:49:11] Loaded plugin: @mpathirage/homebridge-gosundsw2-esphome@1.0.14
[16/03/2021, 13:49:11] Registering accessory '@mpathirage/homebridge-gosundsw2-esphome.GosundDimmerSwitchESPHome'
[16/03/2021, 13:49:11] ---
[16/03/2021, 13:49:11] Loading 3 platforms...
[16/03/2021, 13:49:11] [Config] Initializing config platform...
[16/03/2021, 13:49:11] [Config] Running in Service Mode
[16/03/2021, 13:49:11] [FHEM] Initializing FHEM platform...
[16/03/2021, 13:49:11] [FHEM] Initializing child bridge 0E:B8:72:80:D7:18
[16/03/2021, 13:49:11] [DeebotEcovacs] Initializing DeebotEcovacs platform...
[16/03/2021, 13:49:11] [DeebotEcovacs] INFO - API :EU/DE
[16/03/2021, 13:49:11] Loading 2 accessories...
[16/03/2021, 13:49:11] [Mein Schalter] Initializing DelaySwitch accessory...
[16/03/2021, 13:49:11] [Test lamp] Initializing FakeBulb accessory...
[16/03/2021, 13:49:11] [Test lamp] Starting a fake bulb device with name 'Lamp1'...
[16/03/2021, 13:49:11] [DeebotEcovacs] DidFinishLaunching
Preparing Advertiser for 'Homebridge 1D0B 3724' using bonjour-hap backend!
Setup Payload:
X-HM://0023V0RWAFEPD
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 236-64-698 │
└────────────┘
Server listening on: http://<ip>:8282
Starting to advertise 'Homebridge 1D0B 3724' using bonjour-hap backend!
[16/03/2021, 13:49:11] Homebridge v1.3.3 (Homebridge 1D0B) is running on port 51640.
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 13:49:12] [FHEM] Launched child bridge with PID 28509
[16/03/2021, 13:49:12] [Test lamp] Power state for the 'Lamp1' is 0
homebridge API version: 2.7
this is homebridge-fhem 0.5.29
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - stopping deebots discovery, number of deebots found : 1
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - Discovered Deebot : Daisy
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - Edge Cleaning for Daisy : false
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - Spot Cleaning for Daisy : false
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - SpotArea Cleaning for Daisy : true
[16/03/2021, 13:49:13] [DeebotEcovacs] INFO - CustomArea Cleaning for Daisy : true
[16/03/2021, 13:49:14] Registering platform 'homebridge-fhem.FHEM'
[16/03/2021, 13:49:14] [FHEM] Loaded homebridge-fhem v0.5.29 child bridge successfully
Server error: Error: listen EADDRINUSE: address already in use :::8282
Server listening on: http://<ip>:8283
[16/03/2021, 13:49:14] Loaded 0 cached accessories from cachedAccessories.0EB87280D718.
starting longpoll: http://192.168.178.28:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1615898954448
[16/03/2021, 13:49:14] [FHEM] Checking devices and attributes...
[16/03/2021, 13:49:14] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:14] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=jsonlist2%20TYPE=siri&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:14] [FHEM] siri device is siri
[16/03/2021, 13:49:14] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7B$defs%7Bsiri%7D-%3E%7B%22homebridge-fhem%20version%22%7D%20=%20%220.5.29%22%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:14] [FHEM] Fetching FHEM devices...
[16/03/2021, 13:49:14] [FHEM] fetching: http://192.168.178.28:8083/fhem?cmd=jsonlist2%20room%3DHomeKit&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:15] [FHEM] got: 16 results
[16/03/2021, 13:49:15] [FHEM] Fenster_Speise is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Fenster_Speise has
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Fenster_Speise-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
[16/03/2021, 13:49:15] [FHEM] FileLog_Fenster_Speise: no service type detected
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Fenster_Speise (FileLog)
[16/03/2021, 13:49:15] [FHEM] FileLog_Garage_Links: no service type detected
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Garage_Links (FileLog)
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Garage_Rechts (FileLog)
[16/03/2021, 13:49:15] [FHEM] FileLog_Garage_Rechts: no service type detected
[16/03/2021, 13:49:15] [FHEM] FileLog_Tuer_AnkesZimmer: no service type detected
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Tuer_AnkesZimmer (FileLog)
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Tuer_SilviosZimmer (FileLog)
[16/03/2021, 13:49:15] [FHEM] FileLog_Tuer_SilviosZimmer: no service type detected
[16/03/2021, 13:49:15] [FHEM] FileLog_Tuer_WC: no service type detected
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Tuer_WC (FileLog)
[16/03/2021, 13:49:15] [FHEM] FileLog_Tuer_Wohnzimmer: no service type detected
[16/03/2021, 13:49:15] [FHEM] no accessory created for FileLog_Tuer_Wohnzimmer (FileLog)
[16/03/2021, 13:49:15] [FHEM] Garage_Links is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Garage_Links has
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery [battery]
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Garage_Links-battery: low
[16/03/2021, 13:49:15] [FHEM] caching: StatusLowBattery: 1 (as number; means BATTERY_LEVEL_LOW; from 'low')
2021-03-16 13:49:15 caching: Garage_Links-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
2021-03-16 13:49:15 caching: Garage_Links-contact: open (to broadcast)
[16/03/2021, 13:49:15] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'open (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'open (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] Garage_Rechts is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Garage_Rechts has
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery [battery]
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Garage_Rechts-battery: low
[16/03/2021, 13:49:15] [FHEM] caching: StatusLowBattery: 1 (as number; means BATTERY_LEVEL_LOW; from 'low')
2021-03-16 13:49:15 caching: Garage_Rechts-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
2021-03-16 13:49:15 caching: Garage_Rechts-contact: open (to HMLAN1)
[16/03/2021, 13:49:15] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'open (to HMLAN1)')
[16/03/2021, 13:49:15] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'open (to HMLAN1)')
[16/03/2021, 13:49:15] [FHEM] Tuer_AnkesZimmer is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Tuer_AnkesZimmer has
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery [battery]
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Tuer_AnkesZimmer-battery: ok
[16/03/2021, 13:49:15] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2021-03-16 13:49:15 caching: Tuer_AnkesZimmer-D-firmware: 2.1
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.1 (as string; from '2.1')
2021-03-16 13:49:15 caching: Tuer_AnkesZimmer-contact: closed (to broadcast)
[16/03/2021, 13:49:15] [FHEM] caching: ContactSensorState: 0 (as number; means CONTACT_DETECTED; from 'closed (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] caching: CurrentDoorState: 1 (as number; means CLOSED; from 'closed (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] Tuer_Schlafzimmer is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Tuer_Schlafzimmer has
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery [battery]
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Tuer_Schlafzimmer-battery: ok
[16/03/2021, 13:49:15] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2021-03-16 13:49:15 caching: Tuer_Schlafzimmer-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
2021-03-16 13:49:15 caching: Tuer_Schlafzimmer-contact: tilted (to broadcast)
[16/03/2021, 13:49:15] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'tilted (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'tilted (to broadcast)')
[16/03/2021, 13:49:15] [FHEM] Tuer_SilviosZimmer is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Tuer_SilviosZimmer has
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery [battery]
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Tuer_SilviosZimmer-battery: low
[16/03/2021, 13:49:15] [FHEM] caching: StatusLowBattery: 1 (as number; means BATTERY_LEVEL_LOW; from 'low')
2021-03-16 13:49:15 caching: Tuer_SilviosZimmer-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
2021-03-16 13:49:15 caching: Tuer_SilviosZimmer-contact: closed (to HMLAN1)
[16/03/2021, 13:49:15] [FHEM] caching: ContactSensorState: 0 (as number; means CONTACT_DETECTED; from 'closed (to HMLAN1)')
[16/03/2021, 13:49:15] [FHEM] caching: CurrentDoorState: 1 (as number; means CLOSED; from 'closed (to HMLAN1)')
[16/03/2021, 13:49:15] [FHEM] Tuer_WC is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Tuer_WC has
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Tuer_WC-D-firmware: 2.4
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.4 (as string; from '2.4')
[16/03/2021, 13:49:15] [FHEM] Tuer_Wohnzimmer is ContactSensor
[16/03/2021, 13:49:15] [FHEM] Tuer_Wohnzimmer has
[16/03/2021, 13:49:15] [FHEM] FirmwareRevision [D-firmware]
[16/03/2021, 13:49:15] [FHEM] ContactSensorState [contact]
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState [contact]
2021-03-16 13:49:15 caching: Tuer_Wohnzimmer-D-firmware: 2.1
[16/03/2021, 13:49:15] [FHEM] caching: FirmwareRevision: 2.1 (as string; from '2.1')
[16/03/2021, 13:49:15] [FHEM] homebridgeMapping: On=state,cmdOn=on,cmdOff=off
[16/03/2021, 13:49:15] [FHEM] du_test_hb is switch
[16/03/2021, 13:49:15] [FHEM] du_test_hb has
[16/03/2021, 13:49:15] [FHEM] On [state;on,off]
[16/03/2021, 13:49:15] Initializing platform accessory 'Fenster_Speise'...
[16/03/2021, 13:49:15] [FHEM] creating services for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] information service for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Fenster_Speise
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Fenster_Speise:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Fenster_Speise:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Fenster_Speise:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Fenster_Speise:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Fenster_Speise:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Fenster_Speise:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Garage_Links'...
[16/03/2021, 13:49:15] [FHEM] creating services for Garage_Links
[16/03/2021, 13:49:15] [FHEM] information service for Garage_Links
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Garage_Links
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Garage_Links
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Garage_Links
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Garage_Links
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery characteristic for Garage_Links:battery
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Garage_Links:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Garage_Links:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Garage_Links:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Garage_Links:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Garage_Links:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Garage_Links:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Garage_Rechts'...
[16/03/2021, 13:49:15] [FHEM] creating services for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] information service for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Garage_Rechts
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery characteristic for Garage_Rechts:battery
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Garage_Rechts:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Garage_Rechts:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Garage_Rechts:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Garage_Rechts:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Garage_Rechts:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Garage_Rechts:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Tuer_AnkesZimmer'...
[16/03/2021, 13:49:15] [FHEM] creating services for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] information service for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Tuer_AnkesZimmer
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery characteristic for Tuer_AnkesZimmer:battery
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Tuer_AnkesZimmer:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Tuer_Schlafzimmer'...
[16/03/2021, 13:49:15] [FHEM] creating services for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] information service for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Tuer_Schlafzimmer
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery characteristic for Tuer_Schlafzimmer:battery
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Tuer_Schlafzimmer:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Tuer_SilviosZimmer'...
[16/03/2021, 13:49:15] [FHEM] creating services for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] information service for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Tuer_SilviosZimmer
[16/03/2021, 13:49:15] [FHEM] StatusLowBattery characteristic for Tuer_SilviosZimmer:battery
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Tuer_SilviosZimmer:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Tuer_WC'...
[16/03/2021, 13:49:15] [FHEM] creating services for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] information service for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Tuer_WC
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Tuer_WC:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Tuer_WC:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Tuer_WC:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Tuer_WC:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Tuer_WC:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Tuer_WC:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'Tuer_Wohnzimmer'...
[16/03/2021, 13:49:15] [FHEM] creating services for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] information service for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] firmware revision characteristic for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] ContactSensor service for Tuer_Wohnzimmer
[16/03/2021, 13:49:15] [FHEM] ContactSensorState characteristic for Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom TimesOpened characteristic Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom LastActivation characteristic Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom OpenDuration characteristic Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] [FHEM] Custom ClosedDuration characteristic Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] [FHEM] CurrentDoorState characteristic for Tuer_Wohnzimmer:contact
[16/03/2021, 13:49:15] Initializing platform accessory 'du_test_hb'...
[16/03/2021, 13:49:15] [FHEM] creating services for du_test_hb
[16/03/2021, 13:49:15] [FHEM] information service for du_test_hb
[16/03/2021, 13:49:15] [FHEM] manufacturer, model and serial number characteristics for du_test_hb
[16/03/2021, 13:49:15] [FHEM] name (siriName) characteristic for du_test_hb
[16/03/2021, 13:49:15] [FHEM] Switch service for du_test_hb
[16/03/2021, 13:49:15] [FHEM] On characteristic for du_test_hb:state
Preparing Advertiser for 'FHEM 6BBB' using bonjour-hap backend!
Starting to advertise 'FHEM 6BBB' using bonjour-hap backend!
[16/03/2021, 13:49:15] Homebridge v1.3.3 (FHEM) is running on port 33977.
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Fenster_Speise-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Fenster_Speise-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Fenster_Speise%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Fenster_Speise:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Fenster_Speise:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Fenster_Speise-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Fenster_Speise%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Garage_Links-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Garage_Links-contact
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means CONTACT_NOT_DETECTED)
[16/03/2021, 13:49:16] [FHEM] query: StatusLowBattery for Garage_Links-battery
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means BATTERY_LEVEL_LOW)
[16/03/2021, 13:49:16] [FHEM] Garage_Links: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Garage_Links: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Garage_Links:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Garage_Links:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Garage_Links-contact
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means OPEN)
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Garage_Rechts-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Garage_Rechts-contact
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means CONTACT_NOT_DETECTED)
[16/03/2021, 13:49:16] [FHEM] query: StatusLowBattery for Garage_Rechts-battery
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means BATTERY_LEVEL_LOW)
[16/03/2021, 13:49:16] [FHEM] Garage_Rechts: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Garage_Rechts: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Garage_Rechts:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Garage_Rechts:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Garage_Rechts-contact
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means OPEN)
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Tuer_AnkesZimmer-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.1 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Tuer_AnkesZimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means CONTACT_DETECTED)
[16/03/2021, 13:49:16] [FHEM] query: StatusLowBattery for Tuer_AnkesZimmer-battery
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means BATTERY_LEVEL_NORMAL)
[16/03/2021, 13:49:16] [FHEM] Tuer_AnkesZimmer: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Tuer_AnkesZimmer: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Tuer_AnkesZimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Tuer_AnkesZimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Tuer_AnkesZimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means CLOSED)
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Tuer_Schlafzimmer-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Tuer_Schlafzimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means CONTACT_NOT_DETECTED)
[16/03/2021, 13:49:16] [FHEM] query: StatusLowBattery for Tuer_Schlafzimmer-battery
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means BATTERY_LEVEL_NORMAL)
[16/03/2021, 13:49:16] [FHEM] Tuer_Schlafzimmer: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Tuer_Schlafzimmer: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Tuer_Schlafzimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Tuer_Schlafzimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Tuer_Schlafzimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means OPEN)
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Tuer_SilviosZimmer-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Tuer_SilviosZimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 0 (as number; means CONTACT_DETECTED)
[16/03/2021, 13:49:16] [FHEM] query: StatusLowBattery for Tuer_SilviosZimmer-battery
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means BATTERY_LEVEL_LOW)
[16/03/2021, 13:49:16] [FHEM] Tuer_SilviosZimmer: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Tuer_SilviosZimmer: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Tuer_SilviosZimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Tuer_SilviosZimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Tuer_SilviosZimmer-contact
[16/03/2021, 13:49:16] [FHEM] cached: 1 (as number; means CLOSED)
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Tuer_WC-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.4 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Tuer_WC-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Tuer_WC%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] Tuer_WC: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Tuer_WC: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Tuer_WC:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Tuer_WC:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Tuer_WC-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Tuer_WC%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] query: FirmwareRevision for Tuer_Wohnzimmer-D-firmware
[16/03/2021, 13:49:16] [FHEM] cached: 2.1 (as string)
[16/03/2021, 13:49:16] [FHEM] query: ContactSensorState for Tuer_Wohnzimmer-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Tuer_Wohnzimmer%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer: Custom TimesOpened characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer: Custom LastActivation characteristic requires FakeGatoHistory
[16/03/2021, 13:49:16] [FHEM] query Custom OpenDuration for Tuer_Wohnzimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query Custom ClosedDuration for Tuer_Wohnzimmer:contact: 0
[16/03/2021, 13:49:16] [FHEM] query: CurrentDoorState for Tuer_Wohnzimmer-contact
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22Tuer_Wohnzimmer%22,%22contact%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] query: On for du_test_hb-state
[16/03/2021, 13:49:16] [FHEM] not cached
[16/03/2021, 13:49:16] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BReadingsVal(%22du_test_hb%22,%22state%22,%22%22)%7D&fwcsrf=csrf_109937400268002e15&XHR=1
[16/03/2021, 13:49:16] [FHEM] value:
2021-03-16 13:49:16 caching: Tuer_WC-contact:
[16/03/2021, 13:49:16] [FHEM] Tuer_WC-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Tuer_WC-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Tuer_WC-contact value not handled in values
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Current Door State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] value:
2021-03-16 13:49:16 caching: Fenster_Speise-contact:
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise-contact value not handled in values
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Contact Sensor State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] value:
2021-03-16 13:49:16 caching: Tuer_Wohnzimmer-contact:
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Contact Sensor State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer-contact value not handled in values
[16/03/2021, 13:49:16] [FHEM] value:
[16/03/2021, 13:49:16] [FHEM] Fenster_Speise-contact value not handled in values
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Current Door State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] value:
[16/03/2021, 13:49:16] [FHEM] Tuer_WC-contact value not handled in values
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Contact Sensor State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] value:
[16/03/2021, 13:49:16] [FHEM] Tuer_Wohnzimmer-contact value not handled in values
[16/03/2021, 13:49:16] [homebridge-fhem] This plugin generated a warning from the characteristic 'Current Door State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[16/03/2021, 13:49:16] [FHEM] value:
2021-03-16 13:49:16 caching: du_test_hb-state:
[16/03/2021, 13:49:16] [FHEM] caching: On: false (as boolean; from '')
[16/03/2021, 13:49:16] [FHEM] caching: On: false (as boolean; from '')
[16/03/2021, 13:51:03] [Test lamp] Power state for the 'Lamp1' is 0
Der dummy wird in fhem und in der homebridge angezeigt. - aber nicht in der home-App
Die Schaltzustände werden ebenfalls an fhem zurück gegeben.
Gruss Silvio
wenn defmod bei dir nicht geht ist den fhem ziemlich alt.
wenn du ein plugin in einer child bridge laufen lässt musst du diese extra mit der home app pairen bzw. hinzufügen.
Hallo justme1968,
der fhem Server ist neu aufgesetzt.
Die alte Version wollte sich nicht einmal in die homebridge integrieren.
Alt ist nur die fhem.cfg.
Der fhem-Server läuft auch nicht auf dem gleichen raspberryPi, sondern auf einem 2. raspberryPi.
Was meinst du damit?
Zitatwenn du ein plugin in einer child bridge laufen lässt musst du diese extra mit der home app pairen bzw. hinzufügen
Hallo Silvio,
schau mal hier nach
https://github.com/homebridge/homebridge/wiki/Child-Bridges (https://github.com/homebridge/homebridge/wiki/Child-Bridges)
Da wird es beschrieben.
(Umgesetzt hab ich das nicht, war nicht notwendig)
Gruß Karsten
die child bridge in deiner konfiguration taucht doch nicht von alleine auf. wenn du sie konfiguriert hast solltest du auch wissen warum und wie man sie benutzt. ganz abgesehen davon das sie hier unnötig ist.
Hallo justme1968,
sehe ich auch so.
Es muss doch mit deinem PlugIn funktionieren.
Wie schon geschrieben, habe ich den fhem-Server letztes Wochenende neu aufgesetzt.
Alt ist nur die fhe.cfg - die habe ich vom alten Server kopiert und eingesetzt.
Habe gerade noch mal die Anweisung getestet. "defmod du_test_hb dummy" -taucht auch in der homebridge auf - nur nicht in der home-App
Diesmal hat es funktioniert - hatte wohl einen Fehler drin.
hier mal die "Kopfdaten:
"attr global userattr devStateIcon devStateStyle genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long icon siriName sortby webCmd widgetOverride
attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global motd Error messages while initializing FHEM:\
configfile: Unknown command WEB, try help.\
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global verbose 3
#
define telnetPort telnet 7072 global
setuuid telnetPort 604e3ea4-f33f-252c-0d67-d83b1f3220db10aa
#
define WEB FHEMWEB 8083 global
setuuid WEB 604e3ea4-f33f-252c-7de3-d75ee55ef11fc1df
attr WEB editConfig 1
define siri siri
setuuid siri 604fb77e-f33f-252c-d84b-0abb026e4e7f716f
#
define WEBphone FHEMWEB 8084 global
setuuid WEBphone 604e3ea4-f33f-252c-0533-c3b4d87fa4ea59ac
attr WEBphone stylesheetPrefix smallscreen
define allowed_WEBphone allowed
setuuid allowed_WEBphone 604e3ea4-f33f-252c-762a-c09b0911e8d239ab
attr allowed_WEBphone basicAuth c2lsdmlvOldvbGYxOTY5
attr allowed_WEBphone validFor WEBphone
#
define WEBtablet FHEMWEB 8085 global
setuuid WEBtablet 604e3ea4-f33f-252c-e880-01ee69de7a22860d
attr WEBtablet stylesheetPrefix touchpad
# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog
setuuid Logfile 604e3ea5-f33f-252c-f06f-671d5de1f9f004a0
define autocreate autocreate
setuuid autocreate 604e3ea5-f33f-252c-8ce0-539ce1b9ab715c3e
attr autocreate filelog ./log/%NAME-%Y.log
define eventTypes eventTypes ./log/eventTypes.txt
setuuid eventTypes 604e3ea5-f33f-252c-9d22-7a5f884a9cbe5d70
# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create
setuuid initialUsbCheck 604e3ea5-f33f-252c-3aa5-b27c85e2740050d8
define HMLAN1 HMLAN 192.168.178.30:1000
setuuid HMLAN1 604e3ea5-f33f-252c-eb51-301e3692d49ac69c
attr HMLAN1 hmId 23A3ED
attr HMLAN1 hmLanQlen 1_min
attr HMLAN1 loadLevel 0:low,40:batchLevel,90:high,99:suspended
attr HMLAN1 wdTimer 25
#
define ActionDetector CUL_HM 000000
setuuid ActionDetector 604e3ea5-f33f-252c-27f4-d5b688f3d416f6d7
attr ActionDetector .mId no
attr ActionDetector event-on-change-reading .*
attr ActionDetector model ACTIONDETECTOR
attr ActionDetector room CUL_HM
attr ActionDetector subType virtual
define FileLog_ActionDetector FileLog ./log/ActionDetector-%Y.log ActionDetector
setuuid FileLog_ActionDetector 604e3ea5-f33f-252c-9b01-5f17bf96fb256d77
attr FileLog_ActionDetector room CUL_HM
#
Wenn ich einfach eine jungfreuliche fhem.cfg erstelle, in der nur der dummy drin ist - Das müsste doch dann gehen - oder?
Was muss die fhem.cfg unbedingt haben?
Gruss Silvio
Zitat von: Iphone_wolf am 16 März 2021, 17:16:13
Wenn ich einfach eine jungfreuliche fhem.cfg erstelle, in der nur der dummy drin ist - Das müsste doch dann gehen - oder?
Was muss die fhem.cfg unbedingt haben?
Gruss Silvio
Im Ordner /opt/fhem ist eine Test-fhem.cfg drin.
Einfach fhem mit dieser starten, geht auch manuell auf der Kommandozeile.
Vorher halt das "richtige" fhem stoppen...
Siehe hier: https://wiki.fhem.de/wiki/FHEM_startet_nicht_-_Tipps_zur_Fehlersuche
(z.B. "minimal-Konfig starten")
Gruß, Joachim
hmm
habe jetzt die minimal.cfg am Start und wenn ich dann den dummy eintrage:
defmod du_test_hb dummy
attr du_test_hb genericDeviceType switch
attr du_test_hb homebridgeMapping On=state,cmdOn=on,cmdOff=off
attr du_test_hb room HomeKit
attr du_test_hb webCmd on:off
bekomme ich das zurück:
ERROR:
du_test_hb: unknown attribute genericDeviceType. Type 'attr du_test_hb ?' for a detailed list. du_test_hb: unknown attribute homebridgeMapping. Type 'attr du_test_hb ?' for a detailed list.
ich habe die Anweisung über das webinterface eingetragen - damit hat er es dann genommen.
ABER - Es ist das Gleiche, wie vorher.... :-[
Gerät wird in homebridge angezeigt - aber nicht in der home-App.
hier der Inhalt der minimal.cfg:
attr global userattr cmdIcon devStateIcon:textField-long devStateStyle genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long icon siriName sortby webCmd webCmdLabel:textField-long widgetOverride
attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global statefile ./log/fhem.save
attr global verbose 3
define WEB FHEMWEB 8083 global
setuuid WEB 6050e3e1-f33f-252c-0c12-240a538ee3b4c25a
attr WEB editConfig 1
# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog
setuuid Logfile 6050e3e2-f33f-252c-ce94-d2bf627f3e60d7ac
define autocreate autocreate
setuuid autocreate 6050e3e2-f33f-252c-ddf0-25bb0dc654cef9c1
attr autocreate filelog ./log/%NAME-%Y.log
define eventTypes eventTypes ./log/eventTypes.txt
setuuid eventTypes 6050e3e2-f33f-252c-d9cb-2acc3d3bfa8b91d8
# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create
setuuid initialUsbCheck 6050e3e2-f33f-252c-8e22-bacab347457f938b
define siri siri
setuuid siri 6050e4b9-f33f-252c-73fa-2bf7515c9afcc174
#
define du_test_hb dummy
setuuid du_test_hb 6050e52e-f33f-252c-a907-401de004c96a61bb
attr du_test_hb genericDeviceType switch
attr du_test_hb homebridgeMapping On=state,cmdOn=on,cmdOff=off
attr du_test_hb room HomeKit
attr du_test_hb webCmd on:off
und hier der log von der homebridge:
[16/03/2021, 18:22:30] Got SIGTERM, shutting down child bridge process...
[16/03/2021, 18:22:35] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[16/03/2021, 18:22:40] [HB Supervisor] Restarting Homebridge...
[16/03/2021, 18:22:40] [HB Supervisor] Starting Homebridge with extra flags: -I
[16/03/2021, 18:22:40] [HB Supervisor] Started Homebridge v1.3.3 with PID: 30218
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 18:22:41] Loaded config.json with 2 accessories and 3 platforms.
[16/03/2021, 18:22:41] Loaded 1 cached accessories from cachedAccessories.
[16/03/2021, 18:22:41] ---
[16/03/2021, 18:22:42] Loaded plugin: homebridge-config-ui-x@4.40.0
[16/03/2021, 18:22:42] Registering platform 'homebridge-config-ui-x.config'
[16/03/2021, 18:22:42] ---
[16/03/2021, 18:22:42] Loaded plugin: homebridge-deebotecovacs@1.4.5-beta.0
[16/03/2021, 18:22:42] Registering platform 'homebridge-deebotecovacs.DeebotEcovacs'
[16/03/2021, 18:22:42] ---
[16/03/2021, 18:22:42] Loaded plugin: homebridge-delay-switch@2.2.6
[16/03/2021, 18:22:42] Registering accessory 'homebridge-delay-switch.DelaySwitch'
[16/03/2021, 18:22:42] ---
[16/03/2021, 18:22:42] Loaded plugin: homebridge-fakebulb@0.0.3
[16/03/2021, 18:22:42] Registering accessory 'homebridge-fakebulb.FakeBulb'
[16/03/2021, 18:22:42] ---
[16/03/2021, 18:22:42] Loaded plugin: homebridge-fhem@0.5.29
homebridge API version: 2.7
this is homebridge-fhem 0.5.29
[16/03/2021, 18:22:44] Registering platform 'homebridge-fhem.FHEM'
[16/03/2021, 18:22:44] ---
[16/03/2021, 18:22:44] Loading 3 platforms...
[16/03/2021, 18:22:44] [Config] Initializing config platform...
[16/03/2021, 18:22:44] [Config] Running in Service Mode
[16/03/2021, 18:22:44] [FHEM] Initializing FHEM platform...
[16/03/2021, 18:22:44] [FHEM] Initializing child bridge 0E:B8:72:80:D7:18
[16/03/2021, 18:22:44] [DeebotEcovacs] Initializing DeebotEcovacs platform...
[16/03/2021, 18:22:44] [DeebotEcovacs] INFO - API :EU/DE
[16/03/2021, 18:22:44] Loading 2 accessories...
[16/03/2021, 18:22:44] [Mein Schalter] Initializing DelaySwitch accessory...
[16/03/2021, 18:22:44] [Test lamp] Initializing FakeBulb accessory...
[16/03/2021, 18:22:44] [Test lamp] Starting a fake bulb device with name 'Lamp1'...
[16/03/2021, 18:22:44] [DeebotEcovacs] DidFinishLaunching
Preparing Advertiser for 'Homebridge 1D0B 3724' using bonjour-hap backend!
Setup Payload:
X-HM://0023V0RWAFEPD
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 236-64-698 │
└────────────┘
Server listening on: http://<ip>:8282
Starting to advertise 'Homebridge 1D0B 3724' using bonjour-hap backend!
[16/03/2021, 18:22:44] Homebridge v1.3.3 (Homebridge 1D0B) is running on port 51640.
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 18:22:45] [FHEM] Launched child bridge with PID 30246
[16/03/2021, 18:22:45] [Test lamp] Power state for the 'Lamp1' is 0
homebridge API version: 2.7
this is homebridge-fhem 0.5.29
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - stopping deebots discovery, number of deebots found : 1
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - Discovered Deebot : Daisy
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - Edge Cleaning for Daisy : false
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - Spot Cleaning for Daisy : false
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - SpotArea Cleaning for Daisy : true
[16/03/2021, 18:22:46] [DeebotEcovacs] INFO - CustomArea Cleaning for Daisy : true
[16/03/2021, 18:22:46] Registering platform 'homebridge-fhem.FHEM'
[16/03/2021, 18:22:47] [FHEM] Loaded homebridge-fhem v0.5.29 child bridge successfully
Server error: Error: listen EADDRINUSE: address already in use :::8282
Server listening on: http://<ip>:8283
[16/03/2021, 18:22:47] Loaded 0 cached accessories from cachedAccessories.0EB87280D718.
starting longpoll: http://192.168.178.28:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1615915367452
[16/03/2021, 18:22:47] [FHEM] Checking devices and attributes...
[16/03/2021, 18:22:47] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&fwcsrf=csrf_433428475640228&XHR=1
[16/03/2021, 18:22:47] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=jsonlist2%20TYPE=siri&fwcsrf=csrf_433428475640228&XHR=1
[16/03/2021, 18:22:47] [FHEM] siri device is siri
[16/03/2021, 18:22:47] [FHEM] executing: http://192.168.178.28:8083/fhem?cmd=%7B$defs%7Bsiri%7D-%3E%7B%22homebridge-fhem%20version%22%7D%20=%20%220.5.29%22%7D&fwcsrf=csrf_433428475640228&XHR=1
[16/03/2021, 18:22:47] [FHEM] Fetching FHEM devices...
[16/03/2021, 18:22:47] [FHEM] fetching: http://192.168.178.28:8083/fhem?cmd=jsonlist2%20room%3DHomeKit&fwcsrf=csrf_433428475640228&XHR=1
[16/03/2021, 18:22:48] [FHEM] got: 1 results
[16/03/2021, 18:22:48] [FHEM] homebridgeMapping: On=state,cmdOn=on,cmdOff=off
[16/03/2021, 18:22:48] [FHEM] du_test_hb is switch
[16/03/2021, 18:22:48] [FHEM] du_test_hb has
[16/03/2021, 18:22:48] [FHEM] On [state;on,off]
2021-03-16 18:22:48 caching: du_test_hb-state: on
[16/03/2021, 18:22:48] [FHEM] caching: On: true (as boolean; from 'on')
[16/03/2021, 18:22:48] Initializing platform accessory 'du_test_hb'...
[16/03/2021, 18:22:48] [FHEM] creating services for du_test_hb
[16/03/2021, 18:22:48] [FHEM] information service for du_test_hb
[16/03/2021, 18:22:48] [FHEM] manufacturer, model and serial number characteristics for du_test_hb
[16/03/2021, 18:22:48] [FHEM] name (siriName) characteristic for du_test_hb
[16/03/2021, 18:22:48] [FHEM] Switch service for du_test_hb
[16/03/2021, 18:22:48] [FHEM] On characteristic for du_test_hb:state
Preparing Advertiser for 'FHEM 6BBB' using bonjour-hap backend!
Starting to advertise 'FHEM 6BBB' using bonjour-hap backend!
[16/03/2021, 18:22:48] Homebridge v1.3.3 (FHEM) is running on port 33977.
[16/03/2021, 18:22:49] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:22:49] [FHEM] cached: true (as boolean)
[16/03/2021, 18:22:56] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:22:56] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:22:56] [FHEM] cached: true (as boolean)
[16/03/2021, 18:22:56] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:22:56] [FHEM] cached: true (as boolean)
[16/03/2021, 18:22:56] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:22:58] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:22:58] [FHEM] cached: true (as boolean)
[16/03/2021, 18:22:58] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:01] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:01] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:23:01] [FHEM] cached: true (as boolean)
[16/03/2021, 18:23:18] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:23] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:31] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:32] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:32] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:32] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:35] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:23:35] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:24:09] [Test lamp] Power state for the 'Lamp1' is 0
[16/03/2021, 18:24:09] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:24:09] [FHEM] cached: true (as boolean)
[16/03/2021, 18:24:09] [FHEM] query: On for du_test_hb-state
[16/03/2021, 18:24:09] [FHEM] cached: true (as boolean)
[16/03/2021, 18:24:09] [Test lamp] Power state for the 'Lamp1' is 0
/code]
Es ist alles ok. Du musst jetzt die Home App öffnen oben auf das + Zeichen gehen ein neues Gerät anlegen, ich habe keinen Code bzw. kann ihn nicht scannen , dann ,, mein Gerät wird hier nicht angezeigt wählen und Code manuell eingeben wählen und dort gibst du dann den Code der Homebridge, den du schon hast, ein. Jetzt musst du noch einen Raum auswählen/erstellen, tu dir einen Gefallen für die Zukunft und nimm einen allgemeinen Namen, dieser Raum wird in Zukunft der Sammelraum für alle neu hinzugefügten fhem devices, das sollte es dann aber auch gewesen sein.
Gruß Thomas
Edit: eventuell wird dir in Schritt 2 Fhem auch zur Auswahl angeboten, dann kannst du es ruhig auswählen.
Hallo Zhomas,
die homebridge ist schon angemeldet und sichtbar - andere Geräte in der homebridge werden in der App auch angezeigt - nur Geräte vom fhem Server nicht
Gruss Silvio
laut log hast du fhem in einer sub bridge. diese musst du extra pairen. oder die sub bridge aus der config entfernen. das hatten wir doch heute mittag schon.
Es ist exakt so wie Justme sagt und wie man es in jeder Anleitung zur aktuellen Homebridge nachlesen kann. Da du anscheinend diese Child Bridge nicht los wirst, integrier sie doch einfach, hat soweit ich weiss keine gravierenden Nachteile, nur so am Rande wärst du heute Mittag dem link von Hydrotec . https://github.com/homebridge/homebridge/wiki/Child-Bridges (//http://://github.com/homebridge/homebridge/wiki/Child-Bridges) gefolgt und hättest dort gelesen, wärest du da schon fertig gewesen.
Gruß Thomas
Hallo justme1968,
das hatte ich heute Mittag gelesen, aber dann nicht mehr daran gedacht und bin anderen Tipps hinterher - Sorry.
Hätte mir ne Menge Zeit und Arbeit erspart.
Die Geräte sind nun in der home-App / Eve zu sehen.
Danke an alle, die mich unterstützt haben
Gruss Silvio
Ende Gut alles Gut, ;) :)
Na dann viel Spaß mit fhem und homebridge.
Gruß Thomas
Edit: bitte noch ein ,,gelöst" an den Anfang des Betreff im ersten Beitrag setzen, Danke
Hallo Thomas,
vielen Dank. ;D
Gruss Silvio