MQTT switch based rules caused pimatic to freeze

---

Hey folks,

I bought some Sonoff devices (POW, T1, TOUCH / all running Tasmota 5.13.1) and exchanged them against my old 433Mhz Homeduino stuff…

so far so good: everything is working like a charme when sending ON/OFF commands manually.

now, a few days later pimatic FREEZES every time when sending a sunset based command to my MQTT Mosquito server running on Synology NAS in sleep mode:

 {
      "class": "MqttSwitch",
      "id": "mqttsonoffPOWswitch1",
      "name": "▒_TX Garten Beleuchtung",
      "topic": "cmnd/sonoffPOW1/Power",
      "stateTopic": "stat/sonoffPOW1/POWER",
      "onMessage": "ON",
      "offMessage": "OFF",
      "hap": {
        "service": "Lightbulb",
        "exclude": false
      }

rule looks like:

 {
      "id": "gardenlight",
      "name": "Gartenlicht EIN",
      "rule": "when its after sunset then switch mqttsonoffPOWswitch1 on",
      "active": true,
      "logging": true
    },

taking a look to the log file offers a stop a the last command entry but without success:

tail -100 pimatic-daemon.log
21:00:00.727 [pimatic] info: rule warmwater-weekday: turned ✇ Zirkulationspumpe on
21:05:01.114 [pimatic] info: rule warmwater-weekday: turned ✇ Zirkulationspumpe off
21:05:39.697 [pimatic] info: rule gardenlight: turned 🔘 Garten Beleuchtung on
pi@pimatic:~/pimatic-app $

Any ideas what’s possibly going wrong here?

Kind Regards,
Paule

same behaviour today at same rule:

21:00:01.605 [pimatic] info: rule fenster3-offen: pushover message sent successfully
21:02:55.585 [pimatic] info: rule airchange-2: pushover message sent successfully
21:05:01.624 [pimatic] info: rule warmwater-weekday: turned ✇ Zirkulationspumpe off
21:07:13.525 [pimatic] info: rule gardenlight: turned 🔘 Garten Beleuchtung on
pi@pimatic:~/pimatic-app $ 

with high utilization of pimatic.js:

PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
530 root 20 0 254M 171M 19540 R 84.3 39.6 3h39:01 /usr/local/bin/node /usr/local/bin/pimatic.js start

the rule was fired but without success… web frontend without response anymore… so I have to reboot the raspberry:

22:00:39.111 [pimatic-mqtt] info: Successfully connected to MQTT Broker default
Unhandled rejection (<{"error":{"code":"ECONNRESET"},"option...>, no stack trace)

Why do you use “after” in your rule?
Wouldn’t be “when its sunset” enough?

I ask because with “after” the rule is true all the time after sunset and will trigger unlimited probably.

@saxnpaule said in MQTT switch based rules caused pimatic to freeze:

Why do you use “after” in your rule?
Wouldn’t be “when its sunset” enough?

I ask because with “after” the rule is true all the time after sunset and will trigger unlimited probably.

hmm? can’t remember what the reason was… but: this rule was originaly used for the homeduino devices and I just put the ESP Sonoff devices (MQTT) in…

will try that, thanks for reply.

that’s so bad indeed: same thing today

pimatic is not responding after firing the explainded rule above…

@cybolord said in MQTT switch based rules caused pimatic to freeze:

that’s so bad indeed: same thing today

pimatic is not responding after firing the explainded rule above…

…maybe someone has a hint for this, please? should I deliver further config or log content?

@saxnpaule said in MQTT switch based rules caused pimatic to freeze:

Why do you use “after” in your rule?
Wouldn’t be “when its sunset” enough?

I ask because with “after” the rule is true all the time after sunset and will trigger unlimited probably.

so, here comes the weird thing: changed the rule to a fixed time and everything works again:

 {
      "id": "gardenlight",
      "name": "Gartenlicht EIN",
      "rule": "when its 21:45 then switch mqttsonoffPOWswitch1 on",
      "active": true,
      "logging": true
    },

have other sunset / sunrise based rules that are fine; what’s going on here?!?

~~new rule of thumb (for me): every time when words like “weird” or “strange” appear = check your SDCARD for corruption!

this is the THIRD time in two years that a corrupted SDCARD costs me hours of analyses… was a well known brand

solution: cloned to ISO and back to new SDCARD = everything is working like a charme again - pah

please mark as SOLVED - thank you.~~

…back again: after running fine for 4 days the issue is back!!

this is driving me mad indeed… please: need hint to expand debug logging for analyses: can only see last rule event and pimatic is freezed

thank you.

…meanwhile I found out that when a MQTT “Switch On” rule ist fired at sunset AND mplayer process is running in memory -> then pimatic freezed and stuck at last command!

any ideas how this can happen or what dependencies take place?!