Siemens Home Connect Hausgeräte

Begonnen von DasAndy, 19 November 2014, 14:31:46

Vorheriges Thema - Nächstes Thema

Taasba

nachdem der Connect wieder generell wieder funktioniert, habe ich imme rnoch das Problem, dass die Verbdindung nach 1 oder 2 Waschladungen abbricht:

Zitat2017.04.22 17:49:03 2: set command: init
2017.04.22 17:49:03 3: set WM6YH890 init : Specified appliance with haId SIEMENS-WM6YH890-68A40E00xxxx not found
2017.04.22 17:49:11 2: WM6YH890 found nothing to read, channel closed

mit dem letzten Eintrag wird dann das Log-File alle 10s mit 3 Meldungen "zugemüllt". Ein neues Anmelden an hcconn bringt leider nichts.

Wenn das nicht besser wird, dann werde ich wohl doch eine HM Steckdose mit Leistungsmessung verwenden.

Oder gibt es etwa Hilfe :-) zu dem Problem? :D

LG Taasba
- fhem mit RasPi3 (debian-jessie) - HomeMatic (CCU2 - HMLAN-Adapter) und diverse HM Komponenten - 6 G-Tags (Anwesenheitserkennung) - SolVisMax Remotecontrol
- CUL 433 (Eigenbau - Arduino Nano C1101) - Alexa

swhome

Woher kommt denn dieses set ... init command? Eigentlich wird init nur intern vewendet.

Du könntest ansonsten das verbose Attribut für die Waschmaschine definieren und mir dann ein längeres log zukommen lassen, zB per Dropbox. Dann schaue ich mir das mal an.
Im Einsatz: FHEM auf Raspberry Pi mit 350 devices, hauptsächlich Homematic Wired und HM-Heizungsregler, dazu diverse Eigenbauten für Fussbodenheizung und LED Beleuchtung. Und jetzt mit Alexa!

Dr. Boris Neubert

Hallo,

Danke für die Freischaltung des Accounts und für den Hinweis mit csrfToken.

Ich habe erstmal "simulator" genommen und kann die simulierten Geräte als Devices in sehen.

Wo finde ich denn die Anleitung, meine eigenen Geräte mit FHEM zu verbinden?

Viele Grüße
Boris
Globaler Moderator, Developer, aktives Mitglied des FHEM e.V. (Marketing, Verwaltung)
Bitte keine unaufgeforderten privaten Nachrichten!

Taasba

Hallo swhome,

woher das set command: init kommt weiss ich leider nicht. Ich habe nur über scanDevices die WM eingebunden. Den Code hatte ich nicht verändert.

!Allerdings! hatte ich in der Vergangeheit die Herausforderung, dass wenn die WM nicht mehr erkannt wurde, ich den Code aus der fhem.cfg entfernt hatte. Da bei einem enrneuten scanDevices die WM nicht erkannt wurde hatte ich den Code in fhem.cfg wieder eingefügt und gespeichert. Daraufhin ist fhem abgestürzt. Auch ein neuerliches starten von fhem brachte keinen Erfolg. Nachdem ich den Code wieder entfernt hatte konnte ich fhem wieder starten.

Ich habe die WM nachdem sie gestern über "scanDevices" auch nicht gefunden wurde heute wieder eingerichtet. Ein Attr. verbose 5 ist gesetzt. Sobald ich am Wochenende wieder wasche und der Fehler wieder auftaucht werde ich Dir den Log per PM als Link schicken.

Wie kann ich verbose in ein eigenes Log eintragen? Bei mir wird immer nur ins Hauptlogfile geschrieben, nicht aber in ein eigens für die WM definiertes

define WM6YH890 HomeConnect hcconn SIEMENS-WM6YH890-68A40E00xxxx
attr WM6YH890 alias Waschmaschine
attr WM6YH890 icon scene_washing_machine
attr WM6YH890 room Keller
attr WM6YH890 webCmd startProgram:stopProgram
define FileLog_WM6YH890 FileLog ./log/WM6YH890-%Y.log WM6YH890
attr FileLog_WM6YH890 logtype text
attr WM6YH890 verbose 5
attr FileLog_WM6YH890 room Keller



Hier mal ein Log-Eintrag:
Zitat2017.04.23 20:34:27 1: PERL WARNING: keys on reference is experimental at ./FHEM/48_HomeConnect.pm line 78.
2017.04.23 20:34:27 2: WM6YH890 defined as HomeConnect Washer SIEMENS WM6YH890
2017.04.23 20:34:31 2: WM6YH890 can't get https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH890-68A40E00xxxx/programs/available -- https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH890-68A40E00xxxx/programs/available: Select timeout/error:

Lieben Dank schon mal vorab  :D

LG Taasba
- fhem mit RasPi3 (debian-jessie) - HomeMatic (CCU2 - HMLAN-Adapter) und diverse HM Komponenten - 6 G-Tags (Anwesenheitserkennung) - SolVisMax Remotecontrol
- CUL 433 (Eigenbau - Arduino Nano C1101) - Alexa

swhome

Zitat von: Dr. Boris Neubert am 23 April 2017, 09:18:39
Wo finde ich denn die Anleitung, meine eigenen Geräte mit FHEM zu verbinden?
Einfach das Simulator aus der def der Connection entfernen und neu einloggen, dann gibts echte Geräte statt der simulierten.
Im Einsatz: FHEM auf Raspberry Pi mit 350 devices, hauptsächlich Homematic Wired und HM-Heizungsregler, dazu diverse Eigenbauten für Fussbodenheizung und LED Beleuchtung. Und jetzt mit Alexa!

Dr. Boris Neubert

Zitat von: swhome am 23 April 2017, 23:37:17
Einfach das Simulator aus der def der Connection entfernen und neu einloggen, dann gibts echte Geräte statt der simulierten.

Wow, ist ja toll! Geht. Danke.

Geht aber vermutlich nur, weil mein Webdeveloper-Account dieselbe E-Mail-Adresse hat wie diejenige, mit der ich meine Maschinen bei BSH registriert habe, oder? Ich finde sonst keine andere Möglichkeit, wie FHEM sonst meine Maschinen kennen sollte.
Globaler Moderator, Developer, aktives Mitglied des FHEM e.V. (Marketing, Verwaltung)
Bitte keine unaufgeforderten privaten Nachrichten!

no_Legend

Wie sieht es denn mittlerweile mit einem Release aus?
IntelNUC mit Ubuntu mit FHEM immer aktuell,2x HMLAN, CUL443, CUL868 -homekit/siri -tablet ui -homebridge
Device, diverse:
HM-SEC-KEY,HM-LC-BL1-FM,HM-SEC-SD,HM-Sen-DB-PCB,HM-Sec-RHS,HM-Sec-SC-2,HM-WDS10-TH-O,Harmony,Netamo, 433MHz Steckdosen uvm.

fuppking

Hallo,

ich habe auch eine WM mit HomeConnect und würde Sie auch gern in FHEM einbinden.

Jetzt hab ich mal eine Grundlegende Verständnissfrage.
Warum dauern solche "Freigaben vom Hersteller" immser so lange. So wie ich das Verfolge gibt es die
HomeConnect Funktion schon seit ca 2 Jahren. Wirklich getan hat sich für die "nicht Entwickler" nichts.
Genauso ist das auch mit der "Alexa" Funktion.
Bein "minderwertigen" Hausautomationssoftwareprogrammen funktioninert das teilweise alles.
Warum nicht in FHEM?? Wo liegt da der Wurm oder ist es wieder das gute alte Geld :)

Vielen Dank für eure Aufklärung

Taasba

#248
Hallo swhome,

und heute hier mal der Auszug aus dem LOG mit Verbose 5. Eine Waschladung lief ohne Probleme durch. Die 2. mit anderm Programm lief bis 2% und dann der Abbruch.

Fehlermeldungen inkl. Woran kann das liegen?

Lieben Dank und liebe Grüße

Taasba


2017.04.30 12:59:59 3: hcconn refreshing token
2017.04.30 13:00:00 2: set command: init
2017.04.30 13:00:00 4: WM6YH890 request: https://api.home-connect.com/api/homeappliances
2017.04.30 13:00:00 4: WM6YH890: no token refresh needed
2017.04.30 13:00:00 4: WM6YH890 response: {
  "data": {
    "homeappliances": [{
      "name": "Waschmaschine",
      "brand": "SIEMENS",
      "vib": "WM6YH890",
      "connected": true,
      "type": "Washer",
      "enumber": "WM6YH890/03",
      "haId": "SIEMENS-WM6YH890-68A40E00xxxx"
    }]
  }
}
2017.04.30 13:00:00 2: WM6YH890 defined as HomeConnect Washer SIEMENS WM6YH890
2017.04.30 13:00:00 4: WM6YH890 request: https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH890-68A40E00xxxx/status
2017.04.30 13:00:00 4: WM6YH890: no token refresh needed
2017.04.30 13:00:00 4: WM6YH890 response: {
  "data": {
    "status": [{
      "key": "BSH.Common.Status.DoorState",
      "value": "BSH.Common.EnumType.DoorState.Locked"
    }, {
      "key": "BSH.Common.Status.RemoteControlActive",
      "value": true
    }, {
      "key": "BSH.Common.Status.RemoteControlStartAllowed",
      "value": false
    }, {
      "key": "BSH.Common.Status.LocalControlActive",
      "value": false
    }, {
      "key": "BSH.Common.Status.OperationState",
      "value": "BSH.Common.EnumType.OperationState.Run"
    }]
  }
}
2017.04.30 13:00:00 4: WM6YH890 request: https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH890-68A40E00xxxx/programs/active
2017.04.30 13:00:00 4: WM6YH890: no token refresh needed
2017.04.30 13:00:01 4: WM6YH890 response: {
  "data": {
    "key": "LaundryCare.Washer.Program.Cotton.CottonEco",
    "options": [{
      "key": "LaundryCare.Washer.Option.Temperature",
      "value": "LaundryCare.Washer.EnumType.Temperature.GC60"
    }, {
      "key": "LaundryCare.Washer.Option.SpinSpeed",
      "value": "LaundryCare.Washer.EnumType.SpinSpeed.RPM1600"
    }, {
      "key": "LaundryCare.Washer.Option.WaterPlus",
      "value": false
    }, {
      "key": "LaundryCare.Washer.Option.IDos1DosingLevel",
      "value": "LaundryCare.Washer.EnumType.IDosingLevel.Normal"
    }, {
      "key": "LaundryCare.Washer.Option.IDos2DosingLevel",
      "value": "LaundryCare.Washer.EnumType.IDosingLevel.Normal"
    }, {
      "key": "LaundryCare.Washer.Option.RinsePlus",
      "value": "LaundryCare.Washer.EnumType.RinsePlus.Off"
    }, {
      "key": "LaundryCare.Washer.Option.Stains",
      "value": "LaundryCare.Washer.EnumType.Stains.Off"
    }, {
      "key": "LaundryCare.Washer.Option.Prewash",
      "value": false
    }, {
      "key": "LaundryCare.Washer.Option.LessIroning",
      "value": false
    }, {
      "key": "LaundryCare.Common.Option.VarioPerfect",
      "value": "LaundryCare.Common.EnumType.VarioPerfect.EcoPerfect"
    }, {
      "key": "BSH.Common.Option.RemainingProgramTimeIsEstimated",
      "value": true
    }, {
      "key": "BSH.Common.Option.RemainingProgramTime",
      "value": 16080,
      "unit": "seconds"
    }, {
      "key": "BSH.Common.Option.ProgramProgress",
      "value": 2,
      "unit": "%"
    }, {
      "key": "LaundryCare.Washer.Option.ProcessPhase",
      "value": "LaundryCare.Washer.EnumType.ProcessPhase.LoadAdjustActive"
    }, {
      "key": "BSH.Common.Option.EnergyForecast",
      "value": 60,
      "unit": "%"
    }, {
      "key": "BSH.Common.Option.WaterForecast",
      "value": 40,
      "unit": "%"
    }]
  }
}
2017.04.30 13:00:01 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:01 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:11 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:01 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:14 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:01 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:24 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:24 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:24 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:24 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:24 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:24 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:24 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:24 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:24 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:34 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:34 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 5: WM6YH890 found data: {"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}

2017.04.30 13:00:34 4: BSH.Common.Option.RemainingProgramTime = 16020 seconds
2017.04.30 13:00:34 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 5: WM6YH890 found data: {"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}

2017.04.30 13:00:34 4: BSH.Common.Option.RemainingProgramTime = 16020 seconds
2017.04.30 13:00:34 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 5: WM6YH890 found data: {"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}

2017.04.30 13:00:34 4: BSH.Common.Option.RemainingProgramTime = 16020 seconds
2017.04.30 13:00:34 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 5: WM6YH890 found data: {"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}

2017.04.30 13:00:34 4: BSH.Common.Option.RemainingProgramTime = 16020 seconds
2017.04.30 13:00:34 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:00:34 5: WM6YH890 found data: {"items":[{"timestamp":1493550022,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":16020,"level":"hint"}]}

2017.04.30 13:00:34 4: BSH.Common.Option.RemainingProgramTime = 16020 seconds
2017.04.30 13:00:44 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:44 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:54 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:54 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:00:54 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:00:54 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:00:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:01:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:14 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:01:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 115
Connection: close
Retry-After: 600
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "Too many parallel monitoring connections. Maximum is 10"
  }
}
2017.04.30 13:01:24 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:01:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:01:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}

2017.04.30 13:01:35 4: BSH.Common.Option.ProgramProgress = 3 %
2017.04.30 13:01:35 4: BSH.Common.Option.RemainingProgramTime = 15960 seconds
2017.04.30 13:01:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}

2017.04.30 13:01:35 4: BSH.Common.Option.ProgramProgress = 3 %
2017.04.30 13:01:35 4: BSH.Common.Option.RemainingProgramTime = 15960 seconds
2017.04.30 13:01:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}

2017.04.30 13:01:35 4: BSH.Common.Option.ProgramProgress = 3 %
2017.04.30 13:01:35 4: BSH.Common.Option.RemainingProgramTime = 15960 seconds
2017.04.30 13:01:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}

2017.04.30 13:01:35 4: BSH.Common.Option.ProgramProgress = 3 %
2017.04.30 13:01:35 4: BSH.Common.Option.RemainingProgramTime = 15960 seconds
2017.04.30 13:01:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:01:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":3,"level":"hint"},{"timestamp":1493550084,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15960,"level":"hint"}]}

2017.04.30 13:01:35 4: BSH.Common.Option.ProgramProgress = 3 %
2017.04.30 13:01:35 4: BSH.Common.Option.RemainingProgramTime = 15960 seconds
2017.04.30 13:01:44 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 569
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 569 seconds."
  }
}
2017.04.30 13:01:45 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:01:54 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:55 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:01:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:01:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:01:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:02:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:14 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 580
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 580 seconds."
  }
}
2017.04.30 13:02:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:02:24 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:02:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:16 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:02:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}

2017.04.30 13:02:35 4: BSH.Common.Option.RemainingProgramTime = 15900 seconds
2017.04.30 13:02:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}

2017.04.30 13:02:35 4: BSH.Common.Option.RemainingProgramTime = 15900 seconds
2017.04.30 13:02:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}

2017.04.30 13:02:35 4: BSH.Common.Option.RemainingProgramTime = 15900 seconds
2017.04.30 13:02:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}

2017.04.30 13:02:35 4: BSH.Common.Option.RemainingProgramTime = 15900 seconds
2017.04.30 13:02:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:02:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550146,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15900,"level":"hint"}]}

2017.04.30 13:02:35 4: BSH.Common.Option.RemainingProgramTime = 15900 seconds
2017.04.30 13:02:45 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 580
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 580 seconds."
  }
}
2017.04.30 13:02:45 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:02:55 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:55 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:02:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:02:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:02:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:03:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 580
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 580 seconds."
  }
}
2017.04.30 13:03:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:03:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:03:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:03:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}

2017.04.30 13:03:35 4: BSH.Common.Option.ProgramProgress = 4 %
2017.04.30 13:03:35 4: BSH.Common.Option.RemainingProgramTime = 15840 seconds
2017.04.30 13:03:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}

2017.04.30 13:03:35 4: BSH.Common.Option.ProgramProgress = 4 %
2017.04.30 13:03:35 4: BSH.Common.Option.RemainingProgramTime = 15840 seconds
2017.04.30 13:03:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}

2017.04.30 13:03:35 4: BSH.Common.Option.ProgramProgress = 4 %
2017.04.30 13:03:35 4: BSH.Common.Option.RemainingProgramTime = 15840 seconds
2017.04.30 13:03:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}

2017.04.30 13:03:35 4: BSH.Common.Option.ProgramProgress = 4 %
2017.04.30 13:03:35 4: BSH.Common.Option.RemainingProgramTime = 15840 seconds
2017.04.30 13:03:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:03:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.ProgramProgress","unit":"%","value":4,"level":"hint"},{"timestamp":1493550208,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15840,"level":"hint"}]}

2017.04.30 13:03:35 4: BSH.Common.Option.ProgramProgress = 4 %
2017.04.30 13:03:35 4: BSH.Common.Option.RemainingProgramTime = 15840 seconds
2017.04.30 13:03:45 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 569
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 569 seconds."
  }
}
2017.04.30 13:03:45 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:35 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:03:55 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:55 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:03:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:03:55 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:03:45 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:04:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:05 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:04:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 580
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 580 seconds."
  }
}
2017.04.30 13:04:15 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:04:05 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 599
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 599 seconds."
  }
}
2017.04.30 13:04:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:25 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:04:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:04:25 5: WM6YH890 received HTTP/1.1 429 Too Many Requests
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 11:04:15 GMT
Content-Type: application/vnd.bsh.sdk.v1+json
Content-Length: 196
Connection: close
Retry-After: 589
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept

{
  "error": {
    "key": "429",
    "description": "The rate limit \"10 successive error calls in 10 minutes\" was reached. Requests are blocked during the remaining period of 589 seconds."
  }
}
2017.04.30 13:04:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:25 5: WM6YH890 received event:KEEP-ALIVE
data:
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:35 2: WM6YH890 found nothing to read, channel closed
2017.04.30 13:04:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}

2017.04.30 13:04:35 4: BSH.Common.Option.RemainingProgramTime = 15780 seconds
2017.04.30 13:04:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}

2017.04.30 13:04:35 4: BSH.Common.Option.RemainingProgramTime = 15780 seconds
2017.04.30 13:04:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}

2017.04.30 13:04:35 4: BSH.Common.Option.RemainingProgramTime = 15780 seconds
2017.04.30 13:04:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}

2017.04.30 13:04:35 4: BSH.Common.Option.RemainingProgramTime = 15780 seconds
2017.04.30 13:04:35 5: WM6YH890 received event:NOTIFY
data:{"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
id:SIEMENS-WM6YH890-68A40E00xxxx


2017.04.30 13:04:35 5: WM6YH890 found data: {"items":[{"timestamp":1493550271,"handling":"none","key":"BSH.Common.Option.RemainingProgramTime","unit":"seconds","value":15780,"level":"hint"}]}
- fhem mit RasPi3 (debian-jessie) - HomeMatic (CCU2 - HMLAN-Adapter) und diverse HM Komponenten - 6 G-Tags (Anwesenheitserkennung) - SolVisMax Remotecontrol
- CUL 433 (Eigenbau - Arduino Nano C1101) - Alexa

Andy77H

#249
Hallo!

Danke nochmal für die Freischaltung. Konnten meinen Backofen verbinden, allerdings bekomme ich keine Daten, nur beim Init, die sind aber auch falsch...:

2017.04.30 19:49:12 2: set command: init
2017.04.30 19:49:12 4: HS658GXS6 request: https://api.home-connect.com/api/homeappliances
2017.04.30 19:49:12 4: HS658GXS6: no token refresh needed
2017.04.30 19:49:12 4: HS658GXS6 response: {
  "data": {
    "homeappliances": [{
      "name": "Backofen",
      "brand": "SIEMENS",
      "vib": "HS658GXS6",
      "connected": true,
      "type": "Oven",
      "enumber": "HS658GXS6/25",
      "haId": "SIEMENS-HS658GXS6-[...]"
    }]
  }
}
2017.04.30 19:49:12 2: HS658GXS6 defined as HomeConnect Oven SIEMENS HS658GXS6
2017.04.30 19:49:12 4: HS658GXS6 request: https://api.home-connect.com/api/homeappliances/SIEMENS-HS658GXS6-[...]/programs/available
2017.04.30 19:49:12 4: HS658GXS6: no token refresh needed
2017.04.30 19:49:13 4: HS658GXS6 response: {
  "data": {
    "programs": [{
      "key": "Cooking.Oven.Program.HeatingMode.HotAir"
    }, {
      "key": "Cooking.Oven.Program.HeatingMode.TopBottomHeating"
    }, {
      "key": "Cooking.Oven.Program.HeatingMode.PizzaSetting"
    }]
  }
}
2017.04.30 19:49:13 4: HS658GXS6 request: https://api.home-connect.com/api/homeappliances/SIEMENS-HS658GXS6-[...]/status
2017.04.30 19:49:13 4: HS658GXS6: no token refresh needed
2017.04.30 19:49:13 4: HS658GXS6 response: {
  "data": {
    "status": [{
      "key": "BSH.Common.Status.DoorState",
      "value": "BSH.Common.EnumType.DoorState.Open"
    }, {
      "key": "BSH.Common.Status.LocalControlActive",
      "value": false
    }, {
      "key": "BSH.Common.Status.RemoteControlStartAllowed",
      "value": false
    }, {
      "key": "BSH.Common.Status.RemoteControlActive",
      "value": false
    }, {
      "key": "BSH.Common.Status.OperationState",
      "value": "BSH.Common.EnumType.OperationState.Inactive"
    }, {
      "key": "Cooking.Oven.Status.CurrentCavityTemperature",
      "value": 0,
      "unit": "°C"
    }]
  }
}
2017.04.30 19:49:23 5: HS658GXS6 received HTTP/1.1 200 OK
Server: nginx/1.10.1
Date: Sun, 30 Apr 2017 17:49:14 GMT
Content-Type: text/event-stream
Connection: close
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS,PUT,DELETE
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept




Egal, was ich mache, also Tür auf/zu, Programm starten, etc. - ändert sich nichts... bekomme im Log, trotz "verbose 5", nur immer:

2017.04.30 19:52:04 5: HS658GXS6 received event:KEEP-ALIVE
data:
id:SIEMENS-HS658GXS6-[...]



(den hintern Teil der ID habe ich jeweils duch [...] ersetzt, keine Ahnung, ob das notwendig wäre... ;)

Ciao,

Andy

Skjall

Hallo zusammen,

nachdem ich mein RPi durch ein NUC, das Homematic Funkmodul durch eine CCU2 ersetzt und damit alle Geräte neu definieren musste (Also eigentlich vieles von Anfang) habe ich es endlich mal geschafft den freundlicherweise zur Verfügung gestellten Live-Zugang zu nutzen.

Zunächst einmal: Vielen dank für den Einsatz und das tolle Modul. Alles was ich hier schreibe ist keine Kritik sondern dient der Dokumentation.  ;D

Zu meinem Setup: Ich habe 4 HomeConnect-Fähige Geräte. Waschmaschine, Spülmaschine, Backofen und Kaffeevollautomat.

Mit dem Connector hatte ich zunächst Probleme, da der csrfToken des FHEMWEB immer reingegrätscht hat. (Ja, ich habe das auf der letzten Seite nicht gelesen  ;))  Den habe ich dort auf none gesetzt, sodass das redirecting auch läuft. Ich sehe das auch als unkritisch an. Bei mir bewegt sich alles im LAN ohne Public Services. IoT-Geräte die ich nicht unter Kontrolle habe sind in einer eignen Zone wo nur erlaubt ist, was explizit freigegeben ist.

Ich teste mit den echten Systemen erst ab heute. Insofern sind das erstmal nur eindrücke. Bei Fragen, fragen! ;) Logs stelle ich gerne bereit

Ich liste mal auf, was mir aufgefallen ist.

Ofen: HS658GXS6/05 Dampfbackofen.

- Es braucht manchmal einige Zeit bis die Readings des Backofens im FHEM landen. Beim Ändern oder stoppen des Programms las er weiter Readings obwohl das Programm schon einige zeit (1-2 Minuten) beendet war. Die Original-App erkannte das auch korrekt. Nur die API ist verzögert.

- Der state bei manchen funktionen wird nicht richtig interpretiert. Liegt vermutlich daran, dass es ein Dampfbackofen ist.
- Das Reading Cooking.Oven.Status.CurrentCavityTemperature aktualisiert nicht.

- Dampfgarprogramme
-- Programm "Regenerieren"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.SteamModes.Reheat
-- state: Program eheat active (5 %)

-- Programm "Dämpfen"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.SteamModes.Steam
-- state: Program team active (0 %)

-- Programm "Auftauen"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.SteamModes.Defrosting
-- state: Program efrosting active (1 %)

-- Programm "Teil gehen lassen"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.SteamModes.DoughProving
-- state: Program oughProving active (1 %)

- Reinigungsprogramme:
-- Programm "Trocknungsfunktion"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.Cleaning.Drying
-- state: Program ing active (6 %)

-- Programm "Reinigungsfunktion" (ecoClean)
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.Cleaning.Ecolysis
-- state: Program lysis active (1 %)

-- Programm "Entkalken"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.Cleaning.Descale
-- state: Program cale active (1 %)

-- Programm "Ablaufintegriertes spülen" (nach dem entkalten automatisch)
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.Cleaning.Flushing
-- state: Program shing active (0 %)

- Gerichte:
-- Programm "Tiefgefrorenes" -> "Pizza, 1 Stück, dünner Boden"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.Dish.Recommendation.Konv.PizzaMitDuennemBoden1Stueck
-- state: Program ndation.Konv.PizzaMitDuennemBoden1Stueck active (1 %)

(usw. Wenn da exakte readings erforderlich sind, teste ich alle mal durch und poste es)

Kafeevollautomat EQ.9 Connect (TI909701HC/03)
- Ich bekomme reine Readings wenn für den ausgewählten Bohnenbehälter und ob die Tassenheizung oder die Bediensperre an ist.
- Auch eine Rückmeldung für den fehlenden Milchbehälter kommt nicht. Lustigerweise sagt mir die HC-App "Milchbehälter einsetzen" wenn ich am FHEM einen Latte machen will  ;D

Spülmaschine SX678X26TE/17:
- Theoretisch weiß Siemens, wie viele Tabs ich noch habe. ein Reading gibts aber nicht dafür.
- Ansonsten läuft es gut. Das Starten habe ich noch nicht getestet da ich nicht wusste welches Programm was ist.

Waschmaschine WM6YH790/03
- Mal sehen, wann ich testen kann. Meine Frau will gerade nicht bügeln, nur weil ich am FHEM teste.  ;D

VG Jan

swhome

Hallo Skjall

freut mich dass Du so viele Home Connect Geräte anbinden konntest!

Zitat von: Skjall am 07 Mai 2017, 14:31:37
- Es braucht manchmal einige Zeit bis die Readings des Backofens im FHEM landen. Beim Ändern oder stoppen des Programms las er weiter Readings obwohl das Programm schon einige zeit (1-2 Minuten) beendet war. Die Original-App erkannte das auch korrekt. Nur die API ist verzögert.

Den Effekt habe ich bei meinem Dampfgarer auch, ich vermute einen Fehler in der API

Zitat von: Skjall am 07 Mai 2017, 14:31:37
- Das Reading Cooking.Oven.Status.CurrentCavityTemperature aktualisiert nicht.

Das klappt bei mir und einigen anderen prima, es gibt aber auch Tester hier die keine Temperatur gemeldet bekommen. Ursache ist unklar.

Zitat von: Skjall am 07 Mai 2017, 14:31:37
- Der state bei manchen funktionen wird nicht richtig interpretiert. Liegt vermutlich daran, dass es ein Dampfbackofen ist.

- Dampfgarprogramme
-- Programm "Regenerieren"
-- BSH.Common.Root.ActiveProgram: Cooking.Oven.Program.SteamModes.Reheat
-- state: Program eheat active (5 %)
[...]

Ich habe mir einen wohl zu komplizierten Mechanismus ausgedacht um den Programmnamen zu verkürzen. Ich stelle das um und verwende fortan nur noch das letzte Wort. Ideal wäre es wohl, die Programmliste pro Gerät zu speichern und für jedes einen eindeutigen kurzen Namen zu ermitteln, aber dafür bräuchte ich in Perl bestimmt nen ganzen Tag...

Zitat von: Skjall am 07 Mai 2017, 14:31:37
Kafeevollautomat EQ.9 Connect (TI909701HC/03)
- Ich bekomme reine Readings wenn für den ausgewählten Bohnenbehälter und ob die Tassenheizung oder die Bediensperre an ist.
- Auch eine Rückmeldung für den fehlenden Milchbehälter kommt nicht. Lustigerweise sagt mir die HC-App "Milchbehälter einsetzen" wenn ich am FHEM einen Latte machen will  ;D

Spülmaschine SX678X26TE/17:
- Theoretisch weiß Siemens, wie viele Tabs ich noch habe. ein Reading gibts aber nicht dafür.
- Ansonsten läuft es gut. Das Starten habe ich noch nicht getestet da ich nicht wusste welches Programm was ist.

Diese Readings sind auch im API nicht dokumentiert

Danke fürs Testen & viele Grüße
Stefan
Im Einsatz: FHEM auf Raspberry Pi mit 350 devices, hauptsächlich Homematic Wired und HM-Heizungsregler, dazu diverse Eigenbauten für Fussbodenheizung und LED Beleuchtung. Und jetzt mit Alexa!

Skjall

Moin,

eine klitzekleine bitte hätte ich noch.  ;D
Könntest du ein Reading "state" in das HomeConnectConnection-Device einbauen?
Dann geht auch das devStatIcon richtig. (zumindest geht es bei mir nur mit dem Internal STATE nicht)

LG Jan

Skjall

#253
Hmm.. Sehr interessant. Offensichtlich hat Siemens für meine Waschmaschine (noch) keine API-Unterstützung:

2017.05.13 14:15:24 2: 21308.Washer.1 can't get https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH790-XXXXXXXXXXXX/programs/available -- https://api.home-connect.com/api/homeappliances/SIEMENS-WM6YH790-XXXXXXXXXXXX/programs/available: Select timeout/error:

(Die Xe sind von mir)

Edit: Wenn ich dieses Device drin habe stürzt seit neuestem auch mein FHEM mit der Meldung ab:

Type of argument to keys on reference must be unblessed hashref or arrayref at ./FHEM/48_HomeConnect.pm line 78.

LG Jan

Andy77H

Hi!

Wollte nur Bescheid sagen, dass jetzt alles, bis auf CavitiyTemperature funktioniert/updated, nachdem ich FHEM mal neu gestartet habe...

Ciao,

Andy