Beiträge von Alero

Keiner eine idee?

hi, habe mir das Video angeschaut und soweit auch umgesetzt. Leider ist die mcu nach ca. 30 sek. nicht mehr erreichbar. erst wenn ich das usb Kabel entferne und es wieder einstecke habe ich wieder kurz kontakt. Im Iobroker ist dann auch mqtt mit einem gelben dreieck. (Verbindung fehlegschlagen)

jemand eine Idee?

Software ESPEasy_R120_1024.bin. Alle Einstellungen so wie im Video eingestellt.

es scheint am MQTT zu liegen. hier ein Auszug vom iobroker debug log:

mqtt.2	2023-07-05 08:02:03.335	debug	onStateChange mqtt.2.info.connection: {"val":"","ack":true,"ts":1688536923334,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536898297}
mqtt.2	2023-07-05 08:02:03.335	debug	stateChange mqtt.2.info.connection: {"val":"","ack":true,"ts":1688536923334,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536898297}
mqtt.2	2023-07-05 08:02:03.328	info	Starting MQTT-WebSocket server on 192.168.42.15:1888
mqtt.2	2023-07-05 08:02:03.327	info	Starting MQTT server on 192.168.42.15:1887
mqtt.2	2023-07-05 08:02:03.104	debug	Schedule restart: * * * * *
mqtt.2	2023-07-05 08:02:03.083	info	starting. Version 4.1.1 in /opt/iobroker/node_modules/iobroker.mqtt, node: v16.16.0, js-controller: 4.0.24
mqtt.2	2023-07-05 08:02:02.874	debug	Plugin sentry Initialize Plugin (enabled=true)
mqtt.2	2023-07-05 08:02:00.528	info	Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
mqtt.2	2023-07-05 08:02:00.528	debug	Plugin sentry destroyed
mqtt.2	2023-07-05 08:02:00.527	info	terminating
mqtt.2	2023-07-05 08:02:00.007	info	Scheduled restart.
mqtt.2	2023-07-05 08:01:38.299	debug	onStateChange mqtt.2.Stromzaehler.status: {"val":"Connection Lost","ack":true,"ts":1688536898297,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1687952226454}
mqtt.2	2023-07-05 08:01:38.299	debug	stateChange mqtt.2.Stromzaehler.status: {"val":"Connection Lost","ack":true,"ts":1688536898297,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1687952226454}
mqtt.2	2023-07-05 08:01:38.299	debug	onStateChange mqtt.2.info.connection: {"val":"","ack":true,"ts":1688536898297,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536898297}
mqtt.2	2023-07-05 08:01:38.299	debug	stateChange mqtt.2.info.connection: {"val":"","ack":true,"ts":1688536898297,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536898297}
mqtt.2	2023-07-05 08:01:38.296	debug	Server received "/Stromzaehler/status" (string): "Connection Lost"
mqtt.2	2023-07-05 08:01:38.295	info	Client [ESPClient1] connection closed: timeout
mqtt.2	2023-07-05 08:01:15.794	debug	Client [ESPClient1] send to this client "/Stromzaehler/Pulse/Time": 0
mqtt.2	2023-07-05 08:01:15.793	debug	onStateChange mqtt.2.Stromzaehler.Pulse.Time: {"val":0,"ack":true,"ts":1688536875791,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536875791}
mqtt.2	2023-07-05 08:01:15.793	debug	stateChange mqtt.2.Stromzaehler.Pulse.Time: {"val":0,"ack":true,"ts":1688536875791,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536875791}
mqtt.2	2023-07-05 08:01:15.792	debug	Client [ESPClient1] send to this client "/Stromzaehler/Pulse/Total": 0
mqtt.2	2023-07-05 08:01:15.790	debug	Client [ESPClient1] send to this client "/Stromzaehler/Pulse/Count": 0
mqtt.2	2023-07-05 08:01:15.789	debug	onStateChange mqtt.2.Stromzaehler.Pulse.Total: {"val":0,"ack":true,"ts":1688536875787,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536875787}
mqtt.2	2023-07-05 08:01:15.789	debug	stateChange mqtt.2.Stromzaehler.Pulse.Total: {"val":0,"ack":true,"ts":1688536875787,"q":0,"from":"system.adapter.mqtt.2","user":"system.user.admin","lc":1688536875787}
mqtt.2	2023-07-05 08:01:15.788	debug	Server received "/Stromzaehler/Pulse/Time" (number): 0
mqtt.2	2023-07-05 08:01:15.788	debug	Found object for topic "/Stromzaehler/Pulse/Time" = mqtt.2.Stromzaehler.Pulse.Time