@bill-blacksoll said in Pimatic & Node 8.0:
@00lex
You can even go with Node v10.15.3 (LTS). You can read more about here
thank you.
@michbeck100
would you advise to go with v10.15.3 too?
Pimatic & Node 8.0
@bill-blacksoll said in Pimatic & Node 8.0:
@00lex
You can even go with Node v10.15.3 (LTS). You can read more about here
thank you.
@michbeck100
would you advise to go with v10.15.3 too?
@00lex I’m still on 4.x. But that’s just because I am too lazy to do the update. Just go for it and report back what happened.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
Okay i will report in 2 weeks. I want run both pi’s simultan and move step by step my stuff over.
@00lex said in Pimatic & Node 8.0:
I want to do a fresh install on Raspbian Buster
Note beyond, some plugins do not work with node v8/v10 (see earlier posts on this thread). Buster haven’t been tested yet either. If you don’t mind testing it though, please report back your findings
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
I did a complete installation of pimatic 0.9.48 on node 10.15.3 at the last weekend. It is running super!
I’m running Raspbian GNU/Linux 9 (stretch) on a Raspi 3B.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
don’t know. after my fail with v10, I try v4.9.1 and there was an error with some stuff.
I just read something need node >=6.
then I try successful v8 and after i retry v10.15.3 agian.
I notice with v8 and v10 I need to start piratic two times. second time to install sqlite.
with the first run I get many errors.
okay with v10.15.3 hap doesn’t work correct. I get for every device an error “hap is not property” and there is no “hap-database” bouild.
i will try now v8.9.4.
I’m slowly losing my motivation for pimatic. I use it for three years now and run from time to time over and over again into trouble. and that’s not a buster thing now. I don’t know how pimatic could be interesting for a beginner.
@00lex said in Pimatic & Node 8.0:
I’m slowly losing my motivation for pimatic. I use it for three years now and run from time to time over and over again into trouble.
I think you’re far too negative here which I find rather disappointing. Your are running on a new SBC which is on the market just a few days with a new OS version which has not yet 100% adapted to the hardware. Several reports like the Heise review already indicated that early adopters may expect issues in the first weeks as drivers support is immature.
I must also say that remarks like “there was an error with some stuff” and “many plugin do not work” or making “predictions” are not helpful at all to the community.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
youre right. its hot and I actually want to enjoy my free time. however v4.9.1 works as on my rpi3 @stretch on a rpi4@buster. im happy again
My RPI4 arrived today and I started a tested a quick test drive. Observations:
sudo apt update && sudo apt upgrade -y
). The upgrade contains various driver and kernel updates.Btw, Pimatic is running super-fast on RPI4. In particular, network and memory IO is a lot faster. Plugin installation is just a matter of seconds
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
what I learned in the past years is to make a backup before update pimatic. todays backup breaks my installation
root@home:~# service pimatic status
● pimatic.service - LSB: pimatic service
Loaded: loaded (/etc/init.d/pimatic; generated)
Active: failed (Result: exit-code) since Thu 2019-06-27 21:11:17 CEST; 48s ago
Docs: man:systemd-sysv-generator(8)
Process: 368 ExecStart=/etc/init.d/pimatic start (code=exited, status=1/FAILURE)
Jun 27 21:11:17 home pimatic[368]: at require (internal/module.js:12:17)
Jun 27 21:11:17 home pimatic[368]: at Object.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/pimatic.js:3:19)
Jun 27 21:11:17 home pimatic[368]: at Module._compile (module.js:409:26)
Jun 27 21:11:17 home pimatic[368]: at Object.Module._extensions…js (module.js:416:10)
Jun 27 21:11:17 home pimatic[368]: at Module.load (module.js:343:32)
Jun 27 21:11:17 home pimatic[368]: at Function.Module._load (module.js:300:12)
Jun 27 21:11:17 home pimatic[368]: at Function.Module.runMain (module.js:441:10)
Jun 27 21:11:17 home systemd[1]: pimatic.service: Control process exited, code=exited, status=1/FAILURE
Jun 27 21:11:17 home systemd[1]: pimatic.service: Failed with result ‘exit-code’.
Jun 27 21:11:17 home systemd[1]: Failed to start LSB: pimatic service.
before I recover my sd card, I try something.
backup pimatic-database.sqlite hap-database and config.json, delte pimatic-app, reinstall and copy files back. everything works and its the new version.
It would be great if we can chose between stable and testing for updates.
btw. do you installed hap on your rpi4? and which version of node v10 do you use?
@00lex said in Pimatic & Node 8.0:
service pimatic status
The error output of the service wrapper is always truncated to a few lines and in your case only contains an excerpt of a stack trace. Please check the pimatic-daemon.log and post the the full error message. Thanks
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@00lex said in Pimatic & Node 8.0:
btw. do you installed hap on your rpi4? and which version of node v10 do you use?
I don’t use hap and I am using node v10.16.0 which is in the current LTS version.
See also https://pimatic.teamemo.com/Guide/Getting-Started
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Hi, I would like also to jump in here.
Just installed also Buster on my 3B Test-Raspi. This happend more accidentially, as I took the noobs image with GNU/Linux 9 (stretch), which then seems to update, without confirming it, during the installation, to Buster, … however I’m definitely not an expert on this install-routines
I followed then again the Installation Wiki, which first worked fine, incl. a test start with a fresh config.json.
So directly installed node 10.16.0 and pimatic 0.9.49.
Also all additions have been installed (~10 min), exactly like the last time.
Did a test and pimatic runs and was also available via WEB frontend.
But at the point, where pimatic should have become globally, the problems seems to start:
The result from sudo npm link
looks as follows:
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated jayschema@0.3.2: this project is no longer maintained
npm WARN deprecated formatio@1.1.1: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated superagent@2.3.0: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released.
npm WARN deprecated samsam@1.1.2: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated coffee-script@1.11.1: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated samsam@1.1.3: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm ERR! code 128
npm ERR! Command failed: git clone --depth=1 -q -b master https://github.com/sweetpi/cassert.git /root/.npm/_cacache/tmp/git-clone-021bf075
npm ERR! fatal: Konnte führende Verzeichnisse von '/root/.npm/_cacache/tmp/git-clone-021bf075' nicht erstellen.: Keine Berechtigung
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-06-27T19_45_15_323Z-debug.log
Especially the ‘ERR!’ in the end definitely have not been shown in my installation last weekend (3B, Stretch, pimatic 0.9.48 on node 10.15.3).
The named log file in the last line, I couldn’t have a look at yet, as I’m not able to go by cd ./npm
into the directory, although I changed rights with sudo -s
. The answer is Datei oder Verzeichnis nicht gefunden
However, after the ERR messages I tried to start pimatic, but that doesn’t work.
Response on sudo pimatic.js start
is sudo: pimatic.js: Befehl nicht gefunden
I stop here for today I hope for some advise. It is not urgent, as it is my Test Raspi, but I was going to implement there the first time a ConBee II stic
Regards
Pedder
@pedder said in Pimatic & Node 8.0:
Especially the ‘ERR!’ in the end definitely have not been shown in my installation last weekend
Seems to be a permission problem. Try
cd ./node_modules/pimatic
sudo npm link --unsafe-perm
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law