W A R N I N G #VSCP #IoT

All drivers now have a common format

vscpl1drv-xxxxxxxxxxx

instead of

vscpl1-xxxxxxxxxxxdrv

Level II drivers are prefixed with

vscpl2-

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

State of #VSCP

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.

Cheers
Ake Hedman

IoT, M2M and VSCP talk from Grodans Paradis AB

%d bloggers like this: