Integration von MySensors in FHEM geplant?

Begonnen von fh555, 06 September 2014, 00:40:58

Vorheriges Thema - Nächstes Thema
Drucken
Nach unten Seiten 1 ... 3 4 5 6 7 ... 74
Benutzer-Aktionen

hexenmeister

#60
09 Oktober 2014, 07:47:04
Ich habe ds selbst zwar nicht ausprobiert, aber laut Hersteller-Seite soll das auch mit ENC28J60 gehen.

fh168

#61
09 Oktober 2014, 07:57:05
Hallo Hexenmeister,

der Platz reicht für den ENC28J60 zur Zeit nicht aus (Nano mit FTDI). Ich habe als Alternative den Uno mit Network-Shield genommen, klappt. (Siehe Fotos oben)

LG
/robin
Hue, Lacrosse, PCA301, MySensors, V 1.67 CUL 868 V3.4, Lacrosse-WLAN-Gateway, Tasmota RF-

hexenmeister

#62
09 Oktober 2014, 08:02:14
Oh, Du hast recht, das steht nur bei dem 'nicht MQTT'-Sketch dran:

ZitatEnable your Ethernet module as illustrated below:

#include <UIPEthernet.h>  // Use this if you have attached a Ethernet ENC28J60 shields 
//#include <Ethernet.h>   // Use this for WizNET module and Arduino Ethernet Shield

also geht nicht...

fh168

#63
09 Oktober 2014, 09:08:49
bekommt man das softwaremäßig hin, das alles auf einem Nano mit ENC28J60 draufpasst? Es fehlt nur knapp 1 kb.
Hue, Lacrosse, PCA301, MySensors, V 1.67 CUL 868 V3.4, Lacrosse-WLAN-Gateway, Tasmota RF-

ntruchsess

#64
09 Oktober 2014, 09:27:05
UDP abzuschalten indem man in der uipethernet-conf.h UIP_CONF_UDP auf 0 setzt spart ca. 5kb (dann braucht der Sketch eine feste IP und der mqtt-server mit ip-addresse statt hostnamen angegeben werden, weil dann DHCP und DNS nicht mehr geht.)

Beim RAM-bedarf kann man mit UIP_CONF_MAX_CONNECTIONS 1 einiges sparen. Der mqtt-client sollte nach meinem Verständnis mit 1 offenen Socketverbindung auskommen.

Gruß,

Norbert
while (!asleep()) {sheep++};

fh168

#65
09 Oktober 2014, 09:32:54
hallo,
werde ich ausprobieren. Der mySensors-gateway-MQTT-Sketch benötigt sowieso eine feste IP. Das würde ja passen.
Hue, Lacrosse, PCA301, MySensors, V 1.67 CUL 868 V3.4, Lacrosse-WLAN-Gateway, Tasmota RF-

fh555

#66
10 Oktober 2014, 23:30:27
und ein neues Problem seit den FHEM-Update (gestern und heute).

Ich hatte gestern u.a. die Updates MQTT, MQTT_Bridge, MQTT_Device per "fhem update" eingespielt und anschließend ein "shutdown restart" per "FHEM-Console" durchgeführt. Seitdem läuft der MQTT Gateway garnicht bzw. instabil.

Hat sich in den Definitionen der Geräte etwas geändert?

Momentan spreche ich mein Gateway wie folgt an:
Code Auswählen

define MQTT_MySensors MQTT 192.168.100.250:1883
set MQTT_MySensors connect


und die Geräte definiere ich
Code Auswählen

define mqtt_schalter1 MQTT_DEVICE
attr mqtt_schalter1 IODev MQTT_MySensors
attr mqtt_schalter1 alias Schalter 1
#attr mqtt_schalter1 stateFormat transmission-state
attr mqtt_schalter1 stateFormat state
attr mqtt_schalter1 subscribeReading_state MyMQTT/10/3/V_TRIPPED
attr mqtt_schalter1 room MQTT-Test


hat sich dahingehend etwas geändert?
Ich hatte testweise die alten Files wieder hergestellt um die Hardware auszuschließen und es funktionierte sofort wieder.

Heute hatte ich dann das "neuste Update" eingespielt und jetzt ist es so, dass entweder irgendwann ein Timeout kommt und er disconnected ist ein manueller connect funktioniert von ca. 10 Versuchen 1 mal. Ein Neustart vom Hardware-Gateway" bringt auch nichts. Ein FHEM "shutdown restart" oder das Ändern der fhem.cfg mit anschließenden abspeichern bringt manchmal die Geschichte wieder zum laufen.

Gibt es ein Diskussion-Thread wo sich die Entwickler für die Module austauschen, damit man ggf. solche Fehler gleich melden könnte?

Gruß Jens

fh168

#67
12 Oktober 2014, 16:34:40
Hallo,

ich habe über dieses Thema mal ein Blog-Beitrag geschrieben und ein kurzes youtube-video gedreht.

http://blog.moneybag.de/fhem-sensoren-an-fhem-mit-nrf24l01-transceiver/

LG
/robin

Hue, Lacrosse, PCA301, MySensors, V 1.67 CUL 868 V3.4, Lacrosse-WLAN-Gateway, Tasmota RF-

ntruchsess

#68
12 Oktober 2014, 21:25:19
Hallo Jens,

Zitat von: fh555 am 10 Oktober 2014, 23:30:27
und ein neues Problem seit den FHEM-Update (gestern und heute) ... Seitdem läuft der MQTT Gateway garnicht bzw. instabil.
Code Auswählen

define MQTT_MySensors MQTT 192.168.100.250:1883
set MQTT_MySensors connect

das 'set MQTT_MySensors connect' ist unnötig, das MQTT-modul connected selbständig. Das set connect-kommando ist mehr zum testen.

An der Semantik der define-kommandos hat sich nix geändert. Ich habe zwischenzeitlich nach mqtt-spec Quality-Of-Service implementiert, vieleicht ist da noch was fehlerhaft. Kannst Du bitte logs mit 'attr verbose 5' an allen beteiligten Devices (MQTT + MQTT_DEVICE) posten, in denen man Dein Problem nachvollziehen kann?

Gruß,

Norbert
while (!asleep()) {sheep++};

fh555

#69
13 Oktober 2014, 00:01:35 Letzte Bearbeitung: 13 Oktober 2014, 00:08:22 von fh555
Beide geräte wurden zum Start des Tests neu gestartet.

Erst der FHEM Server, danach der MQTT Gateway

Code Auswählen

2014.10.12 23:40:22 0: Server started with 47 defined entities (version $Id: fhem.pl 6730 2014-10-09 19:21:23Z rudolfkoenig $, os linux, user fhem, pid 3230)
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message received: ConnAck/at-most-once Connection Accepted
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 1 MyMQTT/71/0/V_LIGHT_LEVEL/at-most-once
2014.10.12 23:40:22 5: SW: 821e000100194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 2 MyMQTT/60/0/V_TEMP/at-most-once
2014.10.12 23:40:22 5: SW: 8217000200124d794d5154542f36302f302f565f54454d5000
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 3 MyMQTT/60/1/V_TEMP/at-most-once
2014.10.12 23:40:22 5: SW: 8217000300124d794d5154542f36302f312f565f54454d5000
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 4 MyMQTT/10/3/V_TRIPPED/at-most-once
2014.10.12 23:40:22 5: SW: 821a000400154d794d5154542f31302f332f565f5452495050454400
2014.10.12 23:40:22 5: SW: 8a1a000400154d794d5154542f31302f332f565f5452495050454400
2014.10.12 23:40:22 5: SW: 8a1e000100194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.12 23:40:22 5: SW: 8a17000300124d794d5154542f36302f312f565f54454d5000
2014.10.12 23:40:22 5: SW: 8a17000200124d794d5154542f36302f302f565f54454d5000
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 1/at-most-once
2014.10.12 23:40:22 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 2/at-most-once
2014.10.12 23:40:23 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 3/at-most-once
2014.10.12 23:41:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:41:14 5: SW: c000
2014.10.12 23:42:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:42:14 5: SW: c000
2014.10.12 23:43:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:43:14 5: SW: c000
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:44:14 5: SW: c000
2014.10.12 23:44:14 1: 192.168.100.250:1883 disconnected, waiting to reappear (MQTT_MySensors)
2014.10.12 23:44:14 1: 192.168.100.250:1883 reappeared (MQTT_MySensors)
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: Connect/at-most-once MQIsdp/3/Net::MQTT::Message[3230]
2014.10.12 23:44:14 5: SW: 102600064d51497364700302003c00184e65743a3a4d5154543a3a4d6573736167655b333233305d
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:44:14 5: SW: c000
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: ConnAck/at-most-once Connection Accepted
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 5 MyMQTT/71/0/V_LIGHT_LEVEL/at-most-once
2014.10.12 23:44:14 5: SW: 821e000500194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 6 MyMQTT/60/0/V_TEMP/at-most-once
2014.10.12 23:44:14 5: SW: 8217000600124d794d5154542f36302f302f565f54454d5000
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 7 MyMQTT/60/1/V_TEMP/at-most-once
2014.10.12 23:44:14 5: SW: 8217000700124d794d5154542f36302f312f565f54454d5000
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 8 MyMQTT/10/3/V_TRIPPED/at-most-once
2014.10.12 23:44:14 5: SW: 821a000800154d794d5154542f31302f332f565f5452495050454400
2014.10.12 23:44:14 5: SW: 8a1a000800154d794d5154542f31302f332f565f5452495050454400
2014.10.12 23:44:14 5: SW: 8a17000600124d794d5154542f36302f302f565f54454d5000
2014.10.12 23:44:14 5: SW: 8a1a000400154d794d5154542f31302f332f565f5452495050454400
2014.10.12 23:44:14 5: SW: 8a17000700124d794d5154542f36302f312f565f54454d5000
2014.10.12 23:44:14 5: SW: 8a1e000500194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 5/at-most-once
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 6/at-most-once
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 7/at-most-once
2014.10.12 23:44:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 4/at-most-once
2014.10.12 23:44:46 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 30                                      26.0
2014.10.12 23:44:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.0
2014.10.12 23:44:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.0
2014.10.12 23:44:46 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.0,1
2014.10.12 23:44:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.0
2014.10.12 23:45:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:45:14 5: SW: c000
2014.10.12 23:45:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:45:18 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 31                                      26.1
2014.10.12 23:45:18 5: publish received for MyMQTT/60/1/V_TEMP, 26.1
2014.10.12 23:45:18 5: publish received for MyMQTT/60/1/V_TEMP, 26.1
2014.10.12 23:45:18 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.1,1
2014.10.12 23:45:18 5: publish received for MyMQTT/60/1/V_TEMP, 26.1
2014.10.12 23:46:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:46:14 5: SW: c000
2014.10.12 23:46:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:46:23 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 32                                      26.2
2014.10.12 23:46:23 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:46:23 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.2,1
2014.10.12 23:46:23 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:46:23 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:46:55 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 31                                      26.1
2014.10.12 23:46:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.12 23:46:55 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.1,1
2014.10.12 23:46:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.12 23:46:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.12 23:47:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:47:14 5: SW: c000
2014.10.12 23:47:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:47:18 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
2014.10.12 23:47:18 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:18 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:18 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:18 5: calling readingsSingleUpdate(mqtt_schalter1,state,0,1
2014.10.12 23:47:18 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:47:24 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
  31                                               1
2014.10.12 23:47:24 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:24 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:24 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:24 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:47:24 5: calling readingsSingleUpdate(mqtt_schalter1,state,1,1
2014.10.12 23:47:45 2: IT set B_Dose_Fenster_LED off
2014.10.12 23:47:50 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
2014.10.12 23:47:50 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:50 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:50 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:47:50 5: calling readingsSingleUpdate(mqtt_schalter1,state,0,1
2014.10.12 23:47:50 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:47:51 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
  31                                               1
2014.10.12 23:47:51 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:51 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:51 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:47:51 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:47:51 5: calling readingsSingleUpdate(mqtt_schalter1,state,1,1
2014.10.12 23:48:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:48:14 5: SW: c000
2014.10.12 23:48:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:48:32 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 32                                      26.2
2014.10.12 23:48:32 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:48:32 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.2,1
2014.10.12 23:48:32 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:48:32 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:49:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:49:14 5: SW: c000
2014.10.12 23:49:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:50:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:50:14 5: SW: c000
2014.10.12 23:50:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:51:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:51:14 5: SW: c000
2014.10.12 23:51:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:52:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:52:14 5: SW: c000
2014.10.12 23:52:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:53:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:53:14 5: SW: c000
2014.10.12 23:53:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:53:55 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 33                                      26.3
2014.10.12 23:53:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:53:55 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.3,1
2014.10.12 23:53:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:53:55 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:54:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:54:14 5: SW: c000
2014.10.12 23:54:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:54:27 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 32                                      26.2
2014.10.12 23:54:27 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:54:27 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.2,1
2014.10.12 23:54:27 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:54:27 5: publish received for MyMQTT/60/0/V_TEMP, 26.2
2014.10.12 23:55:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:55:14 5: SW: c000
2014.10.12 23:55:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:56:04 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 33                                      26.3
2014.10.12 23:56:04 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:56:04 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.3,1
2014.10.12 23:56:04 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:56:04 5: publish received for MyMQTT/60/0/V_TEMP, 26.3
2014.10.12 23:56:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:56:14 5: SW: c000
2014.10.12 23:56:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:57:08 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  33 31 2e 31                                      31.1
2014.10.12 23:57:08 5: publish received for MyMQTT/60/0/V_TEMP, 31.1
2014.10.12 23:57:08 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,31.1,1
2014.10.12 23:57:08 5: publish received for MyMQTT/60/0/V_TEMP, 31.1
2014.10.12 23:57:08 5: publish received for MyMQTT/60/0/V_TEMP, 31.1
2014.10.12 23:57:09 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 33                                      26.3
2014.10.12 23:57:09 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:57:09 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:57:09 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.3,1
2014.10.12 23:57:09 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:57:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:57:14 5: SW: c000
2014.10.12 23:57:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:57:41 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 37 2e 38                                      27.8
2014.10.12 23:57:41 5: publish received for MyMQTT/60/0/V_TEMP, 27.8
2014.10.12 23:57:41 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,27.8,1
2014.10.12 23:57:41 5: publish received for MyMQTT/60/0/V_TEMP, 27.8
2014.10.12 23:57:41 5: publish received for MyMQTT/60/0/V_TEMP, 27.8
2014.10.12 23:57:41 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 37                                      26.7
2014.10.12 23:57:41 5: publish received for MyMQTT/60/1/V_TEMP, 26.7
2014.10.12 23:57:41 5: publish received for MyMQTT/60/1/V_TEMP, 26.7
2014.10.12 23:57:41 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.7,1
2014.10.12 23:57:41 5: publish received for MyMQTT/60/1/V_TEMP, 26.7
2014.10.12 23:58:13 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 37 2e 30                                      27.0
2014.10.12 23:58:13 5: publish received for MyMQTT/60/0/V_TEMP, 27.0
2014.10.12 23:58:13 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,27.0,1
2014.10.12 23:58:13 5: publish received for MyMQTT/60/0/V_TEMP, 27.0
2014.10.12 23:58:13 5: publish received for MyMQTT/60/0/V_TEMP, 27.0
2014.10.12 23:58:13 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 34                                      26.4
2014.10.12 23:58:13 5: publish received for MyMQTT/60/1/V_TEMP, 26.4
2014.10.12 23:58:13 5: publish received for MyMQTT/60/1/V_TEMP, 26.4
2014.10.12 23:58:13 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.4,1
2014.10.12 23:58:13 5: publish received for MyMQTT/60/1/V_TEMP, 26.4
2014.10.12 23:58:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.12 23:58:14 5: SW: c000
2014.10.12 23:58:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.12 23:58:45 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
2014.10.12 23:58:45 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:58:45 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:58:45 5: publish received for MyMQTT/10/3/V_TRIPPED, 0
2014.10.12 23:58:45 5: calling readingsSingleUpdate(mqtt_schalter1,state,0,1
2014.10.12 23:58:45 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:58:46 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/0/V_TEMP
  32 36 2e 38                                      26.8
2014.10.12 23:58:46 5: publish received for MyMQTT/60/0/V_TEMP, 26.8
2014.10.12 23:58:46 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.8,1
2014.10.12 23:58:46 5: publish received for MyMQTT/60/0/V_TEMP, 26.8
2014.10.12 23:58:46 5: publish received for MyMQTT/60/0/V_TEMP, 26.8
2014.10.12 23:58:46 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/60/1/V_TEMP
  32 36 2e 33                                      26.3
2014.10.12 23:58:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:58:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:58:46 5: calling readingsSingleUpdate(mqtt_Temperatur2,state,26.3,1
2014.10.12 23:58:46 5: publish received for MyMQTT/60/1/V_TEMP, 26.3
2014.10.12 23:58:53 5: MQTT MQTT_MySensors message received: Publish/at-most-once MyMQTT/10/3/V_TRIPPED
  31                                               1
2014.10.12 23:58:53 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:58:53 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:58:53 5: publish received for MyMQTT/10/3/V_TRIPPED, 1
2014.10.12 23:58:53 2: IT set B_Dose_Fenster_LED on
2014.10.12 23:58:53 5: calling readingsSingleUpdate(mqtt_schalter1,state,1,1


ser. Monitor nach Neustart

Code Auswählen

Started!
<<10 26 00 06 4D 51 49 73 64 70 03 02 00 3C 00 18 4E 65 74 3A 3A 4D 51 54 54 3A 3A 4D 65 73 73 61 67 65 5B 33 32 33 30 5D
>>20 02 00 00
<<C0 00
>>D0 00
<<82 1E 00 05 00 19 4D 79 4D 51 54 54 2F 37 31 2F 30 2F 56 5F 4C 49 47 48 54 5F 4C 45 56 45 4C 00
>>90 03 00 05 00
0;0;3;0;9;send: 0-0-71-71 s=0,c=1,t=23,pt=0,l=0,st=fail:
<<82 17 00 06 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 00
>>90 03 00 06 00
0;0;3;0;9;send: 0-0-60-60 s=0,c=1,t=0,pt=0,l=0,st=fail:
<<82 17 00 07 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 00 82 1A 00 08 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 00 8A 1A 00 08 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 00 8A 17 00 06 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 00
>>90 03 00 07 00
0;0;3;0;9;send: 0-0-60-60 s=1,c=1,t=0,pt=0,l=0,st=fail:
<<8A 1A 00 04 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 00 8A 17 00 07 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 00 8A 1E 00 05 00 19 4D 79 4D 51 54 54 2F 37 31 2F 30 2F 56 5F 4C 49 47 48 54 5F 4C 45 56 45 4C 00
>>90 03 00 04 00
0;0;3;0;9;send: 0-0-10-10 s=3,c=1,t=16,pt=0,l=0,st=ok:
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.0
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 30
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.1
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 31
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.2
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 32
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.1
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 31
<<C0 00
>>D0 00
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:0
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 30
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:1
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 31
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:0
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 30
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:1
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 31
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.2
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 32
<<C0 00
>>D0 00
<<C0 00
>>D0 00
<<C0 00
>>D0 00
<<C0 00
>>D0 00
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.3
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 33
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.2
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 32
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.3
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 33
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:31.1
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 33 31 2E 31
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.3
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 33
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:27.8
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 37 2E 38
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.7
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 37
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:27.0
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 37 2E 30
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.4
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 34
<<C0 00
>>D0 00
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:0
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 30
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.8
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 38
0;0;3;0;9;read: 60-60-0 s=1,c=1,t=0,pt=7,l=5:26.3
MyMQTT/60/1/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 31 2F 56 5F 54 45 4D 50 32 36 2E 33
0;0;3;0;9;read: 10-10-0 s=3,c=1,t=16,pt=2,l=2:1
MyMQTT/10/3/V_TRIPPED
>>30 18 00 15 4D 79 4D 51 54 54 2F 31 30 2F 33 2F 56 5F 54 52 49 50 50 45 44 31
<<C0 00
>>D0 00
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.6
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 36
0;0;3;0;9;read: 60-60-0 s=0,c=1,t=0,pt=7,l=5:26.5
MyMQTT/60/0/V_TEMP
>>30 18 00 12 4D 79 4D 51 54 54 2F 36 30 2F 30 2F 56 5F 54 45 4D 50 32 36 2E 35
<<C0 00
>>D0 00



Momentan läüft es, kommt nur darauf wie lange .....

Momentan in den jetzigen Testbetrieb:
Schalter1
Temperatur 1 + 2

Mit den Definitionen:

Code Auswählen

define MQTT_MySensors MQTT 192.168.100.250:1883
#set MQTT_MySensors connect
attr MQTT_MySensors keep-alive 60
attr MQTT_MySensors verbose 5



Code Auswählen

# #####################################################
# MQTT_DEVICE / NRF24L01+ / MySensors / 2,4 Ghz
# *****************************************************

define mqtt_schalter1 MQTT_DEVICE
attr mqtt_schalter1 IODev MQTT_MySensors
attr mqtt_schalter1 alias Schalter 1
attr mqtt_schalter1 stateFormat transmission-state
#attr mqtt_schalter1 stateFormat state
attr mqtt_schalter1 subscribeReading_state MyMQTT/10/3/V_TRIPPED
attr mqtt_schalter1 room MQTT-Test
attr mqtt_schalter1 verbose 5

#define mqtt_pir1 MQTT_DEVICE
#attr mqtt_pir1 IODev MQTT_MySensors
#attr mqtt_pir1 alias Pir 1
#attr mqtt_pir1 stateFormat state
#attr mqtt_pir1 subscribeReading_state MyMQTT/40/1/V_TRIPPED
#attr mqtt_pir1 room MQTT-Test

define Pflanze MQTT_DEVICE
attr Pflanze IODev MQTT_MySensors
#attr Pflanze stateFormat transmission-state
attr Pflanze stateFormat state
attr Pflanze subscribeReading_state MyMQTT/71/0/V_LIGHT_LEVEL
attr Pflanze room MQTT-Test

define mqtt_Temperatur1 MQTT_DEVICE
attr mqtt_Temperatur1 IODev MQTT_MySensors
#attr mqtt_Temperatur1 stateFormat transmission-state
attr mqtt_Temperatur1 stateFormat state
attr mqtt_Temperatur1 subscribeReading_state MyMQTT/60/0/V_TEMP
attr mqtt_Temperatur1 room MQTT-Test
attr mqtt_Temperatur1 verbose 5

define mqtt_Temperatur2 MQTT_DEVICE
attr mqtt_Temperatur2 IODev MQTT_MySensors
#attr mqtt_Temperatur2 stateFormat transmission-state
attr mqtt_Temperatur2 stateFormat state
attr mqtt_Temperatur2 subscribeReading_state MyMQTT/60/1/V_TEMP
attr mqtt_Temperatur2 room MQTT-Test
attr mqtt_Temperatur2 verbose 5

define schalter1machwas notify mqtt_schalter1 { if (ReadingsVal("mqtt_schalter1","state", "not found") eq "0") { fhem "set B_Dose_Fenster_LED on" } }

fh555

#70
13 Oktober 2014, 00:29:56
ab 00:19 funktioniert es nicht mehr :-(

Zitat
2014.10.13 00:19:44 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.13 00:19:44 5: calling readingsSingleUpdate(mqtt_Temperatur1,state,26.1,1
2014.10.13 00:19:44 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.13 00:19:44 5: publish received for MyMQTT/60/0/V_TEMP, 26.1
2014.10.13 00:20:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:20:14 5: SW: c000
2014.10.13 00:20:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:21:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:21:14 5: SW: c000
2014.10.13 00:21:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:22:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:22:14 5: SW: c000
2014.10.13 00:22:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:23:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:23:14 5: SW: c000
2014.10.13 00:23:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:24:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:24:14 5: SW: c000
2014.10.13 00:24:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:25:14 5: SW: c000
2014.10.13 00:25:14 1: 192.168.100.250:1883 disconnected, waiting to reappear (MQTT_MySensors)
2014.10.13 00:25:14 1: 192.168.100.250:1883 reappeared (MQTT_MySensors)
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Connect/at-most-once MQIsdp/3/Net::MQTT::Message[3230]
2014.10.13 00:25:14 5: SW: 102600064d51497364700302003c00184e65743a3a4d5154543a3a4d6573736167655b333233305d
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:25:14 5: SW: c000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: ConnAck/at-most-once Connection Accepted
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 9 MyMQTT/71/0/V_LIGHT_LEVEL/at-most-once
2014.10.13 00:25:14 5: SW: 821e000900194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 10 MyMQTT/60/0/V_TEMP/at-most-once
2014.10.13 00:25:14 5: SW: 8217000a00124d794d5154542f36302f302f565f54454d5000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 11 MyMQTT/60/1/V_TEMP/at-most-once
2014.10.13 00:25:14 5: SW: 8217000b00124d794d5154542f36302f312f565f54454d5000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 12 MyMQTT/10/3/V_TRIPPED/at-most-once
2014.10.13 00:25:14 5: SW: 821a000c00154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: SW: 8a1a000800154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: SW: 8a17000b00124d794d5154542f36302f312f565f54454d5000
2014.10.13 00:25:14 5: SW: 8a17000a00124d794d5154542f36302f302f565f54454d5000
2014.10.13 00:25:14 5: SW: 8a1e000900194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.13 00:25:14 5: SW: 8a1a000c00154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 9/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 10/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 11/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 8/at-most-once

Ich habe 00:25 den Schalter1 ausgelöst und ohne Funktion :-(
Die Temperaturwerte wurden auch nicht mehr aktualisiert

Code Auswählen


Internals
IODev

MQTT_MySensors
NAME

mqtt_Temperatur1
NR

52
STATE

26.1
TYPE

MQTT_DEVICE
qos

0
retain

0
Readings
state

26.1

2014-10-13 00:19:44
transmission-state

subscription acknowledged

2014-10-13 00:25:14
mqtt_Temperatur1
Attributes
IODev

MQTT_MySensors

deleteattr
room

MQTT-Test

deleteattr
stateFormat

state

deleteattr
subscribeReading_state

MyMQTT/60/0/V_TEMP

deleteattr
verbose 5

deleteattr

fh555

#71
13 Oktober 2014, 00:41:50
und wieder "eingeschalfen" :-(

Code Auswählen

2014.10.13 00:25:14 5: SW: c000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: ConnAck/at-most-once Connection Accepted
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 9 MyMQTT/71/0/V_LIGHT_LEVEL/at-most-once
2014.10.13 00:25:14 5: SW: 821e000900194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 10 MyMQTT/60/0/V_TEMP/at-most-once
2014.10.13 00:25:14 5: SW: 8217000a00124d794d5154542f36302f302f565f54454d5000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 11 MyMQTT/60/1/V_TEMP/at-most-once
2014.10.13 00:25:14 5: SW: 8217000b00124d794d5154542f36302f312f565f54454d5000
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message sent: Subscribe/at-least-once 12 MyMQTT/10/3/V_TRIPPED/at-most-once
2014.10.13 00:25:14 5: SW: 821a000c00154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: SW: 8a1a000800154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: SW: 8a17000b00124d794d5154542f36302f312f565f54454d5000
2014.10.13 00:25:14 5: SW: 8a17000a00124d794d5154542f36302f302f565f54454d5000
2014.10.13 00:25:14 5: SW: 8a1e000900194d794d5154542f37312f302f565f4c494748545f4c4556454c00
2014.10.13 00:25:14 5: SW: 8a1a000c00154d794d5154542f31302f332f565f5452495050454400
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: PingResp/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 9/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 10/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 11/at-most-once
2014.10.13 00:25:14 5: MQTT MQTT_MySensors message received: SubAck/at-most-once 8/at-most-once
2014.10.13 00:26:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:26:14 5: SW: c000
2014.10.13 00:27:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:27:14 5: SW: c000
2014.10.13 00:28:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:28:14 5: SW: c000
2014.10.13 00:29:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:29:14 5: SW: c000
2014.10.13 00:30:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:30:14 5: SW: c000
2014.10.13 00:31:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:31:14 5: SW: c000
2014.10.13 00:32:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:32:14 5: SW: c000
2014.10.13 00:33:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:33:14 5: SW: c000
2014.10.13 00:34:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:34:14 5: SW: c000
2014.10.13 00:35:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:35:14 5: SW: c000
2014.10.13 00:36:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:36:14 5: SW: c000
2014.10.13 00:37:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:37:14 5: SW: c000
2014.10.13 00:38:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:38:14 5: SW: c000
2014.10.13 00:39:14 5: MQTT MQTT_MySensors message sent: PingReq/at-most-once
2014.10.13 00:39:14 5: SW: c000


Code Auswählen

DEF
192.168.100.250:1883
DeviceName

192.168.100.250:1883
FD

4
NAME

MQTT_MySensors
NOTIFYDEV

global
NR

32
NTFY_ORDER

50-MQTT_MySensors
PARTIAL

STATE

opened
TYPE

MQTT
buf

msgid

13
ping_received

0
timeout

60
Readings
connection

timed-out

2014-10-13 00:41:14

ntruchsess

#72
13 Oktober 2014, 12:09:05 Letzte Bearbeitung: 13 Oktober 2014, 12:15:56 von ntruchsess
@fh555:
Nach den Logs meldet sich die Gegenstelle (192.168.100.250) ja einfach ab (d.h. die Verbindung bricht ab, ist ja kein sauberer Disconnect über das mqtt-protokoll). was läuft denn unter '192.168.100.250'? Ist dass das MySensors MQTT-gateway, oder ein mosquitto-broker?

Während die Gegenstelle abgemeldet ist, kann nichts ankommen. Und nachgeliefert wird das auch nur, wenn der Sensor das mit 'retain' an den Broker senden würde (und der Broker nicht zwischendurch abstürzt)...

Und schau mal nach meinem Beitrag zu Deinem notify.

Gruß,

Norbert
while (!asleep()) {sheep++};

fh168

#73
15 Oktober 2014, 07:23:42
hallo,

fh555 kann gerade nicht anworten, weil er im Urlaub ist.

Was anderes: ich habe zwei 18B20 parallel auf einer Platine geschaltet, wie spreche ich die mit Fhem an?

Die melden sich im Arduino mit


Code Auswählen
MyMQTT/21/0/V_TEMP
MyMQTT/21/1/V_TEMP

wenn ich einen

Code Auswählen
attr mySensorsTemp autoSubscribeReadings MyMQTT/21/+/V_TEMP

mit wildcards mache, findet er nur den ersten Sensor.

Vielen Dank noch für die positiven Bewertungen in meinem Blog-Beitrag.

LG
/robin
Hue, Lacrosse, PCA301, MySensors, V 1.67 CUL 868 V3.4, Lacrosse-WLAN-Gateway, Tasmota RF-

ntruchsess

#74
15 Oktober 2014, 08:15:17
Ich hab das grade im Trockenlauf getestet, funktioniert. (In Ermangelung von MySensors-sensoren habe ich die mqtt-messages habe ich mit 'mosquitto_pub -h 192.168.1.4 -t MyMQTT/21/0/V_TEMP -m "wert1"' bzw. 'mosquitto_pub -h 192.168.1.4 -t MyMQTT/21/1/V_TEMP -m "wert2"' geschickt).
Muss also irgendwo außerhalb von fhem liegen. Du kannst mit attr verbose 5 an den MQTT-devices den loglevel so einstellen, dass Du alle von FHEM geschickten und empfangenen Messages detailiert sehen kannst.

Du darfst in Deinem Blog übrigens ruhig konkret angeben, wer die MQTT-module geschrieben hat.

gruß
while (!asleep()) {sheep++};
Drucken
Nach oben Seiten 1 ... 3 4 5 6 7 ... 74
Benutzer-Aktionen