If you are a brave person please test the new deb packages for the VSCP server. More of them will follow. Please note that this is not release code. They are for test only.
There are three files for each binary
vscpd_12.29.2-20_amd64.deb for 64-bit base machines
vscpd_12.29.2-20_i386.deb for 32-bit based machines
vscpd_12.29.2-20_armhf.deb for Raspberry Pi and the like
you find the files here under 12.29… Use wget for example to get them.
Installation process is
sudo dpkg -i vscpd_12.29.2_20…….
On a machine without wxWidgets installed it will complain about that, can be other dependencies also that fail. To fix that issue
sudo apt-get install -f
which will download and install the dependencies.
Remove the installed package with
sudo dpkg -r vscpd
Report problems on the VSCP list or on Github.
I will try to set up a package repository later. Expect problems. But it currently at least appears to works on the machines I have here.
All drivers now have a common format
Level II drivers are prefixed with
Also note that the default installation folder is changed to the driver folder (with sub folders level 1 and level2) of the installation tree under (default) /srv/vscp
Also note that ‘-‘ is used instead of ‘_’
Before updating to >= 12 remove drivers from /usr/local/lib
So finally we are getting closer to a #13, Aluminium. It’s been over a year now since the last release. A lot, and I mean a lot has gone into VSCP & Friends since then, actually to much to list it here. But it is a better software package now than before and it was pretty good at that time to if I may say it myself.
For users maybe the deb packages will be the most notable thing. There will be a Debian package for the vscp server, vscp works and for the helper lib. Also all of the drivers will have debian packages. But as drivers now are installed in the vscp folder structure (/srv/vscp/drivers/) they will be a bit special. This is a step against a web installable driver functionality I hope to have in place in the future.
Windows support for the VSCP server is now gone but it is possible to build and run it on a windows 10 machine in the bash mode. VSCP Works and the helper lib will be available as will the Level I (CANAL) drivers.If someone want to put down the work it should not be a big thing to get the VSCP server running on Windows either.
The last steps to work on before the release is here for those of you that are interested.
Last for you home automation freaks out there. Take a look at OpenHAB and Domoticz. One of them is probably what you are looking for, not VSCP & Friends, even if it to of course can be used for tasks like home control.
I’m the one taking the picture… 😉
About one year late with this upcoming release. But it will be worth the wait!
We today got a EUR 300 donation from VPNgids.nl to the project.
Vacation is over and VSCP development is up on speed again. The aim now is to bring everything up to a release stable state again. With all the new stuff added and new changes incorporated this is heavy work. So we work on to that goal. Just that
At the moment are some testing under-way for a changed webserver engine. The Civetweb server has been forked and ported and initial tests are good. The advantage here is a MIT license. We try to aim at MIT (or “mitlike”) everywhere if possible to make the system possible to be easily embedded in both commercial and non commercial projects..
Windows support is gone for the VSCP server. At least for the near future. It’s not worth the time it takes to keep it up and running. However the helper lib and VSCP works will still have Windows versions.
Debian install packages will be available for everything in the next release. The different parts will be separated so there will be several install packages. One for the server, one for works, one for each driver etc. That is no need for compiling the system any-more on most targets.
Well of to work… Have fun!
A typical example is in the script above where a CLASS1.CONTROL, Type=5, TurnOn event is sent to Zone=11, Subzone=3 every second.
As scripts can be stored in variables it is possible to remotely and dynamically change the content of the script and therefore also the outcome of the action.
Some custom VSCP functions is available and this list will of course be increased with socket communication and other. It i also possible to load external functionality from disc.
Today is the 17 birthday for VSCP. Persistence is seen as crazy if the outcome is bad but on the other hand heroic if the outcome is good. We all have to see how history will judge the VSCP project.
Anyway, the VSCP bumblebee is happy today and will get some cake.