Module für pilight (Senden und Empfangen)

Begonnen von Risiko, 03 März 2015, 20:33:54

Vorheriges Thema - Nächstes Thema

danieljo

Also ich habe gestern wie gewünscht die "Verbose" auf 5 gestellt.

Vllt. sollte ich erwähnen das meine Wetterstation die Daten niemals gleichzeitig senden. Es werden zu unterschiedlichen Zeiten 3 daten Blöcke gesendet:

"id" "temperature" "humidity" "battery"
"id" "windavg" "battery"
"id" "winddir" "wingust" "battery"


Events (Filter:.*):
2015-09-02 21:39:33 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"temperature":14.2,"humidity":85.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015-09-02 21:40:04 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015-09-02 21:40:34 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015-09-02 21:40:35 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015-09-02 21:41:06 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015-09-02 21:41:37 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015-09-02 21:42:38 pilight_ctrl myctrl rcv_raw: {"message":{"id":236,"temperature":14.2,"humidity":85.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1




Kann es sein das dein Modul alle Werte auf einmal erwartet?

Risiko

Zitat von: danieljo am 02 September 2015, 21:45:29
Vllt. sollte ich erwähnen das meine Wetterstation die Daten niemals gleichzeitig senden. Es werden zu unterschiedlichen Zeiten 3 daten Blöcke gesendet:

"id" "temperature" "humidity" "battery"
"id" "windavg" "battery"
"id" "winddir" "wingust" "battery"
Ah. Gut zu wissen. Das muss ich nochmal prüfen bzw. berücksichtigen.

Benötige aber die Logausschriften und nicht die Events aus dem Eventmonitor!!

Risiko

danieljo

Die Logeinträge reiche ich dir heute Abend nach

Mfg, Daniel Joachims

danieljo

Hier die einträge aus der Log-File:

2015.09.01 21:42:12 5: Triggering myctrl (1 changes)
2015.09.01 21:42:12 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:42:13 5: Triggering myctrl (1 changes)
2015.09.01 21:42:13 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:42:43 5: Triggering myctrl (1 changes)
2015.09.01 21:42:43 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:42:43 5: Triggering myctrl (1 changes)
2015.09.01 21:42:43 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:42:43 5: Triggering myctrl (1 changes)
2015.09.01 21:42:43 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":3}
2015.09.01 21:42:44 5: Triggering myctrl (1 changes)
2015.09.01 21:42:44 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":4}
2015.09.01 21:43:14 5: Triggering myctrl (1 changes)
2015.09.01 21:43:14 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:43:45 5: Triggering myctrl (1 changes)
2015.09.01 21:43:45 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:43:46 5: Triggering myctrl (1 changes)
2015.09.01 21:43:46 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:44:16 5: Triggering myctrl (1 changes)
2015.09.01 21:44:16 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"temperature":15.6,"humidity":89.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:44:16 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.6,89,1
2015.09.01 21:44:47 5: Triggering myctrl (1 changes)
2015.09.01 21:44:47 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:44:48 5: Triggering myctrl (1 changes)
2015.09.01 21:44:48 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:45:19 5: Triggering myctrl (1 changes)
2015.09.01 21:45:19 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:45:49 5: Triggering myctrl (1 changes)
2015.09.01 21:45:49 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:45:49 5: Triggering myctrl (1 changes)
2015.09.01 21:45:49 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:46:21 5: Triggering myctrl (1 changes)
2015.09.01 21:46:21 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:46:51 5: Triggering myctrl (1 changes)
2015.09.01 21:46:51 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"windavg":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:46:52 5: Triggering myctrl (1 changes)
2015.09.01 21:46:52 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":2}
2015.09.01 21:47:22 5: Triggering myctrl (1 changes)
2015.09.01 21:47:22 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"temperature":15.6,"humidity":89.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:47:22 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.6,89,1
2015.09.01 21:47:53 5: Triggering myctrl (1 changes)
2015.09.01 21:47:53 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}
2015.09.01 21:47:54 5: Triggering myctrl (1 changes)
2015.09.01 21:47:54 5: Notify loop for myctrl rcv_raw: {"message":{"id":236,"winddir":315,"windgust":0.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-b8-27-eb-f7c908","repeats":1}

Risiko

Hallo Daniel,

habe sie Sache heut (hoffentlich) gefixt. Ab morgen dann per Update verfügbar.

Risiko

danieljo

Wunderbar. Ich bedanke mich schonmal vorab bei dir und werde es morgen testen und dir Rückmeldung geben.

MFG, Daniel Joachims

danieljo

Also irgendwie funktioniert das noch nicht.

Ich bekomme zwar in den Readings battery;humidity,state,temperature richtiger weise angeizeigt, aber der Rest fehlt.

Risiko

Zitat von: danieljo am 07 September 2015, 18:56:31
Also irgendwie funktioniert das noch nicht.

Ich bekomme zwar in den Readings battery;humidity,state,temperature richtiger weise angeizeigt, aber der Rest fehlt.
Hmm. Stelle bitte verbose von pilight_ctrl auf 4 und überwache mal die Logs von pilight_temp_Parse: RCV -> PITEMP,alecto_wx500.....
Leider kann ich das ohne Hardware auch nicht simulieren.

Risiko.

danieljo

Das ist die ausgabe von pilight_ctrl verbose 4:

2015.09.07 20:20:16 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.5,82,1
2015.09.07 20:20:16 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.5,82,1
2015.09.07 20:20:17 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.5,82,1
2015.09.07 20:20:17 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.5,82,1
2015.09.07 20:23:22 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.4,82,1
2015.09.07 20:23:22 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.4,82,1
2015.09.07 20:23:23 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.4,82,1
2015.09.07 20:23:23 4: pilight_temp_Parse: RCV -> PITEMP,alecto_wx500,236,15.4,82,1

Risiko

Nabend

Sieht für mich nach ner alten Version aus. Was sagt version? - Befehl in der Befehlszeile eingeben
pilight_temp muss in Version 0.16 und pilight_ctrl in 1.11 vorliegen.

Risiko

danieljo

Also version sagt folgendes:

# $Id: 10_pilight_ctrl.pm 1.11 2015-09-06 Risiko $
# $Id: 30_pilight_temp.pm 0.16 2015-09-06 Risiko $

Ist somit also aktuell.

Risiko

Also die Logausschriften passen definitiv nicht zur Version!
Hast du FHEM nach dem Update nicht neu gestartet?

Risiko

danieljo

Na klar habe ich ein "shutdown restart" gemacht. Wenn du selber schauen möchtest kann ich dir per PN remote zugriff geben dann kannst du selber schauen ist wahrscheinlich effektiver oder?
Mfg, Daniel Joachims

danieljo

Okey anscheinend funktioniert es nun. Das einzige was geändert worden ist das ich den "featureLevel" in global gesetzt habe

MFG, Daniel Joachims

Tom71

#314
Hallo,
ich habe Probleme den pilight Service anzusprechen. Habe pilight auf localhost:5001 laufen:

curl http://127.0.0.1:5001/send?%7B%22action%22%3A%22identify%22%2C%22options%22%3A%7B%22receiver%22%3A1%7D%2C%22media%22%3A%22all%22%7D
{"message":"success"}


Wenn ich den Service aus FHEM anspechen möchte, kann sich FHEM nicht verbinden:

2015.09.14 10:55:04 5: pilight(DoInit): send {"action":"identify","options":{"receiver":1},"media":"all"}
2015.09.14 10:55:04 4: pilight(SimpleWrite): snd -> {"action":"identify","options":{"receiver":1},"media":"all"}
2015.09.14 10:55:04 5: SW: 7b22616374696f6e223a226964656e74696679222c226f7074696f6e73223a7b227265636569766572223a317d2c226d65646961223a22616c6c227d0a
2015.09.14 10:55:07 5: pilight(Check): opened
2015.09.14 10:55:07 4: pilight(Check): Could not connect to pilight-daemon localhost:5001 - maybe wrong api version or port
2015.09.14 10:55:07 1: localhost:5001 disconnected, waiting to reappear (pilight)


Eingebunden ist der Service:

Internals:
   API        6.0
   CFGFN
   DEF        localhost:5001
   DevIoJustClosed 1
   DeviceName localhost:5001
   NAME       pilight
   NR         110
   NTFY_ORDER 50-pilight
   PARTIAL
   RETRY_INTERVAL 60
   STATE      disconnected
   TYPE       pilight_ctrl
   Readings:
     2015-09-14 10:56:21   state           disconnected
   Helper:
     CHECK      0
     CON        disconnected
     NEXT_TRY   1442221041.48406
     sendQueue:
     whiteList:
Attributes:
   verbose    5


Könnte es etwas mit der Url-Codierung sein?

Version der module ist:
$Id: 10_pilight_ctrl.pm 1.12 2015-09-11 Risiko $


Gelöst: Es war wie bei einigen Beiträgen vorher der Port.

"port": 5000,
"webserver-port": 5001,


Nach hinzufügen vom port parameter in der pilight config geht es.
Homematic | RaspberryMatic