@michbeck100 said in Trouble with fresh installation:
@jbs Did you use the test version of the frontend from ppm or the GitHub version?
The GitHub version:
Trouble with fresh installation
@michbeck100 said in Trouble with fresh installation:
@jbs Did you use the test version of the frontend from ppm or the GitHub version?
The GitHub version:
@jbs You might guess it: Try the npm version as described in my instructions. I have never tried to install the frontend from GitHub using ppm, so this might be the problem. As I can’t test from here, so i am just guessing.
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
@michbeck100 said in Trouble with fresh installation:
@jbs You might guess it: Try the npm version as described in my instructions. I have never tried to install the frontend from GitHub using ppm, so this might be the problem. As I can’t test from here, so i am just guessing.
Doesn’t fix the problem. Can not login with Chrome, Firefox, IE or Edge. But, I am able to login with my mobile using Chrome
Clean your cache for the side in chrome.
@ortin said in Trouble with fresh installation:
Clean your cache for the side in chrome.
Doesn’t fix the problem. As mentioned, also not working in Firefox, IE, Edge.
@jbs all those applications have debug consoles… What do they tell you?
@gleno0h said in Trouble with fresh installation:
@jbs all those applications have debug consoles… What do they tell you?
Firefox:
Firefox can not connect to the server at ws: //192.168.1.140: 8080 / socket.io /? EIO = 3 & transport = websocket & sid = 38CufEdU_4kwbWw0AAAa. socket.io.js: 3: 1012
The connection with ws: //192.168.1.140: 8080 / socket.io /? EIO = 3 & transport = websocket & sid = 38CufEdU_4kwbWw0AAA was interrupted while loading the page.
Chrome:
WebSocket connection to 'ws://192.168.1.140:8080/socket.io/?EIO=3&transport=websocket&sid=9srpXM3KeyO2fGT7AAAd' failed: WebSocket is closed before the connection is established.
hi there,
for me the same - new Rpi3B+, latest NOOB and Raspbian from scratch. I’ve tried to install 0.9.43 and it ended up with the same Warns and Errors. When i finally try to start it always ends with: Pidfile exists, but process is dead.
i’ve tried to install the 0.9.44-a as described here but all the same…
but why the hell the ‘stable’ version ends up like that???
Thanks
For all who still struggle with installing the test version, I’ve created a small script which basically follows my instructions. It installs to the directory pimatic-test
and it sets the pimatic password to admin
and the port to 8080
. I did test this on my Mac, but it should also work on your raspberry.
Please don’t forget to make it executable: chmod +x install-pimatic.sh
, before running.
#!/bin/sh
INSTALL_DIR=pimatic-test
PIMATIC_DIR=$INSTALL_DIR/node_modules/pimatic
mkdir ${INSTALL_DIR}
npm install pimatic-mobile-frontend@test --prefix ${INSTALL_DIR}
sed -i -e 's/"pimatic": "0\.9\.\*"//g' ${INSTALL_DIR}/node_modules/pimatic-mobile-frontend/package.json
npm install pimatic@test --prefix ${INSTALL_DIR} --production
sed -i -e 's/0\.9\.44-a/0.9.44/g' ${PIMATIC_DIR}/package.json
wget https://raw.githubusercontent.com/pimatic/pimatic/master/ppm.js
chmod +x ppm.js
mv ppm.js ${PIMATIC_DIR}/ppm.js
cp ${PIMATIC_DIR}/config_default.json ${INSTALL_DIR}/config.json
sed -i -e 's/"port": 80/"port": 8080/g' ${INSTALL_DIR}/config.json
sed -i -e 's/"password": ""/"password": "admin"/g' ${INSTALL_DIR}/config.json
After running you should be able to run pimatic with sudo node node_modules/pimatic/pimatic.js
as usual. If this works for you you can also use your own config.json. This script uses the default config.
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
@michbeck100 said in Trouble with fresh installation:
whew, this worked fine for me
Thank’s a lot helping me outta this
@jbs said in Trouble with fresh installation:
@michbeck100
Sorry, was messing the the version numbers in my previous post.
I am not sure from which directory I have to run the commands like$ rm -r node_modules $ npm install pimatic@test $ npm install pimatic-mobile-frontend@test
All from /pimatic-app?
Also a fresh install with this test version will not start: /usr/bin/env: ‘node\r’: not found.
The file is saved with dos newline rules.
Use:
dos2unix node_modules/pimatic/ppm.js
Also posted here https://forum.pimatic.org/topic/4501/pimatic-0-9-44a-test-results my working version (with some additional monules I needed):
cd ~
mkdir pimatic-test && cd pimatic-test
cp ../pimatic-app/config.json config.json
npm install pimatic-ping@0.9.5
npm install pimatic-sysinfo@0.9.4
npm install bluetooth-hci-socket
npm install pimatic-mobile-frontend@test
npm install pimatic@test
chmod 755 node_modules/pimatic/ppm.js
dos2unix node_modules/pimatic/ppm.js
sudo node node_modules/pimatic/pimatic.js
(still cant find how to get those black code boxes)
@dr_roelski said in Trouble with fresh installation:
still cant find how to get those black code boxes
see https://forum.pimatic.org/topic/1179/how-to-post-code-snippets-and-alike-on-the-forum
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law