Done
-
pimatic@0.9.53
-
Hey Guys…
i dont if its Pimatic lasted update or Module but i see that everytime i start / restart Pimatic it will created a file in Root with 0bytes called “0”.
(i would upload a Pic of it but the Forum says i dont have permission to upload ?!? )
Someone knows for what this file is and why it will be created?
-
@mwittig Hi Marcus, been awhile. Just got back to Pimatic, although my time will be limited. I have submitted a pull on Github for Pimatic core to fix Log Messages not shown / disappearing #1131.
@OrTiN and others: until a new release is available this can be hacked by changing <pimatic-app>/node_modules/pimatic/lib/database.coffee:
line 122:
if meta?.timeStamp and meta.tags?
to:
if meta?.timestamp and meta.tags?
The uppercase S in timeStamp should be lowercase. After reboot all is well.
Kind regards,
Dan
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins -
Hey Dan, nice to see you back here!!!
-
Thanks @dan. With that change I see the messages now.
-
Yes, works well after reboot
Thanks! -
Same here!
-
@tehmilcho This doesn’t really help you, but I did a greenfield production install of 0.9.53 on a Pi 3 running Raspbian Buster fully patched. Can confirm your issue does not occur in my install.
Plugins loaded:
charts
cron
denon-avr
hap
homeduino
intergasincomfort
kodi
milight-reloaded
mobile-frontend
netcheck
ping
samsung-tv
shell-execute
sunrise
tradfri
upnp-root
– and some private add-ons not (yet) made available to the publicYou can cross these off your list.
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins -
@dan said in pimatic@0.9.53:
Hi Marcus, been awhile. Just got back to Pimatic, although my time will be limited. I have submitted a pull on Github for Pimatic core to fix Log
Hi Dan. Thanks for looking into this. Much appreciated and great to hear you’re back! I have merged your PR and will do a new release asap.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in pimatic@0.9.53:
Hi Dan. Thanks for looking into this. Much appreciated and great to hear you’re back! I have merged your PR and will do a new release asap.
Good to be back, and thanks for the merge!
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins -
Hello,
I freshly installed Pimatic@0.9.53 with Node.js version 10.16.3 and i am having trouble to install the pimatic-led-light plugin, here i think this is the important part of the ./pimatic-app/npm-debug.log:9516 verbose pkgid usb@1.1.1 9517 verbose cwd /home/pi/pimatic-app 9518 error Linux 4.19.75-v7+ 9519 error argv "/usr/local/bin/node" "/home/pi/pimatic-app/node_modules/pimatic/ppm.js" "install" "pimatic-led-light@0.9.5" "--unsafe-perm" 9520 error node v10.16.3 9521 error npm v2.15.12 9522 error code ELIFECYCLE 9523 error usb@1.1.1 install: `node-pre-gyp install --fallback-to-build` 9523 error Exit status 1 9524 error Failed at the usb@1.1.1 install script 'node-pre-gyp install --fallback-to-build'. 9524 error This is most likely a problem with the usb package, 9524 error not with npm itself. 9524 error Tell the author that this fails on your system: 9524 error node-pre-gyp install --fallback-to-build 9524 error You can get information on how to open an issue for this project with: 9524 error npm bugs usb 9524 error Or if that isn't available, you can get their info via: 9524 error 9524 error npm owner ls usb 9524 error There is likely additional logging output above. 9525 verbose exit [ 1, true ]
I am using an Raspi 3 B+ with Raspbian Buster. And yes, i already installed libudev-dev.
Need more information?Would be great if someone could help me!
-
i have the same problem. Maybe a bug?
-
usb@1.1.1 isnt compatible with node version > 9, see:
https://libupdate.com/libs/59810f94-5383-4948-9036-a81895621900how do we change the version of this lib to a newer?
-
@scobby Its not a bug. From your github issue I got:
23:23:48.223 [pimatic] Installing: "pimatic-telegram@1.1.14" from npm-registry. 23:23:52.767 [pimatic, ppm] WARN engine pimatic-telegram@1.1.14: wanted: {"node":">=8.0.0","npm":">1.1.x"} (current: {"node":"4.6.2","npm":"2.15.12"}) 23:23:53.751 [pimatic, ppm] WARN engine telegraf@3.34.1: wanted: {"node":">=8"} (current: {"node":"4.6.2","npm":"2.15.12"})
The error clearly states you are on node 4.6.2. Telegram 1.1.14 requires a higher node version. RTM: https://forum.pimatic.org/topic/4746/pimatic-telegram-1-1-14, and instructions on how to go back to 1.1.11.
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins -
@dan i am already behind the telegram bug, i switched to node v10.
Now i have the problem that blinkenstick (dependencie of pimatic-led-light) is not compatible with node > v9 because it has a dependencie of usb@1.1.1.
And usb@1.1.1 is not compatible with node =>9. -
@scobby as of today same for me, running on node 10.15 but led-light isn’t working anymore.
Can do without it since I mostly do webcalls to hyperion.