pimatic@0.9.52

---

• 20190823, V0.9.52
  • Fixed bug in variable expression handler introduced by earlier refactoring

After updating to the latest Pimatic version a rule for one of my camera’s is no longer working.
It gives me the following error:

error executing an action: Error: Command failed: /bin/sh -c ffmpeg -y -i 'rtsp://192.168.2.23/user=*****_password=******_channel=1_stream=0.sdp?real_stream' -f image2 -vframes 1 -pix_fmt yuvj420p /home/pi/pimatic-app/node_modules/pimatic-mobile-frontend/public/img/temp.jpeg 2> /dev/null

Any idea what could be the reason and how I can fix this?

@djmvt Can you please try to execute the command in the console? Please also make sure the path /home/pi/pimatic-app/node_modules/pimatic-mobile-frontend/public/img/still exists after the update

• open a terminal
• execute sudo bash
• then execute /bin/sh -c ffmpeg -y -i 'rtsp://192.168.2.23/user=*****_password=******_channel=1_stream=0.sdp?real_stream' -f image2 -vframes 1 -pix_fmt yuvj420p /home/pi/pimatic-app/node_modules/pimatic-mobile-frontend/public/img/temp.jpeg 2> /dev/null

Ok will do but I’m not at home next couple of days so cannot test till Monday. I do have access to Pimatic remotely but cannot connect to the pi directly.

Thanks, will follow up on this next Monday!

I guess it’s indeed the issue that the path is missing since the mobile frontend update. Would it be possible (since I won’t be able to log in to the pi directly) to create the path from the frontend with a rule? Maybe that’s to farfetched but since it’s possible to execute a command from a rule it is maybe a way to fix it without connecting to the pi?

Haha that actually fixed it! I’ve created a rule that executed a mkdir command at the push of a button and it is working again! Thanks, had to let it sink for a while but problem fixed

@djmvt Excellent. I am glad to hearing you were able to fix it via remote access to pimatic web frontend.

I haven’t thought about this option myself when I read your earlier post. Indeed, the shell plugin can be used as an execution device to call arbitrary commands from the remote and one should be aware the implied security risks.

@mwittig absolutely, that’s the only “danger” in this method. I want to be able to access Pimatic when not at home but it is not a really save way. Also to get the picture from the camera saved I have to send the username and password open over the network. It’s not a huge problem since this is a fixed camera only showing the portal of my house but it is a security risk. Tried to run Pimatic with ssl enabled but couldn’t get that to work. So only security for now is an alternative port number and ofcourse the login for the frontend itself.

@djmvt said in pimatic@0.9.52:

Tried to run Pimatic with ssl enabled but couldn’t get that to work.

I’ll take this into account for the dockerized pimatic setup I am currently working on. Using SSL with a qualified certificate should become easy this way.