Gosund SP111 mit ESPurna 1.13.2 MQTT

Begonnen von Edi77, 04 Oktober 2018, 00:22:09

Vorheriges Thema - Nächstes Thema

Edi77

Hallo

Habe da ein Problem mit einer SP111

Im DEBUG Fenster kommt folgendes an

629052] [MQTT] Sending /sp111a/KS/apparent => 0 (PID 1)
[629058] [MQTT] Sending /sp111a/KS/factor => 0 (PID 1)
[629063] [MQTT] Sending /sp111a/KS/energy => 0.003 (PID 1)
[687002] [NTP] Error: NTP server not reachable
[689106] [MQTT] Sending /sp111a/KS/current => 0.000 (PID 1)
[689110] [MQTT] Sending /sp111a/KS/voltage => 230 (PID 1)
[689112] [MQTT] Sending /sp111a/KS/power => 0 (PID 1)
[689114] [MQTT] Sending /sp111a/KS/reactive => 0 (PID 1)
[689118] [MQTT] Sending /sp111a/KS/apparent => 0 (PID 1)
[689123] [MQTT] Sending /sp111a/KS/factor => 0 (PID 1)
[689128] [MQTT] Sending /sp111a/KS/energy => 0.003 (PID 1)
[747000] [NTP] Error: NTP server not reachable
[749175] [MQTT] Sending /sp111a/KS/current => 0.000 (PID 1)
[749178] [MQTT] Sending /sp111a/KS/voltage => 230 (PID 1)
[749181] [MQTT] Sending /sp111a/KS/power => 0 (PID 1)
[749182] [MQTT] Sending /sp111a/KS/reactive => 0 (PID 1)
[749185] [MQTT] Sending /sp111a/KS/apparent => 0 (PID 1)
[749190] [MQTT] Sending /sp111a/KS/factor => 0 (PID 1)
[749195] [MQTT] Sending /sp111a/KS/energy => 0.003 (PID 1)
[765267] [WEBSOCKET] Requested action: relay
[765270] [RELAY] #0 scheduled ON in 0 ms
[765274] [RELAY] #0 set to ON
[765277] [MQTT] Sending /sp111a/KS/relay/0 => 1 (PID 1)
[765755] [WEBSOCKET] Requested action: relay
[765758] [RELAY] #0 scheduled OFF in 0 ms
[765763] [RELAY] #0 set to OFF
[765765] [MQTT] Sending /sp111a/KS/relay/0 => 0 (PID 1)
[766767] [RELAY] Saving mask: 0


Soweit alles in Ordnung, die Daten kommen auch im FHEM an:



define ESP35gosundsp111KS MQTT_DEVICE
attr ESP35gosundsp111KS IODev mqttServer
attr ESP35gosundsp111KS event-on-change-reading .*
attr ESP35gosundsp111KS room MQTT
attr ESP35gosundsp111KS subscribeReading_sp111a_apparent /sp111a/KS/apparent
attr ESP35gosundsp111KS subscribeReading_sp111a_board /sp111a/KS/board
attr ESP35gosundsp111KS subscribeReading_sp111a_current /sp111a/KS/current
attr ESP35gosundsp111KS subscribeReading_sp111a_energy /sp111a/KS/energy
attr ESP35gosundsp111KS subscribeReading_sp111a_factor /sp111a/KS/factor
attr ESP35gosundsp111KS subscribeReading_sp111a_host /sp111a/KS/host
attr ESP35gosundsp111KS subscribeReading_sp111a_ip /sp111a/KS/ip
attr ESP35gosundsp111KS subscribeReading_sp111a_power /sp111a/KS/power
attr ESP35gosundsp111KS subscribeReading_sp111a_reactive /sp111a/KS/reactive
attr ESP35gosundsp111KS subscribeReading_sp111a_rssi /sp111a/KS/rssi
attr ESP35gosundsp111KS subscribeReading_sp111a_status /sp111a/KS/status
attr ESP35gosundsp111KS subscribeReading_sp111a_uptime /sp111a/KS/uptime
attr ESP35gosundsp111KS subscribeReading_sp111a_version /sp111a/KS/version
attr ESP35gosundsp111KS subscribeReading_sp111a_voltage /sp111a/KS/voltage
attr ESP35gosundsp111KS subscribeReading_sp111a_vcc /sp111a/KS/vcc
# attr ESP35gosundsp111KS subscribeReading_sp111a_relay /sp111a/KS/relay/0

define FileLog_ESP35gosundsp111KS FileLog ./log/ESP35gosundsp111KS-%Y.log ESP35gosundsp111KS:.*
attr FileLog_ESP35gosundsp111KS logtype text
attr FileLog_ESP35gosundsp111KS room LogDateien

define ESP35gosundsp111KSre MQTT_DEVICE
attr ESP35gosundsp111KSre IODev mqttServer
attr ESP35gosundsp111KSre event-on-change-reading .*
attr ESP35gosundsp111KSre room MQTT
attr ESP35gosundsp111KSre eventMap 1:ON 0:OFF
# attr ESP35gosundsp111KSre devStateIcon 1:rc_GREEN:0 0:rc_RED:1
attr ESP35gosundsp111KSre devStateIcon ON:rc_GREEN:OFF OFF:rc_RED:ON
attr ESP35gosundsp111KSre icon hue_filled_br30
attr ESP35gosundsp111KSre publishSet ON OFF /sp111a/KS/relay/0
attr ESP35gosundsp111KSre webCmd ON:OFF
attr ESP35gosundsp111KSre stateFormat state
attr ESP35gosundsp111KSre subscribeReading_sp111a_relay /sp111a/KS/relay/0

define FileLog_ESP35gosundsp111KSre FileLog ./log/ESP35gosundsp111KSre-%Y.log ESP35gosundsp111KSre:.*
attr FileLog_ESP35gosundsp111KSre logtype text
attr FileLog_ESP35gosundsp111KSre room LogDateien


Das Relay schaltet also mit 0 und 1
Im Terminal kann ich mit
# mosquitto_pub -t /sp111a/KS/relay/0/set -m 1
# mosquitto_pub -t /sp111a/KS/relay/0/set -m 0

Ich habe es mal mit
{mosquitto_pub('-t','/sp111a/KS/relay/0/set','-m','1')}
{mosquitto_pub(-t /sp111a/KS/relay/0/set -m 1)}
versucht, hat aber nicht funktioniert

Auch das hier funktioniert
# curl http://192.168.1.35/api/sp111a/KS/relay/0?apikey=E7858A4534DD9400 {"relay0":1}


Wo ist mein Fehler?
Master FHEM 6 als VM auf ESX Ubuntu 20.04 LTS mit MAXCube/MAX!/FS20|TabletUI|Flightradar|Tasmota|TTN Lora|CCU3 HomematicIP|RPi mit GammaScout|MQTT EasyESP 8266|LuftdatenInfo|deCONZ HUEDev|probemon|Siemens Logo|P4D|3D PRINTER RAISE3D

Beta-User

probiere es mal mitattr ESP35gosundsp111KSre publishSet_ON /sp111a/KS/relay/0/set
attr ESP35gosundsp111KSre publishSet_OFF /sp111a/KS/relay/0/set

Und am besten an der Konsole mit mosquitto_sub beobachten, was da abläuft und ggf. nachregeln.

Kann auch sein, dass es die publishReading_...-Attribute sind, die weiterhelfen.
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn: u.a MySensors, Weekday-&RandomTimer, Twilight,  div. attrTemplate-files