Pimatic shutdown?

---

After a working setup using a TX/RX tranceiver set on a breadboard and Homeduino/WiringPI plugins I wanted to switch to a more robust RFXCOM solution.

I reinstalled Raspian (Pixel) and Pimatic from scratch again. Installed the RFXCOM device and plugin and restarted the PI.
Installed my KAKU switch and created a rule to switch on KAKU at a certain time. However KAKU was not switched on at the specified time. Only when I open the Pimatic webpage, the KAKU was switched on.

What could be wrong?
Does somebody have the same experience?

@focussing could you post the debug log?

@Gleno0h

This is the interesting part. At 12:02 I switched on/off manually.
At 13:05 the rule should trigger switch on - it did not.
At 13:09 I opened the webpage, and suddenly it switched on…

12:02:15.299 [pimatic-rfxcom] debug: [RFXComProtocol] code: 0x01595522 - unitcode: 1 - packetType: lighting2 - value: true
[rfxcom] on /dev/ttyUSB0 - Sent : 0B,11,00,06,01,59,55,22,01,01,0F,00
[rfxcom] on /dev/ttyUSB0 - Received: 04,02,01,06,00
12:02:17.156 [pimatic-rfxcom] debug: [RFXComProtocol] code: 0x01595522 - unitcode: 1 - packetType: lighting2 - value: false
[rfxcom] on /dev/ttyUSB0 - Sent : 0B,11,00,07,01,59,55,22,01,00,00,00
[rfxcom] on /dev/ttyUSB0 - Received: 04,02,01,07,00
13:09:34.198 [pimatic-rfxcom] debug: [RFXComProtocol] code: 0x01595522 - unitcode: 1 - packetType: lighting2 - value: true
[rfxcom] on /dev/ttyUSB0 - Sent : 0B,11,00,08,01,59,55,22,01,01,0F,00
13:09:34.218 [pimatic] info: rule test: turned schakelaar 1 on
13:09:34.656 [pimatic-mobile-frontend] info: rendering theme: graphite/water
13:09:37.385 [pimatic-mobile-frontend] info: rendering theme finished
[rfxcom] on /dev/ttyUSB0 - Received: 04,02,01,08,00
[rfxcom] on /dev/ttyUSB0 - Received: 0B,11,00,01,01,59,55,22,01,00,00,70
14:06:52.154 [pimatic-rfxcom] info: lighting2: {“subtype”:0,“seqnbr”:1,“id”:“0x01595522”,“unitcode”:1,“commandNumber”:0,“command”:“Off”,“level”:0,“rssi”:7}
14:06:52.165 [pimatic-rfxcom] debug: [RfxComPowerSwitch#schakelaar-1] Device: { id: ‘rfx-0x01595522-1’,
14:06:52.165 [pimatic-rfxcom] debug:> response:
14:06:52.165 [pimatic-rfxcom] debug:> { id: ‘rfx-0x01595522-1’,
14:06:52.165 [pimatic-rfxcom] debug:> code: ‘0x01595522’,
14:06:52.165 [pimatic-rfxcom] debug:> unitcode: 1,
14:06:52.165 [pimatic-rfxcom] debug:> command: ‘Off’,
14:06:52.165 [pimatic-rfxcom] debug:> packetType: ‘lighting2’,
14:06:52.165 [pimatic-rfxcom] debug:> classname: ‘RfxComPowerSwitch’ } }
14:06:52.169 [pimatic-rfxcom] debug: [RfxComPowerSwitch#schakelaar-1] code: 0x01595522
14:06:52.172 [pimatic-rfxcom] debug: [RfxComPowerSwitch#schakelaar-1] unitcode: 1
pi@raspberrypi3:~/pimatic-app $

https://forum.pimatic.org/topic/2593/pimatic-cron-doesnt-work-until-i-login-to-web-panel

known issue I have the work-arround with the cron job running but I think it is very ugly.

@sweetpi is ther already a ticket in GITHUB for this? Could not find one.

@thex Thanks! That looks indeed the same problem. I tried to remember when I setup the previous working setup.
That must have been last quarter this year. It was one of the first Pixel versions from what I remember.

So it should be something that has changed in Raspian over that period…