Dev-br-1 1.0.2

[pimagical]

update to 1.0.2 and pimatic restart gave:

error [pimatic]: Cannot find module './base' error [pimatic]: [Error: Couldn't find plugin info for pimatic-ip-camera]

IpCameraDevice is gone in the GUI.

[funky81]

Ok, my mistakes. I will upload the revision.

Sent from Xiaomi MiNote On Aug 4, 2015 3:43 PM, "pimagical" notifications@github.com wrote:

update to 1.0.2 and pimatic restart gave:

error [pimatic]: Cannot find module './base' error [pimatic]: [Error: Couldn't find plugin info for pimatic-ip-camera]

IpCameraDevice is gone in the GUI.

— Reply to this email directly or view it on GitHub https://github.com/funky81/pimatic-ip-camera/issues/5.

[pimagical]

updated to 1.0.4 and pimatic restart gave:

error [pimatic-mobile-frontend]: Client error: Unable to process binding "template: function (){return { name:'devicepage-template',foreach:devicepages} }" Message: Unable to process binding "template: function (){return { name:'device-group-template',foreach:$root.groups} }" Message: Unable to process binding "if: function (){return $root.enabledEditing() || $parent.getDevicesInGroup($data.id).length > 0 }" Message: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$parent.getDevicesInGroup($data.id),afterRender:$parent.afterRenderDevice} }" Message: Cannot find template with ID ipcamera-template

error [pimatic]: [Error: Couldn't find plugin info for pimatic-ip-camera]

[funky81]

I've just re-installed my pimatic. somehow I cant find the above error. do you mind to paste here your config.json?

[funky81]

Hi @pimagical, i think you have to re-install the plugin. I try to re-create your situation and found out that the possible solution for this is remove the pimatic-ipcamera plugin directory then reinstall it again. it works fine without touch / modify the config.json file.

please let me know either this working or not. thanks

[pimagical]

1. Yes i had a few issue so i deleted the plugin reference into the config. After your 1.0.4 update i added it again to the config and after a restart it created another plugin folder in node_modules so ended up with a pimatic_ip_camera and a pimatic_ipcamera folder. This gave again problems. Deleted both and a restart fixed this.
2. I had left device "name" with some spaces and have given it a real name now. After this i haven't had the above error any more.
3. With 1.0.4 i experienced twice after an hour when started the stream an stop the stream, pimatic becomes unreachable and get a memory message in the linux chrome browser. Restarting the raspberry pi would not get the pimatic service up and running. So i deleted the pimatic_ipcamera folder with ssh and with a restart the pimatic service will come up again. There are some issues yet to be solved.

[funky81]

Thanks for the feedback. Somehow I feel the same way, it seems this plugins consume too much memory. See if I can fixed this tonight.

Sent from Xiaomi MiNote On Aug 8, 2015 7:24 PM, "pimagical" notifications@github.com wrote:

1.

Yes i had a few issue so i deleted the plugin reference into the config. After your 1.0.4 update i added it again to the config and after a restart it created another plugin folder in node_modules so ended up with a pimatic_ip_camera and a pimatic_ipcamera folder. This gave again problems. Deleted both and a restart fixed this. 2.

I had left device "name" with some spaces and have given it a real name now. After this i haven't had the above error any more. 3.

With 1.0.4 i experienced twice after an hour when started the stream an stop the stream, pimatic becomes unreachable and get a memory message in the linux chrome browser. Restarting the raspberry pi would not get the pimatic service up and running. So i deleted the pimatic_ipcamera folder with ssh and with a restart the pimatic service will come up again. There are some issues yet to be solved.

— Reply to this email directly or view it on GitHub https://github.com/funky81/pimatic-ip-camera/issues/5#issuecomment-128973032 .

[funky81]

i just update the plugins...now it's just picture refresh. not image base64 streaming