Hi everyone,
I just solved it myself. I setup pimatic as a service and rebooted my pi. Now it seems to work like a charm. I will test now my rules
Cheers
Questions about the release of v0.9
Hi everyone,
I just solved it myself. I setup pimatic as a service and rebooted my pi. Now it seems to work like a charm. I will test now my rules
Cheers
I’m impressed by the work you did, thank you very much!
One question I stumbled over is the following output as soon as pimatic is checking for new updates: Could not get plugin info from update server, request info from npm
How can I solve it?
Cheers
I still have the problem, any ideas?
sorry i have no clue, maybe @mwittig?
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebook
make it so !
The last three days i also getting Could not get plugin info from update server, request info from npm
and no updates are found. maybe the ppm server or so is down?
pimatic-google-calendar | pimatic-wmi | pimatic-snmp | pimatic-wakeonlan |
Like my work? Then consider a donation
Follow me: www.thorstenreichelt.de
the update server seems to be running fine.
but i will ask sweetpi for a reboot
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebook
make it so !
@thost96 said in Questions about the release of v0.9:
The last three days i also getting
Works fine for me. Please reboot your Raspi and check if you still get the error
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
another important information is that if you have manually installed a plugin that is not (yet) available on npm, you will receive this error.
do you have such plugins?
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebook
make it so !
@leader21 ahh okay, i think it’s caused by the ChronoTherm plugin.
pimatic-google-calendar | pimatic-wmi | pimatic-snmp | pimatic-wakeonlan |
Like my work? Then consider a donation
Follow me: www.thorstenreichelt.de
Hi everyone,
it seems that the problem got solved by itself. Don’t know what happened maybe through a reboot or whatever…
Cheers and thank you!!!