Autor Thema: [AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support  (Gelesen 104875 mal)

Offline australien

  • Full Member
  • ***
  • Beiträge: 126
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1245 am: 02 September 2018, 22:00:54 »
Kaputt?

Ich habe es auf zweit Tablets versucht. Amazon und ein noname Tablet.


BTW. Wenn ich den Tasker tnes installiere, kann mit eine komme Sache Weiterleitung auf einen teuren locate Service? Nicht gewollt, oder?
« Letzte Änderung: 02 September 2018, 22:04:06 von australien »
raspberry pi3
signalduino (mit nanoCUL) auf Somfy Frequenz | NeumanHat 3x 886 1x 433
Amazon Fire Tablet 7 | Noname Android Tablet 10"

Online CoolTux

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16631
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1246 am: 02 September 2018, 22:05:37 »
Ich habe es auf zweit Tablets versucht. Amazon und ein noname Tablet.

Dann bin ich auch ratlos. Sorry.

Es sei denn Dir fallen noch Infos ein die Dir und mir helfen könnten das Problem genauer zu analysieren.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.me/MOldenburg
Mein GitHub: https://github.com/LeonGaultier
kein Support für cfg Editierer

Offline TomLee

  • Sr. Member
  • ****
  • Beiträge: 926
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1247 am: 16 September 2018, 20:42:21 »
Auf was muss ich beim Wechsel vom alten Amad auf Amadng achten. Muss zugeben hab länger schon nicht mitgelesen, lief alles.
Müssen alle alten Devices gelöscht werden ?

Was ich bisher versucht habe:
Parallel zu den alten Devices ein AMADCommBridge-Device angelegt, den Flow installiert und dem Assistenten gefolgt. Es wurde aber kein neues AmadDevice angelegt.
Dann hab ich das alte Device welches neu als AmadDevice angelegt werden sollte gelöscht. Den Assistenten wieder aktiviert der mittlerweile wieder von selbst deaktiviert war. Und nochmals versucht. Auch dann kein neues AmadDevice.
Dann hab ich ein update gemacht und Fhem neu starten wollen, was dann nach einem restart nicht mehr erreichbar war.
Also wieder Backup von gestern abend eingespielt und alles läuft wieder.

Müssen alle alten Devices zuvor gelöscht werden ?


Online CoolTux

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16631
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1248 am: 16 September 2018, 20:46:28 »
Auf was muss ich beim Wechsel vom alten Amad auf Amadng achten. Muss zugeben hab länger schon nicht mitgelesen, lief alles.
Müssen alle alten Devices gelöscht werden ?

Was ich bisher versucht habe:
Parallel zu den alten Devices ein AMADCommBridge-Device angelegt, den Flow installiert und dem Assistenten gefolgt. Es wurde aber kein neues AmadDevice angelegt.
Dann hab ich das alte Device welches neu als AmadDevice angelegt werden sollte gelöscht. Den Assistenten wieder aktiviert der mittlerweile wieder von selbst deaktiviert war. Und nochmals versucht. Auch dann kein neues AmadDevice.
Dann hab ich ein update gemacht und Fhem neu starten wollen, was dann nach einem restart nicht mehr erreichbar war.
Also wieder Backup von gestern abend eingespielt und alles läuft wieder.

Müssen alle alten Devices zuvor gelöscht werden ?

Hallo Thomas,

Du musst alle alten Devices lösche und sofern dann noch vorhanden die CommBridge auch. Danach legst Du die CommBridge vom Type AMADCommBridge neu an und folgst der Anleitung.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.me/MOldenburg
Mein GitHub: https://github.com/LeonGaultier
kein Support für cfg Editierer

Offline TomLee

  • Sr. Member
  • ****
  • Beiträge: 926
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1249 am: 16 September 2018, 22:33:29 »
Auch nachdem ich jetzt zuvor alle alten Devices gelöscht habe und dem Assistenten wieder gefolgt bin kein neues AmadDevice.
Mir war zuvor auch schon aufgefallen: Ist es korrekt das im Flowset AMADNG Info/Control Flowset v4.2.3 nur zwei Flows sind ? First Run Assistant und NFC Tag Support ? Da stimmt doch was nicht ? Die alten deaktiviere/lösche ich doch ?
Die Bridge ist jetzt auch nur opened davor (bei meinem ersten Versuch) mein ich war sie initialized.

Internals:
BRIDGE 1
FD 51
NAME AMADBridge
NR 494
PORT 8090
STATE opened
TYPE AMADCommBridge
VERSIONFLOWSET 4.2.3
VERSIONMODUL 4.2.2
READINGS:
2018-09-16 22:58:01 fhemServerIP 192.168.188.26
2018-09-16 22:04:19 state opened
Attributes:
fhemControlMode setControl
room AMAD

Werd mal ein manuelles anlegen versuchen, die AMAD_ID kann eine beliebige sechstellige Zahl sein ?
« Letzte Änderung: 16 September 2018, 23:03:30 von TomLee »

Online CoolTux

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16631
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1250 am: 16 September 2018, 23:00:46 »
Die ID kann irgendeine Zahl sein, muss aber einmal sein.
Hast Du autocreate aktiv?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.me/MOldenburg
Mein GitHub: https://github.com/LeonGaultier
kein Support für cfg Editierer

Offline TomLee

  • Sr. Member
  • ****
  • Beiträge: 926
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1251 am: 16 September 2018, 23:12:07 »
Ja, autocreate ist an.

Internals:
AMAD_ID 179336
CFGFN
DEF 192.168.188.30
179336 Automagic
HOST 192.168.188.30
IODev AMADBridge
NAME SamsungTablet
NOTIFYDEV global,SamsungTablet
NR 2067
NTFY_ORDER 50-SamsungTablet
PORT 8090
STATE initialized
TYPE AMADDevice
VERSIONFLOWSET 4.2.3
VERSIONMODUL 4.2.5
READINGS:
2018-09-16 22:54:50 deviceState unknown
2018-09-16 22:58:35 lastStatusRequestState
statusRequest_error 2018-09-16 22:54:50
state initialized
helper:
deviceStateErrorCounter 0
infoErrorCounter 1
setCmdErrorCounter 0
Attributes:
IODev AMADBridge
remoteServer Automagic
room AMAD

Ist das korrekt das nur die zwei Flows im Set sind ?

Offline TomLee

  • Sr. Member
  • ****
  • Beiträge: 926
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1252 am: 16 September 2018, 23:18:08 »
2018.09.16 23:16:06 5: AMADDevice (SamsungTablet) - IOWrite: 192.168.188.30:8090 GET IODevHash=HASH(0x6236068)
2018.09.16 23:16:06 5: AMADCommBridge (SamsungTablet) - statusRequestERROR: 192.168.188.30: Verbindungsaufbau abgelehnt
2018.09.16 23:16:06 5: AMADCommBridge (SamsungTablet) - statusRequestERROR: AMADCommBridge_statusRequestErrorHandling: error while requesting AutomagicInfo: 192.168.188.30: Verbindungsaufbau abgelehnt
« Letzte Änderung: 16 September 2018, 23:20:30 von TomLee »

Offline TomLee

  • Sr. Member
  • ****
  • Beiträge: 926
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1253 am: 16 September 2018, 23:48:09 »
Nachdem ich die alten Flows alle gelöscht habe und die neuen importiert, wird jetzt auch automatisch ein Device angelegt und die Readings kommen rein. Müssen wohl in einer Gruppe sein ? Trotzdem Danke.

Online CoolTux

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16631
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1254 am: 17 September 2018, 04:54:10 »
Guten Morgen,

Die alten Floss müssen immer alle gelöscht werden, sonst werden die neuen mit selben Namen nicht importiert. Das sagt Dir aber auch Automagic beim Abschluss des Imports.

Grüße
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.me/MOldenburg
Mein GitHub: https://github.com/LeonGaultier
kein Support für cfg Editierer

Offline bennebartsch

  • Jr. Member
  • **
  • Beiträge: 67
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1255 am: 28 Oktober 2018, 14:09:47 »
Guten Tag, erstmal danke für das Modul!
Bei mir klappt soweit alles, allerdings ist der Slider von set volumeNotification in der setList wohl mit 0-7 angegeben, mein Galaxy S9 hat aber 0-15. Man kann trotzdem noch per set andere Werte setzten, aber es wäre schön wenn der Schönheitsfehler behoben wird :-)

Online CoolTux

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16631
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1256 am: 28 Oktober 2018, 14:37:55 »
Attribut setNotifyVolMax auf 15 setzen.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.me/MOldenburg
Mein GitHub: https://github.com/LeonGaultier
kein Support für cfg Editierer

Offline bennebartsch

  • Jr. Member
  • **
  • Beiträge: 67
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1257 am: 28 Oktober 2018, 17:48:08 »
Attribut setNotifyVolMax auf 15 setzen.

Das habe ich wohl übersehen, vielen Dank!
Gefällt mir Gefällt mir x 1 Liste anzeigen

Offline NewRasPi

  • Full Member
  • ***
  • Beiträge: 102
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1258 am: 04 November 2018, 23:29:42 »
Hallo Fhem Forum, hallo CoolTux,
ich würde jetzt auch gerne AMADNG auf mein neues ACER Tab 10.1 A3-A50 mit Android 7.0 einrichten.
Bisher geschafft habe ich die App Automatic auf dieses Tablet zu installieren und die Flow Datei wie in der Anleitung importiert.
Auf dem FHEM Raspberry Pi3 habe ich mit
  define WohnzimmerTablet AMAD 10.63.173.49 <SSID-FRITZBOX> das AMAD Device angelegt. Automatisch kam dann das AMADCommBridge dazu. Diesem habe ich mit dem set Befehl die IP des FHEM Servers 10.63.173.5
zugewiesen.
Das Tablet und den Raspberry neu gestartet und gehoft das es geht. Leider sieht es anders aus.
Die List Daten sind:
Internals:
   APSSID     Fritz7490_nomap
   DEF        10.63.173.49 Fritz7490_nomap
   HOST       10.63.173.49
   NAME       TabletWohnzimmer
   NR         252
   PORT       8090
   STATE      initialized
   TYPE       AMAD
   VERSIONFLOWSET 2.6.12
   VERSIONMODUL 2.6.13
   READINGS:
     2018-11-04 23:20:47   deviceState     offline
     2018-11-04 22:49:21   lastStatusRequestState statusRequest_error
     2018-11-04 22:47:16   state           initialized
   helper:
     deviceStateErrorCounter 17
     infoErrorCounter 0
     setCmdErrorCounter 0
Attributes:
   room       AMAD
   verbose    5
Von der AMADCommBridge:
Internals:
   BRIDGE     1
   CONNECTS   291
   FD         50
   NAME       AMADCommBridge
   NR         253
   PORT       8090
   STATE      opened
   TYPE       AMAD
   VERSIONFLOWSET 2.6.12
   VERSIONMODUL 2.6.13
   READINGS:
     2018-11-04 22:00:09   expertMode      1
     2018-11-04 19:53:57   fhemServerIP    10.63.173.5
     2018-11-04 22:47:16   state           opened
     2018-11-04 23:24:18   transmitterERROR AMADCommBridge_10.63.173.49_58938 has no device name sends
Attributes:
   room       AMAD
   verbose    5
Die Daten aus dem Event Monitor (andere Device ausgeschnitten)
2018.11.04 22:47:35 4 : Connection accepted from AMADCommBridge_10.63.173.49_36497

2018.11.04 22:47:35 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 133 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","checkActiveTask": "0"}}
2018-11-04 22:47:35 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_36497 has no device name sends

2018.11.04 22:47:46 5 : AMAD (TabletWohnzimmer) - Send statusRequest with URL: "http://10.63.173.49:8090/fhem-amad/deviceInfo/" and Header: "fhemIP: 10.63.173.5 fhemDevice: TabletWohnzimmer activeTask: none apSSID: Fritz7490_nomap"
2018.11.04 22:47:46 4 : AMAD (TabletWohnzimmer) - AMAD_checkDeviceState: run Check
2018.11.04 22:47:46 4 : AMAD (TabletWohnzimmer) - AMAD_checkDeviceState: set new Timer
2018.11.04 22:47:51 5 : AMAD (TabletWohnzimmer) - statusRequestERROR: connect to your device is timed out. check network
2018-11-04 22:47:51 AMAD TabletWohnzimmer lastStatusRequestState: statusRequest_error
2018.11.04 22:47:51 5 : AMAD (TabletWohnzimmer) - statusRequestERROR: AMAD_statusRequestErrorHandling: error while requesting AutomagicInfo: connect to http://10.63.173.49:8090 timed out

2018.11.04 22:48:22 4 : Connection accepted from AMADCommBridge_10.63.173.49_58619
2018.11.04 22:48:23 4 : Connection accepted from AMADCommBridge_10.63.173.49_58620
2018.11.04 22:48:23 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 133 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","checkActiveTask": "0"}}
2018-11-04 22:48:23 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58620 has no device name sends

2018.11.04 22:49:16 4 : AMAD (TabletWohnzimmer) - AMAD_checkDeviceState: run Check
2018.11.04 22:49:16 5 : AMAD (TabletWohnzimmer) - Send statusRequest with URL: "http://10.63.173.49:8090/fhem-amad/deviceInfo/" and Header: "fhemIP: 10.63.173.5 fhemDevice: TabletWohnzimmer activeTask: none apSSID: Fritz7490_nomap"
2018.11.04 22:49:16 4 : AMAD (TabletWohnzimmer) - AMAD_checkDeviceState: set new Timer
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58651
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58652
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58653
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58654
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58655
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58656
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58657
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58658
2018.11.04 22:49:17 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 139 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","flow_informations": "aktiv"}}
2018-11-04 22:49:17 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58658 has no device name sends
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58659
2018.11.04 22:49:17 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 181 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","nextAlarmState": "null","airplanemode": "off","deviceState": "online"}}
2018-11-04 22:49:17 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58659 has no device name sends
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58661
2018.11.04 22:49:17 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 335 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","dockingState": "undocked","deviceState": "online"}}
2018-11-04 22:49:17 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58661 has no device name sends
2018.11.04 22:49:17 4 : Connection accepted from AMADCommBridge_10.63.173.49_58662
2018.11.04 22:49:17 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 399 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","deviceState": "online"}}
2018-11-04 22:49:17 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58662 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58663
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58664
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58665
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58666
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58667
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58668
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58669
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58670
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58671
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58672
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58673
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58673 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58674
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58674 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58675
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58675 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58676
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58676 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58677
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58677 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58678
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 443 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58678 has no device name sends
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58679
2018.11.04 22:49:19 4 : Connection accepted from AMADCommBridge_10.63.173.49_58680
2018.11.04 22:49:19 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 508 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","screenOrientation": "landscape","screenOrientationMode": "auto","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:19 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58680 has no device name sends
2018-11-04 22:49:20 OWDevice DS2405_4AEC29CDBAAB sensed: 1
2018.11.04 22:49:20 4 : Connection accepted from AMADCommBridge_10.63.173.49_58681
2018.11.04 22:49:20 4 : Connection accepted from AMADCommBridge_10.63.173.49_58682
2018.11.04 22:49:20 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 508 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","screenOrientation": "landscape","screenOrientationMode": "auto","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:20 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58681 has no device name sends
2018.11.04 22:49:20 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 508 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","screenOrientation": "landscape","screenOrientationMode": "auto","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:20 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58682 has no device name sends
2018.11.04 22:49:20 4 : Connection accepted from AMADCommBridge_10.63.173.49_58683
2018.11.04 22:49:20 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 734 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","airplanemode": "off","currentMusicTrack": "no player active","currentMusicAlbum": "no player active","currentMusicArtist": "no player active","currentMusicApp": "no player active","currentMusicIcon": "no player active","currentMusicState": "null","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","screenOrientation": "landscape","screenOrientationMode": "auto","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
2018-11-04 22:49:20 AMAD AMADCommBridge transmitterERROR: AMADCommBridge_10.63.173.49_58683 has no device name sends
2018.11.04 22:49:20 4 : Connection accepted from AMADCommBridge_10.63.173.49_58684
2018.11.04 22:49:20 5 : AMAD (AMADCommBridge) - Receive RAW Message in Debugging Mode: POST / HTTP/1.1 Content-Type: application/json User-Agent: Mozilla/5.0 (compatible; Automagic) Connection: close Host: 10.63.173.5:8090 Accept-Encoding: gzip Content-Length: 758 {"amad": {"amad_id": "1541366738468","fhemcmd": "setreading"},"payload": { "flowsetVersionAtDevice": "4.2.4","doNotDisturb": "always","nextAlarmState": "null","screen": "on unlocked","airplanemode": "off","currentMusicTrack": "no player active","currentMusicAlbum": "no player active","currentMusicArtist": "no player active","currentMusicApp": "no player active","currentMusicIcon": "no player active","currentMusicState": "null","bluetooth": "off","connectedBTdevices": "none","connectedBTdevicesMAC": "none","nextAlarmTime": "null","nextAlarmDay": "null","screenOrientation": "landscape","screenOrientationMode": "auto","automagicState": "Automagic Premium Automagic Service läuft ","dockingState": "undocked","keyguardSet": "0","deviceState": "online"}}
FHEM Version:
74_AMAD.pm           14120 2017-04-27 16:22:21Z CoolTux
74_AMADDevice.pm     17639 2018-10-29 06:47:59Z CoolTux
Nun wär eigentlich meine erste Frage, ist das überhaupt das neuste AMADNG ?
und kann man aus diesen Angaben erkennen, was ich falsch mache?
Falls noch weitere Infos gebraucht werden sagt mir bitte bescheid.
Vielen Dank für die Hilfe.
Schöne Grüße
NewRasPi - Elmar
« Letzte Änderung: 05 November 2018, 00:19:54 von NewRasPi »
Raspberry Pi 2 Mod B + Raspberry Pi 3; HM Lan Adapter; 8 Kanal Relaiskarte; ca. 15x 1wire Temperatur Sensor DS18B20; 10x HC-SR501 Bewegungsmelder; 9x HM Rauchmelder HM-Sec-SD; HM Funk Fenstersensoren; HM Strommess-Zwischenstecker;

Offline OdfFhem

  • Full Member
  • ***
  • Beiträge: 111
Antw:[AMADNG] AMAD 4.2 The Next Generation of AMAD with Tasker Support
« Antwort #1259 am: 05 November 2018, 05:41:42 »
Hallo,

ich habe die aktuelle Version von AMAD im Einsatz und kein FHEM-Device vom Typ AMAD. Stattdessen 1x AMADCommBridge und je Tablet/Smartphone 1x AMADDevice.

Hilfreich bei der Einrichtung war der folgende Wiki-Eintrag
https://wiki.fhem.de/wiki/AMAD

Viele Grüße