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.
My hope was to have a LTS release ready before the summer but I never reached that point. But things are what they are. There are mainly two reasons for the delay. First I don’t want to rush some big changes in the core structure that force me to do incompatible updates later with code needed for update paths. This mostly relate to the database. Next I want to move as much of the code as possible to MIT licensed which means I have to remove and rewrite some stuff. Hopefully something will be available soon after the summer.
The multicast channel support is now fully implemented. This means one can set up groups on the VSCP multichannel group that act as subnets using a specific port. AES128/AES192/AES256 encryption is available. The multicast announce is also fully in place now. Python and c/c++ samples available.
A new UDP interface has been implemented. Also here are AES128/AES192 and AES256 encryption available. Python and c/c++ samples available.
Support classes for encryption and frame packaging has been added to the vscphelper lib to make it easier to handle this new functionality.
pyvscp is a pip installable Python module that add VSCP functionality to Python. The main interfaces is in place but more will come and also more documentation. It’s very easy to interface the VSCP server and VSCP with this module. I personally love it.
The libvscphelper library is now packaged as a deb as the first component that will be available on this form. It is needed to be installed to use most of the functionality of pyvscp. VSCP Works and the vscp server till also be packed in their own deb’s for easy installation.
node.js bindings installable with npm is next and I know there is c# bindings brewing also. Probably have to dig into Java soon also if someone does not volunteer for that job.
A lot of other this to have hap-end of course.
Now I will go on a four-week leave. I am not used to that long vacations and right now I don’t actually know how to survive such a long time without coding. But I have promised my wife to try to to be honest I probably need it. I will check mail occasionally though but wil probably not answer mails on a daily basis.
For those of you running head code of the VSCP & Friends package
Remember to build the full VSCP & Friends package after checking it out from git and then compile all files and do a “make install” as root. If you don’t do this drivers and the VSCP server (the daemon) may use different package formats which will corrupt memory and probably make the VSCP server and the rest of the code unstable.
From version 220.127.116.11 Magnesium the configuration file format has changed. A lot of things have moved out from the <general> section up to the top-level. Refer to the distribution vscpd.conf for full info.
Configuration file reading order has changed as well. Now things work as the following
Read the <general> tag information from the XML configuration.
Read configuration from the database.
Read the full XML configuration.
This change makes it easier to have a safe setting in the XML configuration file that can’t be overwritten by changes in the database. The importance of this will be more clear when settings can be changed in the administrative web interface.
REMEMBER TO DELETE DATABASE FILES AFTER A NEW BUILD.
ps There is a lot of bumblebees here on the VSCP hill right now, more than ever before. Must be a sign… 😉 ds