I develop pimatic on an normal Ubuntu system (intel I7). So this isnt really a problem. It works a thousands times faster on an normal pc.
-
Pimatic on Standard PC instead of rPi
pimatic rocks!!!
-
For quick evaluation and testing, I successfully run it on a Windows 10 PC. Unfortunately I cannot remember how I installed it (long time ago) and as far as I know there is no Windows installer for it. Would be nice to have at least a how-to instruction for it.
-
I had no problems to install pimatic on a virtual debian8 (Hyper V).
The VM has only 50% of one core (old AMD Turion 2x2,2Ghz) but it’s so damn fast (compared to my current raspi1 pim host)So it works even on a virtualized host. It’s up to you if you run it on windows, linux, mac or even virtualized. (as the users here reported working)
Maybe someone could create a docker image for testing
-
@SLiX said:
Maybe someone could create a docker image for testing
This would be great!
I have a vagrant image which I mainly use for pinatic 0.9 testing. If any is interested in that I am happy to share it.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Would love to test that vagrant image! If you have some spare time, please post a link (you don’t need to hurry)!
-
im a little bit sad about to hear that devels test on high-performance hardware… maybe this is the reason for slowness on RPi?
-
The reason for slowness is the RPi itself ^^
I think not every dev want’s to buy an extra RPi just for developing.
-
well i cannot complain. pimatic on my pi2 is running at good speed and still has resources left.
compared to the pi B+ it’s a turtle/rabbit comparison imho.@demlak just imagine how a development takes place. you are writing your sources, maybe compile code and install additional programs for testing and so on. also testing the code again and again takes time. therefore a dev that is testing and developing on highspeed is working efficiently. if you ask me this is more than ok, as long as the result good
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
i understand… im not new to such things
but for me, i think developing near at target hardware should always be
-
yes you are right. developing on fast hardware and testing on the target should be the game.
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@SLiX said:
Would love to test that vagrant image! If you have some spare time, please post a link (you don’t need to hurry)!
Hi, here is a link to the vagrant image. It is a fork from baswenneker’s project (author of pimatic-ifttt) and I have spent some time to rewrite the provisioning script. My fork installs node 4.2 and pimatic from git using the v0.9.x branch. It also does the necessary autostart installation. If it is all done pimatic should be reachable at http://localhost:9999
Regarding the envisaged v0.9.x features there aren’t so many exciting things to see, currently. I guess most of the commits are still in sweetpi’s local repo. Actually, the branch is even a little bit outdated as it has been synced with development for a couple of week. The script can be easily changed to checkout development or master instead.
The provisioning script isn’t elegant - just plain bash. I didn’t have much time so far to look into the chef provisioner.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Got it now running for tests on my Desktop PC with Linux Mint Debian Edition. Works great. I will now add all my Wallplugs etc. and than transfer everything to the server i want to use.
-
Hello,
a bit old but still interesting…
Because of i will going to use a windows server, i already thought about using pimatic in windows.I found a working solution in you version here.
Just installed:
- Git-2.11.0-32-bit.exe
- rubyinstaller-2.3.3-x64.exe
- vagrant_1.9.1.msi
- VirtualBox-5.1.12-112440-Win.exe
and then followed the instructions @mwittig made in his git (https://github.com/mwittig/vagrant-pimatic-dev)
one issue was that he didn’t found rsync…
here you have to change one “word” in the following file:
C:\Users\username\.vagrant.d\boxes\debian-VAGRANTSLASH-jessie64\8.6.1\virtualbox\include\_Vagrantfile
here you have to change “rsync” to "virtualbox"
and then after a second reboot of the vm it was workingone issue still resists:
- how can i access the vm via ssh?
after
vagrant ssh
i get
ssh executable not found in any directories in the %PATH% variable. Is an SSH client installed? Try installing Cygwin, MinGW or Git, all of which
contain an SSH client. Or use your favorite SSH client with the following
authentication information shown below:
Host: 127.0.0.1
Port: 2222
Username: vagrant
Private key: C:/pimatic/vagrant-pimatic-dev/.vagrant/machines/default/virtualbox/private_key
`i will try again.
(ich werde es weiter versuchen)edit:
it works with puttygen.exe
just edit the load an existing private key file:
save and set in putty.exe the path to your saved file.here we go…
Mit freundlichen Grüßen
Chris -
I use an Intel NUC with Ubuntu 14.04. Works really smooth
-
I will use a:
HP Microserver- with Win Server 2016
- and ubuntu in VirtualBox
Just tried hyperv and it not working with USB-throughput…
How did you install node?
With apt?!Mit freundlichen Grüßen
Chris -
@chris
I’m using Windows Server 2012R2 with Homeduino USB attached directly to it.
Homeduino identifies as a COM port (COM5 on mine, yours will wary).The thing is, I determined Windows Node install to not work as well as I hoped, so I installed a VirtualBox on that said computer. VirtualBox forwards the COM port to virtual machine, and all works well. It does not eat resources much, so it shouldn’t be a problem. In addition, this way you get an easy way to backup your pimatic: copy paste the VM folder.
I have it set up so that when the computer starts, it launched VirtualBox Pimatic instance hidden (headless mode). So you don’t need to start it manually either.
To install, you can pretty much follow the guide found in https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions
And for Pimatic itself, start from the topic “Pimatic installation” https://pimatic.org/guide/getting-started/installation/ -
I am running a test system on Windows 10 which works very well with say 90% of the plugins. Obviously, there are some platform-specific plugin like pimatic-gpio which cannot be used on Windows. The biggest hurdle for some users may be that Visual Studio 2013 for C++ needs to be installed (the free edition will do) as some nodeJS package contain native code.
If it is useful for some users we can additional information to plugins on platform support.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I’d like to try and install Pimatic on Windows as well! I suppose pimatic-homeduino works?
How about cron (linux exclusive), or some other type of timing procedure?Supposedly all http request making plugins work. Though I’d settle with getting homeduino working first
-
@kitsunen said in Pimatic on Standard PC instead of rPi:
I suppose pimatic-homeduino works?
Homeduino should work, but I haven’t tried this so far with an Arduino board. I’ll give this a shot tomorrow with my test system in Windows. Cron should also work as it is 100% JS implementation of a Unix “Cron-alike” as far as I can see. It should be tested thoroughly on Windows which has not been done yet as far as I know. As you say any plugin basically doing http callouts should work.
An issue on winows you may run to is path length for filenames. To avoid this it is helpful to install pimatic with short path for the installation directory. This problem will disappear, once we have migrated pimatic to NPM3 or some other package manager which keeps package dependencies flat rather than building up deep directory trees for dependencies.
Generally, consider Windows support as “experimental”. You’ll be better of running on Linux, Mac OS X, or some other Unix derivate supported by NodeJS.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig Yeah, I might just go for another VirtualBox VM to do the reliable stuff …
Definitely trying this out on my developing PC though! Thanks for the input!By the way, I’ve been thinking for some time, is there some link to make donations for the project (I might not make much a difference, but I wanted to make some kind of gesture) ?