Pimatic-Lirc doesn't work right after RPi restart

---

Hi everybody,

I’m using pimatic for about a month right now. I’m really happy with it.
For now there are just 2 small issues.
If the Pi restarts for some reason (mostly when it accidentally gets disconnected from it’s power source) then pimatic says something like “lirc_conf.json” not found. So I have to restart pimatic manually. I will give you the exact message when I’m back home again.

Maybe pimatic try’s to initiate the lirc services a little to soon?
Pilight shows a similar behaviour because it says it cannot find SSDP connection when trying to send RF commands. A service restart of pilight resolves the problem too.

Any idea? I was thinking about a little “Sleep” command at some point.

Regards

Pascal

@Partovic Maybe the account used for the service doesn’t have enough rights ?

@koffienl which service? pimatic or lirc? I didn’t make any special settings. Everything is default.

@Partovic said:

lirc_conf.json" not found.

The error is : lirc_conf.json" not found , so perhaps the pimatic service doesn’t have anough rights to access that file ?

@koffienl but wouldn’t that result in no function at all? after a restart, pimatic works fine. So it seems to be there es no real right issue. I’m thinking of something like a racecondition …

Hi, sorry for being so late.
Here’s the output after I restart the Pi:

• error [pimatic]: Could not parse rule “if remote of LircRemote is equal to “Alphaluxx” and command of LircRemote is equal to “KEY_STOP” then press leinwand_stop”: Cannot find module ‘/tmp/cached_remotes_lirc.json’

restart of pimatic resolves the problem.
Any ideas?

@Partovic said:

‘/tmp/cached_remotes_lirc.json’

How do you restart pimatic ?

@koffienl this message only occurs when the whole pi get’s a “restart” (means unexpected disconnect from the power source). after that i have to restart pimatic by “service pimatic restart”

Just want to have it as failsave as possible. short power outtages should not prevent pimatic lirc from working.

I have tested pimatic-lirc and run into the same issue. After a reboot I get 220 x this Error “Cannot find module '/tmp/cached_remotes_lirc.json”.
And a lot of other stuff does’t work any more. After stop/start pimatic service its ok.

22:50:29.406 [pimatic] info: New device "System"...
22:51:50.464 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:50.930 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:50.957 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:50.987 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.016 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.044 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.070 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.099 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.125 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.157 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.183 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.209 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.234 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.260 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.286 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.329 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.355 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.381 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.407 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.436 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.462 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.488 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.519 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.549 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.576 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.602 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.628 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.653 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.736 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.762 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.788 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.814 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.844 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.870 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.895 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.921 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.947 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.973 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:51.999 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.025 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.052 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.078 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.104 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.129 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.155 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.181 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.207 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.233 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.259 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.285 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.310 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.336 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.362 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.388 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.414 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.439 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.465 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.491 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.517 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.551 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.577 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.603 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.631 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.657 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.683 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.709 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.735 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.761 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.787 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.813 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.838 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.864 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.890 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.916 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.942 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.967 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:52.993 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.019 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.045 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.071 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.096 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.122 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.148 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.174 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.200 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.226 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.252 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.278 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.303 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.329 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.355 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.381 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.407 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.432 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.459 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.485 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.511 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.537 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.563 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.589 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.614 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.640 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.666 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.691 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.717 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.743 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.769 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.795 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.820 [pimatic] error: Could not force add rule, because error has no rule attribute.
22:51:53.850 [pimatic] error: Could not parse rule "if pimatic is starting then set $start to 0 and after 30 second set $start = 1": Cannot find module '/tmp/cached_remotes_lirc.json'
22:51:53.856 [pimatic] error: Could not parse rule "if [it is after sunset or before sunrise] and ping_sat_wohnzimmer is present for 5 seconds then turn on AmbiLight": Cannot find module '/tmp/cached_remotes_lirc.json'
22:51:53.859 [pimatic] error: Could not parse rule "if its 06:30 and kaffeeStatus of kaffeesatz-status = "voll" then turn Unitec2 on and set $kaffee_status = "Kaffe läuft..." and push title:"Kaffe läuft..." message:"..." and after 5 minutes push title:"Kaffe ist fertig..." message:"..." and after 5 minutes set $kaffee_status = "Kaffee ist fertig" and after 20 minutes turn unitec2 off and after 21 minutes set $kaffee_status = "leer"": Cannot find module '/tmp/cached_remotes_lirc.json'
...

Maybe the following occurs:
After a reboot of pi, all files in directory ’ /tmp’ (FS = ‘tmpfs’) are deleted and service ’ pimatic’ is starting earlier than service ‘lirc’, so the file ‘/tmp/cached_remotes_lirc.json’ is not available when service pimatic is starting for the first time. When you start pimatic for the second time all the files are available and you don’t get any errors.

Could be a possible explanation. Anyone with in idea To fix that? Setting Kind of a Delay on any Part?

@magic-tune Yes, for me it works when I restart pimatic again

The plugin pimatic-lirc should implement an check for the file and try to open it after an certain time. This should repeat like 10 times.

@Partovic Just a hint and I’m not sure about this:

in the init script of pimatic “/etc/init.d/pimatic” you find the block:

### BEGIN INIT INFO
# Provides:          pimatic
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: pimatic service
# Description:       pimatic home automation framework init.d script for debian systems.
### END INIT INFO

Maybe if you set (Not sure if it is $lirc or something else)

# Required-Start:    $remote_fs $syslog $lirc

or (After all services have been started)

# Required-Start:    $remote_fs $syslog $all

With this you should be able to delay the start of pimatic after every other service has started on the pi

@techbarney quite a good hint. will try that! is there a list of all available / usable variables for the init script?

@Partovic
Can you check the following directory “/etc/rc2.d” ?
Is there in the directory “/etc/rc2.d” a file named “S<nn>lirc”. The file should be symbolic link to “…/init.d/lirc”. I don’t have installed lirc, so I don’t know the exact name of the lirc service.
What is the exact filename of pimatic in the directory “/etc/rc2.d”?
On my system it is “S02pimatic -> …/init.d/pimatic”

John

@Partovic
@john1957 give your the right hint with the deleted /tmp folder.
This should help: edit /etc/default/rcS

# delete files in /tmp during boot older than x days.
# '0' means always, -1 or 'infinite' disables the feature
TMPTIME=-1

@magic-tune and @john1957
I’ve tried that yesterday. unfortunately it does not work for me.
First it was #TMPTIME=0.
Then i removed the hashtag and changed it to -1. no effect at all.
I also tried # Required-Start: $remote_fs $syslog $all
Am I missing something?

@Partovic I have try a little bit:
use in “/etc/init.d/pimatic” the line # Required-Start: $all

after that execute update-rc.d pimatic defaults

then you can check for example in /etc/rc2.d/ which position pimatic has. With $all, it should have the same number as rc.local

Then a reboot and please a report