Questions about the release of v0.9

---

@n3ro Start with a clean Jessie image and make sure there is nodeJS installed (uninstalled in case).

@mwittig after hard debugging the most of it is working
DAMN systemd!

pimatic works. i have some errors in the log but the main functions are working

[pimatic] error: Invalid config of device "node24": Missing property "sensortype" in /attributes/0, Mi
ssing property "sensortype" in /attributes/1, Missing property "sensortype" in /attributes/2, Missing property "sen
sortype" in /attributes/3, Missing property "sensortype" in /attributes/4

Finally made the switch! Running Turnkeylinux 14.1 under ESXi with homeduino over a esp-link.

systemd init scripts to start pimatic at boot, with a dependency to start socat to establish the serial port link to the homeduino device. if the connection breaks or socat for whatever reason stops, systemd restarts both pimatic and socat automatically. (nice!).

Only issue during the upgrade was milight; had to remove and reinstall the plugin, and add libudev-dev library. Seems much faster on identical “hardware”; love the work that has been put into the new version so far; espeically the device config gui stuff.

Something went completely wrong following the instructions for updating from v0.8 to v0.9

I followed the instructions and my v0.8 build is still running though i stopped pimatic before.

that was the output for sudo service pimatic status

pi@raspberrypi:~ $ sudo service pimatic status
   pimatic.service - LSB: pimatic service
   Loaded: loaded (/etc/init.d/pimatic)
   Active: failed (Result: exit-code) since Fri 2016-11-25 11:49:04 CET; 9min ago
  Process: 14128 ExecStop=/etc/init.d/pimatic stop (code=exited, status=127)

Nov 25 00:49:40 raspberrypi pimatic[410]: Started.
Nov 25 00:49:40 raspberrypi systemd[1]: Started LSB: pimatic service.
Nov 25 11:49:04 raspberrypi systemd[1]: Stopping LSB: pimatic service...
Nov 25 11:49:04 raspberrypi pimatic[14128]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: not found
Nov 25 11:49:04 raspberrypi systemd[1]: pimatic.service: control process exited, code=exited status=127
Nov 25 11:49:04 raspberrypi systemd[1]: Stopped LSB: pimatic service.
Nov 25 11:49:04 raspberrypi systemd[1]: Unit pimatic.service entered failed state.
Nov 25 11:58:03 raspberrypi systemd[1]: Stopped LSB: pimatic service.

Any ideas on how to solve it?

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?

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?

the update server seems to be running fine.
but i will ask sweetpi for a reboot

@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

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?

@leader21 ahh okay, i think it’s caused by the ChronoTherm plugin.

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!!!