Module für pilight (Senden und Empfangen)

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

Vorheriges Thema - Nächstes Thema
Drucken
Nach unten Seiten 1 ... 28 29 30 31 32 ... 61
Benutzer-Aktionen

Esjay

#435
01 Februar 2016, 15:35:37
 Hi alle zusammen,

Ich bin gerade dabei mein Fhem einzurichten, und habe da ein kleines Problem. und zwar will sich Fhem nicht mit pilight verbinden.

Ich bin folgender Maßen vorgegangen.
In die Befehlszeile oben habe ich
Code Auswählen
define WZ pilight_ctrl 192.168.178.37:5000 eingegeben.
Dann habe ich mit
Code Auswählen
define Switch pilight_switch kaku_switch  19864566 0 nen "Schalter" erugt

Anschließend hab ich in der pilight config.json den Port 5000 geändert
Siehe hier
Code Auswählen
"settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-http-port": 5000,
                "webserver-cache": 1
        },
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
        "registry": {
                "pilight": {
                        "version": {
                                "current": "7.0"
                        }
                }
        }
}


Wenn ich dann in der Fhem einen reset durchführe, geht der Status von disconnected auf opened. Anschließend wieder auf disconnected.

Hier der log
Code Auswählen
2016.02.01 11:19:23 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:19:23 3: WZ device opened
2016.02.01 11:19:23 1: Including ./log/fhem.save
2016.02.01 11:19:23 1: usb create starting
2016.02.01 11:19:25 3: Probing CUL device /dev/ttyAMA0
2016.02.01 11:19:25 3: Probing TCM_ESP3 device /dev/ttyAMA0
2016.02.01 11:19:26 3: Probing FRM device /dev/ttyAMA0
2016.02.01 11:19:31 1: usb create end
2016.02.01 11:19:31 2: SecurityCheck:  WEB,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2016.02.01 11:19:31 0: Featurelevel: 5.7
2016.02.01 11:19:31 0: Server started with 11 defined entities (version $Id: fhem.pl 9893 2015-11-15 08:43:05Z rudolfkoenig $, os linux, user fhem, pid 2016)
2016.02.01 11:19:42 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:20:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:20:46 3: WZ device opened
2016.02.01 11:20:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:22:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:22:01 3: WZ device opened
2016.02.01 11:22:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:23:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:23:16 3: WZ device opened
2016.02.01 11:23:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:24:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:24:31 3: WZ device opened
2016.02.01 11:24:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:25:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:25:46 3: WZ device opened
2016.02.01 11:25:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:27:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:27:01 3: WZ device opened
2016.02.01 11:27:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:28:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:28:16 3: WZ device opened
2016.02.01 11:28:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:29:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:29:31 3: WZ device opened
2016.02.01 11:29:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:30:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:30:46 3: WZ device opened
2016.02.01 11:30:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:32:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:32:01 3: WZ device opened
2016.02.01 11:32:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:33:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:33:16 3: WZ device opened
2016.02.01 11:33:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:34:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:34:31 3: WZ device opened
2016.02.01 11:34:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:35:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:35:46 3: WZ device opened
2016.02.01 11:35:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:37:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:37:01 3: WZ device opened
2016.02.01 11:37:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:38:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:38:16 3: WZ device opened
2016.02.01 11:38:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:39:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:39:31 3: WZ device opened
2016.02.01 11:39:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:40:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:40:46 3: WZ device opened
2016.02.01 11:40:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:42:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:42:01 3: WZ device opened
2016.02.01 11:42:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:43:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:43:16 3: WZ device opened
2016.02.01 11:43:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:44:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:44:31 3: WZ device opened
2016.02.01 11:44:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:45:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:45:46 3: WZ device opened
2016.02.01 11:45:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:47:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:47:01 3: WZ device opened
2016.02.01 11:47:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:48:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:48:16 3: WZ device opened
2016.02.01 11:48:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:49:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:49:31 3: WZ device opened
2016.02.01 11:49:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:50:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:50:46 3: WZ device opened
2016.02.01 11:50:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:52:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:52:01 3: WZ device opened
2016.02.01 11:52:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:53:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:53:16 3: WZ device opened
2016.02.01 11:53:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:54:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:54:31 3: WZ device opened
2016.02.01 11:54:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:55:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:55:46 3: WZ device opened
2016.02.01 11:55:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:57:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:57:01 3: WZ device opened
2016.02.01 11:57:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:58:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:58:16 3: WZ device opened
2016.02.01 11:58:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 11:59:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 11:59:31 3: WZ device opened
2016.02.01 11:59:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:00:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:00:46 3: WZ device opened
2016.02.01 12:00:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:02:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:02:01 3: WZ device opened
2016.02.01 12:02:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:03:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:03:16 3: WZ device opened
2016.02.01 12:03:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:04:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:04:31 3: WZ device opened
2016.02.01 12:04:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:05:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:05:46 3: WZ device opened
2016.02.01 12:05:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:07:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:07:01 3: WZ device opened
2016.02.01 12:07:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:08:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:08:16 3: WZ device opened
2016.02.01 12:08:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:09:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:09:31 3: WZ device opened
2016.02.01 12:09:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:10:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:10:46 3: WZ device opened
2016.02.01 12:10:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:12:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:12:01 3: WZ device opened
2016.02.01 12:12:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:13:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:13:16 3: WZ device opened
2016.02.01 12:13:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:14:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:14:31 3: WZ device opened
2016.02.01 12:14:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:15:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:15:46 3: WZ device opened
2016.02.01 12:15:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:17:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:17:01 3: WZ device opened
2016.02.01 12:17:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:18:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:18:16 3: WZ device opened
2016.02.01 12:18:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:19:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:19:31 3: WZ device opened
2016.02.01 12:19:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:20:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:20:46 3: WZ device opened
2016.02.01 12:20:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:22:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:22:01 3: WZ device opened
2016.02.01 12:22:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:23:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:23:16 3: WZ device opened
2016.02.01 12:23:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:24:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:24:31 3: WZ device opened
2016.02.01 12:24:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:25:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:25:46 3: WZ device opened
2016.02.01 12:25:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:27:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:27:01 3: WZ device opened
2016.02.01 12:27:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:28:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:28:16 3: WZ device opened
2016.02.01 12:28:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:29:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:29:31 3: WZ device opened
2016.02.01 12:29:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:30:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:30:46 3: WZ device opened
2016.02.01 12:30:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:32:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:32:01 3: WZ device opened
2016.02.01 12:32:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:33:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:33:16 3: WZ device opened
2016.02.01 12:33:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:34:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:34:31 3: WZ device opened
2016.02.01 12:34:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:35:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:35:46 3: WZ device opened
2016.02.01 12:35:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:37:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:37:01 3: WZ device opened
2016.02.01 12:37:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:38:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:38:16 3: WZ device opened
2016.02.01 12:38:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:39:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:39:31 3: WZ device opened
2016.02.01 12:39:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:40:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:40:46 3: WZ device opened
2016.02.01 12:40:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:42:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:42:01 3: WZ device opened
2016.02.01 12:42:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:43:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:43:16 3: WZ device opened
2016.02.01 12:43:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:44:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:44:31 3: WZ device opened
2016.02.01 12:44:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:45:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:45:46 3: WZ device opened
2016.02.01 12:45:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:47:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:47:01 3: WZ device opened
2016.02.01 12:47:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:48:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:48:16 3: WZ device opened
2016.02.01 12:48:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:49:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:49:31 3: WZ device opened
2016.02.01 12:49:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:50:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:50:46 3: WZ device opened
2016.02.01 12:50:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:52:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:52:01 3: WZ device opened
2016.02.01 12:52:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:53:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:53:16 3: WZ device opened
2016.02.01 12:53:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:54:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:54:31 3: WZ device opened
2016.02.01 12:54:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:55:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:55:46 3: WZ device opened
2016.02.01 12:55:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:57:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:57:01 3: WZ device opened
2016.02.01 12:57:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:58:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:58:16 3: WZ device opened
2016.02.01 12:58:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 12:59:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 12:59:31 3: WZ device opened
2016.02.01 12:59:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:00:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:00:46 3: WZ device opened
2016.02.01 13:00:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:02:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:02:01 3: WZ device opened
2016.02.01 13:02:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:03:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:03:16 3: WZ device opened
2016.02.01 13:03:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:04:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:04:31 3: WZ device opened
2016.02.01 13:04:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:05:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:05:46 3: WZ device opened
2016.02.01 13:05:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:07:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:07:01 3: WZ device opened
2016.02.01 13:07:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:08:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:08:16 3: WZ device opened
2016.02.01 13:08:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:09:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:09:31 3: WZ device opened
2016.02.01 13:09:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:10:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:10:46 3: WZ device opened
2016.02.01 13:10:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:12:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:12:01 3: WZ device opened
2016.02.01 13:12:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:13:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:13:16 3: WZ device opened
2016.02.01 13:13:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:14:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:14:31 3: WZ device opened
2016.02.01 13:14:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:15:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:15:46 3: WZ device opened
2016.02.01 13:15:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:17:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:17:01 3: WZ device opened
2016.02.01 13:17:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:18:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:18:16 3: WZ device opened
2016.02.01 13:18:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:19:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:19:31 3: WZ device opened
2016.02.01 13:19:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:20:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:20:46 3: WZ device opened
2016.02.01 13:20:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:22:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:22:01 3: WZ device opened
2016.02.01 13:22:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:23:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:23:16 3: WZ device opened
2016.02.01 13:23:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:24:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:24:31 3: WZ device opened
2016.02.01 13:24:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:25:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:25:46 3: WZ device opened
2016.02.01 13:25:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:27:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:27:01 3: WZ device opened
2016.02.01 13:27:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:28:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:28:16 3: WZ device opened
2016.02.01 13:28:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:29:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:29:31 3: WZ device opened
2016.02.01 13:29:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:30:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:30:46 3: WZ device opened
2016.02.01 13:30:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:32:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:32:01 3: WZ device opened
2016.02.01 13:32:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:33:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:33:16 3: WZ device opened
2016.02.01 13:33:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:34:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:34:31 3: WZ device opened
2016.02.01 13:34:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:35:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:35:46 3: WZ device opened
2016.02.01 13:35:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:37:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:37:01 3: WZ device opened
2016.02.01 13:37:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:38:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:38:16 3: WZ device opened
2016.02.01 13:38:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:39:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:39:31 3: WZ device opened
2016.02.01 13:39:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:40:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:40:46 3: WZ device opened
2016.02.01 13:40:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:42:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:42:01 3: WZ device opened
2016.02.01 13:42:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:43:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:43:16 3: WZ device opened
2016.02.01 13:43:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:44:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:44:31 3: WZ device opened
2016.02.01 13:44:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:45:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:45:46 3: WZ device opened
2016.02.01 13:45:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:47:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:47:01 3: WZ device opened
2016.02.01 13:47:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:48:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:48:16 3: WZ device opened
2016.02.01 13:48:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:49:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:49:31 3: WZ device opened
2016.02.01 13:49:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:50:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:50:46 3: WZ device opened
2016.02.01 13:50:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:52:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:52:01 3: WZ device opened
2016.02.01 13:52:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:53:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:53:16 3: WZ device opened
2016.02.01 13:53:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:54:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:54:31 3: WZ device opened
2016.02.01 13:54:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:55:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:55:46 3: WZ device opened
2016.02.01 13:55:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:57:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:57:01 3: WZ device opened
2016.02.01 13:57:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:58:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:58:16 3: WZ device opened
2016.02.01 13:58:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 13:59:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 13:59:31 3: WZ device opened
2016.02.01 13:59:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:00:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:00:46 3: WZ device opened
2016.02.01 14:00:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:02:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:02:01 3: WZ device opened
2016.02.01 14:02:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:03:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:03:16 3: WZ device opened
2016.02.01 14:03:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:04:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:04:31 3: WZ device opened
2016.02.01 14:04:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:05:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:05:46 3: WZ device opened
2016.02.01 14:05:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:07:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:07:01 3: WZ device opened
2016.02.01 14:07:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:08:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:08:16 3: WZ device opened
2016.02.01 14:08:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:09:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:09:31 3: WZ device opened
2016.02.01 14:09:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:10:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:10:46 3: WZ device opened
2016.02.01 14:10:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:12:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:12:01 3: WZ device opened
2016.02.01 14:12:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:13:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:13:16 3: WZ device opened
2016.02.01 14:13:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:14:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:14:31 3: WZ device opened
2016.02.01 14:14:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:15:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:15:46 3: WZ device opened
2016.02.01 14:15:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:17:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:17:01 3: WZ device opened
2016.02.01 14:17:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:18:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:18:16 3: WZ device opened
2016.02.01 14:18:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:19:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:19:31 3: WZ device opened
2016.02.01 14:19:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:20:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:20:46 3: WZ device opened
2016.02.01 14:20:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:22:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:22:01 3: WZ device opened
2016.02.01 14:22:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:23:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:23:16 3: WZ device opened
2016.02.01 14:23:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:24:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:24:31 3: WZ device opened
2016.02.01 14:24:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:25:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:25:46 3: WZ device opened
2016.02.01 14:25:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:27:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:27:01 3: WZ device opened
2016.02.01 14:27:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:28:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:28:16 3: WZ device opened
2016.02.01 14:28:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:29:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:29:31 3: WZ device opened
2016.02.01 14:29:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:30:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:30:46 3: WZ device opened
2016.02.01 14:30:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:32:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:32:01 3: WZ device opened
2016.02.01 14:32:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:33:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:33:16 3: WZ device opened
2016.02.01 14:33:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:34:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:34:31 3: WZ device opened
2016.02.01 14:34:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:35:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:35:46 3: WZ device opened
2016.02.01 14:35:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:37:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:37:01 3: WZ device opened
2016.02.01 14:37:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:38:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:38:16 3: WZ device opened
2016.02.01 14:38:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:39:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:39:31 3: WZ device opened
2016.02.01 14:39:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:40:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:40:46 3: WZ device opened
2016.02.01 14:40:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:42:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:42:01 3: WZ device opened
2016.02.01 14:42:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:43:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:43:16 3: WZ device opened
2016.02.01 14:43:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:44:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:44:31 3: WZ device opened
2016.02.01 14:44:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:45:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:45:46 3: WZ device opened
2016.02.01 14:45:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:47:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:47:01 3: WZ device opened
2016.02.01 14:47:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:48:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:48:16 3: WZ device opened
2016.02.01 14:48:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:49:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:49:31 3: WZ device opened
2016.02.01 14:49:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:50:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:50:46 3: WZ device opened
2016.02.01 14:50:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:52:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:52:01 3: WZ device opened
2016.02.01 14:52:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:53:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:53:16 3: WZ device opened
2016.02.01 14:53:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:54:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:54:31 3: WZ device opened
2016.02.01 14:54:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:55:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:55:46 3: WZ device opened
2016.02.01 14:55:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:57:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:57:01 3: WZ device opened
2016.02.01 14:57:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:58:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:58:16 3: WZ device opened
2016.02.01 14:58:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 14:59:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 14:59:31 3: WZ device opened
2016.02.01 14:59:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:00:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:00:46 3: WZ device opened
2016.02.01 15:00:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:02:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:02:01 3: WZ device opened
2016.02.01 15:02:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:03:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:03:16 3: WZ device opened
2016.02.01 15:03:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:04:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:04:31 3: WZ device opened
2016.02.01 15:04:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:05:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:05:46 3: WZ device opened
2016.02.01 15:05:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:07:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:07:01 3: WZ device opened
2016.02.01 15:07:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:08:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:08:16 3: WZ device opened
2016.02.01 15:08:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:09:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:09:31 3: WZ device opened
2016.02.01 15:09:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:10:20 2: WZ(Write): ERROR: no connection to pilight-daemon 192.168.178.37:5000
2016.02.01 15:10:22 2: WZ(Write): ERROR: no connection to pilight-daemon 192.168.178.37:5000
2016.02.01 15:10:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:10:46 3: WZ device opened
2016.02.01 15:10:56 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:10:57 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5000
2016.02.01 15:11:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:11:46 3: Can't connect to 192.168.178.37:5000: Connection refused
2016.02.01 15:11:47 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5000
2016.02.01 15:12:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:12:46 3: Can't connect to 192.168.178.37:5000: Connection refused
2016.02.01 15:12:47 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5000
2016.02.01 15:13:22 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:13:22 3: Can't connect to 192.168.178.37:5000: Connection refused
2016.02.01 15:13:23 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5000
2016.02.01 15:13:28 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:13:28 3: Can't connect to 192.168.178.37:5000: Connection refused
2016.02.01 15:13:29 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5000
2016.02.01 15:13:38 3: Opening WZ device 192.168.178.37:5001
2016.02.01 15:13:38 3: Can't connect to 192.168.178.37:5001: Connection refused
2016.02.01 15:13:39 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5001
2016.02.01 15:13:43 3: Opening WZ device 192.168.178.37:5001
2016.02.01 15:13:43 3: Can't connect to 192.168.178.37:5001: Connection refused
2016.02.01 15:13:44 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:5001
2016.02.01 15:14:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:14:31 3: WZ device opened
2016.02.01 15:14:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:14:48 2: WZ(Write): ERROR: no connection to pilight-daemon 192.168.178.37:5000
2016.02.01 15:14:50 2: WZ(Write): ERROR: no connection to pilight-daemon 192.168.178.37:5000
2016.02.01 15:15:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:15:46 3: WZ device opened
2016.02.01 15:15:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:17:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:17:01 3: WZ device opened
2016.02.01 15:17:13 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:18:16 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:18:16 3: WZ device opened
2016.02.01 15:18:28 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:19:31 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:19:31 3: WZ device opened
2016.02.01 15:19:43 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:20:46 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:20:46 3: WZ device opened
2016.02.01 15:20:58 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)
2016.02.01 15:22:01 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:22:01 3: WZ device opened
2016.02.01 15:22:14 3: Opening WZ device 192.168.178.37:80
2016.02.01 15:22:14 3: Can't connect to 192.168.178.37:80: Connection refused
2016.02.01 15:22:15 2: WZ(Check): Could not connect to pilight-daemon 192.168.178.37:80
2016.02.01 15:23:18 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:23:18 3: WZ device opened
2016.02.01 15:23:29 3: Opening WZ device 192.168.178.37:5000
2016.02.01 15:23:29 3: WZ device opened
2016.02.01 15:23:41 1: 192.168.178.37:5000 disconnected, waiting to reappear (WZ)

Dann hab ich folgendes gefunden

ZitatRisiko:
@update71
Es kann keine Verbindung zu pilight aufgebaut werden!!
Verwechselst du nicht webserver-port für die WebGui und den pilight Port für die Kommunikation!!??


--- Code: ---settings": {
"port": 5000,
"webserver-port": 5001,
}

--- Ende Code ---

Risiko.

Also habe ich die config.json um die Zeile "port" 5000, erweitert.

Anschließend konnte ich pilight nicht mehr starten.

Ich dreh mich ab jetzt im Kreis, und vermute das ich ohne Hilfe nicht mehr raus komme.

MfG

sash.sc

#436
01 Februar 2016, 16:42:26
Port 5000 ist schon richtig.  Dein http Port muss dann raus gelöscht werden

Gesendet von meinem C6603 mit Tapatalk

Raspi 4B+ Bullseye ;LaCrosse; HomeMatic; MapleCUL; ZigBee; Signalduino ESP32 ; Shellys; MQTT2; Grafana mit Influxdb

Risiko

#437
01 Februar 2016, 18:06:32
Du kannst natürlich nicht beide Ports mit der gleichen Portnummer versehen.
Also entweder so wie es sash.sc sagt den http Port raus oder eine andere Nummer vergeben.

Bernd

#438
06 Februar 2016, 13:30:07
Hallo zusammen,

an sich funktioniert alles super - vielen Dank für die Module und die vielen Posts dazu - aber dennoch habe ich ein kleinen Problem.

Ich hatte bis dato meine Funksteckdosen via IT-Modul und CUL (868MHz) gesteuert. Das klappt auch meistens. Nun wollte ich auf 433MHz umstellen und habe mir ein TX- und RX-Modul besorgt, mit meinem BananaPi verbunden, ein paar Module installiert und in der Config-Datei einfach die Zeilen mit der IT-Definition durch die pilght-switch-Definition getauscht. Pilight-ctlr wurde natürlich auch definiert.

Mit pilight-receive habe ich geprüft, was denn als Protokoll gesendet wurde ("sc2262"). Leider hat das mit pilight_switch nicht geklappt. Durch etwas stöbern im Forum bin ich dann auf das Protokoll "elro_800_switch" gekommen. Damit, und mit den im pilight-receive angezeigten System- und Unit-Codes habe ich dann die Definitionen der jeweiligen Schalter angelegt:

Code Auswählen

define C1 pilight_switch elro_800_switch 29 15
define C3 pilight_switch elro_800_switch 29 14

Das hat auch bei einem Teil der Steckdosen zum sofortigen Erfolg geführt - nur nicht bei allen - und das ist nun mein Problem:

Intertechno ITR-1500 (die Weissen, selbstlernenden) Funksteckdosen lassen sich nur ausschalten, aber nicht einschalten. Die erste Zeile mit "State : off", zeigt den Log-Eintrag  für das Ausschalten, die zweite mit "State : on" das Anschalten. Off geht, On leider nicht.

Code Auswählen

2016-02-06_12:53:05 MyPilight rcv_raw: {"origin":"sender","protocol":"elro_800_switch","message":{"systemcode":29,"unitcode":14,"state":"off"},"repeat":1,"uuid":"0000-02-13-09-00eb18"}
2016-02-06_12:53:07 MyPilight rcv_raw: {"origin":"sender","protocol":"elro_800_switch","message":{"systemcode":29,"unitcode":14,"state":"on"},"repeat":1,"uuid":"0000-02-13-09-00eb18"}


Ich habe kein Attribut "brands" in pilight-ctrl definiert. Aber auch mit diversen Versuche mit "brands" habe ich es nicht hinbekommen.

Die System- und Unit-Codes funktionieren mit IT problemlos auch mit den ITR-1500 Dosen.

Ich hatte mit

Code Auswählen

define C3 pilight_switch kaku_switch 4466531 0

zwar Erfolg beim Einschalten, nur muss ich dann die ganzen IDs ermitteln / neu anlernen. Ich hoffe, es gibt einen Weg die alten IT-Codes verwenden zu können.

Hat jemand einen Tipp dazu?

Vielen Dank und Gruß

Bernd[/code]
FHEM auf BananaPi

Risiko

#439
06 Februar 2016, 13:59:08
Hallo Bernd,

ich kann in den Logs keinen Fehler in den FHEM-Modulen sehen.
Ich finde deine Beschreibung aber sehr seltsam:

1. Das Protokoll sc2262 scheint es offiziell zu geben - oder ich übersehe etwas: https://wiki.pilight.org/doku.php/protocols#switches
2. Protokoll elro_800_switch und kaku_switch sind nicht verwand. Wieso soll es denn bei dem einen gehen und bei dem anderen nicht.

Meiner Meinung nach ist für die selbstlernenden Intertechno das Protokoll kaku_switch das Richtige.
Für nicht selbstlernenden IT das Protokoll  kaku_switch_old.

Wenn du auch einen Empfänger angeschlossen hast, kannst doch einfach die ID's mit pilight-receive ohne neu zu lernen ermitteln.

Risiko

Bernd

#440
06 Februar 2016, 14:59:05 Letzte Bearbeitung: 06 Februar 2016, 15:02:34 von Bernd
Hallo Risiko,

danke für die schnelle Reaktion.

Ich habe diese weissen ITR-1500 alle mit den IT-Codes aus FHEM angelernt. Device in FHEM definiert (define B1 IT F00000000F FF F0), Steckdose in die Wand und auf ON geklickt. Damit war die Dose zufrieden und funktionierte aus FHEM. Die Fernbedienungen ITT-1500 habe ich nie verwendet.
Wenn ich nun die Kommunikation zwischen FHEM-CUL und ITR-1500 ansehe, bekomme ich für ein ON das:
Code Auswählen

{
        "message": {
                "systemcode": 29,
                "unitcode": 14,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "sc2262",
        "uuid": "0000-02-13-09-00eb18",
        "repeats": 1
}
{
        "message": {
                "systemcode": 29,
                "unitcode": 14,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "sc2262",
        "uuid": "0000-02-13-09-00eb18",
        "repeats": 2
}

Ich hatte gehofft, diese Codes in Pilight verwenden zu können. Leider geht damit nur ein OFF.

Wenn ich nun mit der IT-Fernbedienung ITT-1500 eine Dose anlerne, bekomme ich das in pilight-receive:
Code Auswählen

{
        "message": {
                "id": 17806006,
                "unit": 2,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-02-13-09-00eb18",
        "repeats": 4
}
{
        "message": {
                "id": 17806006,
                "unit": 2,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-02-13-09-00eb18",
        "repeats": 4
}
{
        "message": {
                "id": 17806006,
                "unit": 2,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-02-13-09-00eb18",
        "repeats": 4
}

Damit kann ich dann zwar ein pilight-switch definieren (define C3 pilight_switch kaku_switch 4466531 0), aber dann muss ich diese 8-stelligen Codes alle erzeugen/ermitteln. Das wollte ich eigentlich vermeiden. Die Dose sind nicht alle so schön zugänglich.

Der Versuch. mit kaku_switch einen Code anzulernen hatte leider auch keinen Erfolg. Ein
Code Auswählen

pilight-send -p kaku_switch -i 12345678 -u 0 -t -l

war leider auch nicht erfolgreich. Die Dose hat es nicht akzeptiert.

Bernd
FHEM auf BananaPi

Bernd

#441
06 Februar 2016, 15:57:28 Letzte Bearbeitung: 06 Februar 2016, 16:08:20 von Bernd
Nachtrag zu ITR-1500: Sie funktionieren mit den alten IT-Codes und dem Pollin-Protokoll  :)
Code Auswählen

pilight: pilight-send -p pollin -s 29 -u 14 -f
oder
FHEM define C3 pilight_switch pollin 29 14


Nur der STATE ist jetzt immer auf "defined". (Nachtrag: STATE geht - reboot (shutdown restart) tut gut)

Bernd
FHEM auf BananaPi

Risiko

#442
06 Februar 2016, 16:50:50
Hallo Bernd,

es ist schön, dass es geht. Verstehen tue ich es aber nicht.
Pollin für IT - sehr seltsam.

Das Protokoll sc2262 ist laut Doku für eine Kontaktsensor.
arctech_switch ist ein anderer Name für Kaku_switch, intertechno_switch - Stichwort brands.
Mit
Code Auswählen
define pilight_switch kaku_switch 17806006 2 hätte es gehen müssen.

Naja, es geht ja jetzt.
Viel Spaß.

Bernd

#443
07 Februar 2016, 17:11:52
Hallo Risiko,
Code Auswählen

DEFINE C3 pilight_switch kaku_switch 17806006 2

hat funktioniert. Nur wollte ich nicht unnötigerweise die ganzen IDs ermitteln.

Mit dem POLLIN Protokoll läuft es jetzt super.

Vielen Dank nochmal für das Modul und den Support.

Gruß

Bernd
FHEM auf BananaPi

Oldsurfer

#444
10 Februar 2016, 19:28:14
Hallo zusammen
ich bin gerade dabei auf FHEM umzusteigen. Die Steuerung von Funksteckdosen funktioniert auch schon. Meine LED-Dimmer kann ich zwar schalten, aber leider über die Oberfläche nicht dimmen.
Kann mir da jemand einen Tip geben wie ich das Module pilight_dimmer konfigurieren muss?
Hier die entsprechenden Zeilen aus der Pilight-Konfiguration:
"dimmer1": {
         "protocol": [ "kaku_dimmer" ],
         "id": [{
            "id": 100,
            "unit": 0
         }],
         "state": "off",
         "dimlevel": 0
und entsprechend aus meiner jetzigen FHEM-Datei:
## Dimmer1 Wohnzimmer ##
define Gesamtwohnen pilight_dimmer kaku_dimmer 100 0 kaku_screen
attr Gesamtwohnen IODev pilight
attr Gesamtwohnen group EG
attr Gesamtwohnen room Wohnzimmer

Bin für jeden Tip dankbar. Danke

Oldsurfer

roelleke

#445
10 Februar 2016, 23:03:43
Hallo,
Das Kaku_Screenshots ist in jedem Fall zuviel.
Hier ist meine Definition als Beispiel:

define TeDachLicht pilight_dimmer kaku_dimmer 6266126 0
attr TeDachLicht userattr Erdgeschoss Erdgeschoss_map structexclude
attr TeDachLicht Erdgeschoss EGRaeume
attr TeDachLicht IODev PilightSrv1
attr TeDachLicht alias Dachbeleuchtung
attr TeDachLicht cmdIcon ein:Restart aus:Shutdown
attr TeDachLicht comment {if(ReadingsVal($name,"state","") eq 'off') {"off"} else {ReadingsVal($name,"dimlevel",0)}}
attr TeDachLicht devStateIcon 0:dim06% 1:dim12% 2:dim18% 3:dim25% 4:dim31% 5:dim37% 6:dim43% 7:dim50% 8:dim56% 9:dim62% 10:dim68% 11:dim75% 12:dim81% 13:dim87% 14:dim93% 15:dim100%
attr TeDachLicht eventMap on:ein off:aus
attr TeDachLicht fp_wohnzimmer 200,800,5,
attr TeDachLicht group Dach
attr TeDachLicht room Terrasse
attr TeDachLicht stateFormat {if(ReadingsVal($name,"state","") eq 'off') {"off"} else {ReadingsVal($name,"dimlevel",0)}}
attr TeDachLicht webCmd dimlevel:ein:aus

Vielleicht ist es hilfreich

Oldsurfer

#446
11 Februar 2016, 17:12:25
Super, das war genu was ich gesucht hatte.
Vielen Dank :-)

Risiko

#447
11 Februar 2016, 18:57:45
Hallo Oldsurfer
Das sollte auch mit der Zugabe des 2. Protokolls Screen gehen.
Zusätzlich hätte man hier eben noch die Funktion Up und Down.
Man muss dann natürlich das attr webcmd anpassen:
Code Auswählen

attr Gesamtwohnen webCmd on:off:up:down:dimlevel

Oldsurfer

#448
11 Februar 2016, 20:18:49
Hallo Risiko
die Lösung ist natürlich viel einfacher umzusetzen. Ich habe nur die up:down Anweisungen weggelassen. Den Level kann man auch gut mit dem Dimlevel einstellen.

Oldsurfer

Mellowback

#449
13 Februar 2016, 00:57:07
Wie installiere ich denn das Modul ?
Immer wenn ich mit pilight_temp arbeiten möchte, kennt er es nicht.
Drucken
Nach oben Seiten 1 ... 28 29 30 31 32 ... 61
Benutzer-Aktionen