@tpointandrew
good to hear!
-
Some problems with homeduino
-
oh no… not correct. i forget to start with sudo pimatic.js
pi@raspberrypi ~ $ sudo service pimatic stop
Not running.
pi@raspberrypi ~ $ sudo service pimatic status
Not running.
pi@raspberrypi ~ $ sudo service pimatic.js
pimatic.js: unrecognized service
pi@raspberrypi ~ $ sudo pimatic.js
20:07:05.501 2015-04-16 Thursday
20:07:12.363 [pimatic] Starting pimatic version 0.8.66
20:07:14.547 [pimatic] Startup error: Error: SQLITE_BUSY: database is locked
20:07:14.557 [pimatic] exiting…
pi@raspberrypi ~ $ sudo service pimatic stop
Not running.
pi@raspberrypi ~ $ -
@tpointandrew
and if you runsudo fuser /home/pi/pimatic-app/pimatic-database.sqlite
now, what is the precessnumber that is using the database?
-
But with:
sudo fuser /home/pi/pimatic-app/pimatic-database.sqlite
i get the PID and with:
sudo kill 2287
I can kill the process. After this i can finally start again with sudo pimatic.js
Thank you very much. 1 problem is solved now
The reason why I have to reboot so many times is because my pimatic will not restart it self because get the message:
Can not restart self, when not daemonized. Please run pimatic with: “node /home/pi/pimatic-app/node_modules/pimatic/pimatic.js start” to use this feature.
But I cannot start with node /home/pi/pimatic-app/node_modules/pimatic/pimatic.js start
got this:
pi@raspberrypi ~ $ node /home/pi/pimatic-app/node_modules/pimatic/pimatic.js start
Started.But I the Website of Pimatic says “ops no connection”
Only with “sudo service pimatic.js” it is possible for me.
-
-
@wimpie said:
sudo service pimatic start
Because there is not this here:
0:11:17.026 2015-04-16 Thursday
20:11:23.599 [pimatic] Starting pimatic version 0.8.66
20:11:25.071 [pimatic] Loading plugin: “pimatic-cron” (0.8.5)
20:11:25.908 [pimatic] Loading plugin: “pimatic-homeduino” (0.8.50)
20:11:27.245 [pimatic] Loading plugin: “pimatic-mobile-frontend” (0.8.62)
20:11:28.541 [pimatic-cron] the time is: Thu Apr 16 2015 20:11:28 GMT+0000 (UTC)
20:11:28.962 [pimatic] New device “Brenner”…
20:11:29.210 [pimatic-mobile-frontend] packing static assets
20:11:30.085 [pimatic-mobile-frontend] packing static assets finished
20:11:30.098 [pimatic-mobile-frontend] rendering html
20:11:36.958 [pimatic-mobile-frontend] rendering html finished
20:11:37.011 [pimatic] Listening for HTTP-request on port 80…
20:11:37.045 [pimatic-homeduino] data: "ready"
20:11:37.051 [pimatic-homeduino] data: "PING"
20:11:37.058 [pimatic-homeduino] Connected to homeduino device.
20:11:37.077 [pimatic-homeduino] data: "ACK"
20:11:37.082 [pimatic-homeduino] Receiving on pin 0Thougt this is import 4 running pimatic and see the debug message only with this “boot sequence”
-
@tpointandrew
followed these steps?
http://pimatic.org/guide/getting-started/autostarting/ -
sorry but i cannot follow you anymore seems you are mixing things up.
you can only stop the service if it IS a service / daemon.
if you are starting pimatic manually withsudo pimatic.js
it is not started as service and not daemonised. pimatic is then running directliy from the commandline, not in background.your above debug output can be seen at the messages at the gui.
therefore no need to start pimatic manually at the gui imho …pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@tpointandrew
@leader21 is right. If pimatic autostarts, then there is no reason to manually start it again (unless you’ve killed the precess of course). It is already running, so the database is locked.If you try to start another instance of pimatic, it will result in the databse-locked error you were getting.
-
thx for explanation
But what could the reason why I cant receive debug for my codes which I send with my remote everytime? Think only 1 time of 100 starts
-
maybe a hardware issue.
what receiver do you use? do you have a picture of it or your installation?
there are big differences at hardware!!
the recommended receiver is the RXB6 also known as 3400RF
and how far are you away with your remote from the receiver?
the “crappy ones” can receive within a range of maybe 50cm. hold your remote closer to the receiver and press your buttons. maybe you will have a better result then.furthermore there’s mostly a possibility to solder an antenna to the receiver and sender.
you can try to solder a 17.5 cm straight copper wire to it or if you are using a bread board put the wire into the hole/line for the antenna pin on the bread board.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
I will make some picture from the installation tomorrow. No good Cam here at the moment.
Sender & receiver pictures of amazon
-
ok i see - as i thought. the receiver is not good!
what you can do is what i said above - move very close to the receiver and press your buttons on the remote and solder a copper wire to the ant pinpimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
What is the USB serial chip on the nano? If it’s the ftdi version it stops receiving after some minutes. You will need the ch340 version. Best source is eBay for about 6€ inkl. Versand. You only must solder the connectors to the pub.
-
good point klaus!
could be an issue too.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@tpointandrew
are you that pimatic is the problem? Maybe your arduino or receiver is defected, or maybe your remote control? -
Thx for all the tipps. After the Info about the arduino nano i have switched to the gpio setup with homeduino and everything works fine at the moment.
my cpu is at max 10% with a lot of running plugins, but I will order the right nano stick these days
The signal is absolutly okay without the nano.
-
Please keep us informed!
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@tpointandrew I had some problems with receiving using the same receiver. I’m not sure why, but it made a big difference to connect a ground between the nano and the RPI.