Created symlink /etc/systemd/system/multi-user.target.wants/vscpd.service → /lib /systemd/system/vscpd.service. Job for vscpd.service failed because the service did not take the steps required by its unit configuration. See "systemctl status vscpd.service" and "journalctl -xe" for details.
when installing the VSCP daemon the install program did not install the directory structure needed for the VSCP subsystem. The workaround is easy. Just run
sudo vscpd -s
and then terminate immediately and all should be alright. This will create the necessary folders. You need to issue
sudo systemctl start vscp
to start the VSCP daemon after doing this. As an alternative you can reboot.
A new version vscpd 14.0.5 Silicon of VSCP & Friends has been released. It’s available for download here. This release mainly fixes a resource allocation problem that appears on Raspberry Pi and similar devices. If you have experienced connection problems on this or other platforms you should upgrade. Full list of changes is on the release page.
How to turn off the lights at a specified time (either sunset + x hrs, or for example at YY:ZZ).
How to turn on at a certain time.
How to turn off at sunrise.
So the easiest way to demonstrate this capability of the VSCP daemon is to show the setup I have here in our house for this. Oh well part of it of course, we should not go to far away from the topic.
Yes I use VSCP based devices for some things here in the house but just as the shoemakers children have holes in there shoes I am often stuck at fixing things for others before I can do something for myself. So here it is a lot of my setups are test setups that are replaced by other test setups that are replaced by even other test setups etc in a never ending story. Its the just the way it is for makers I guess.
But some things I use here at least and that is I schedule the lamps in the house so they turn on at sunset and turn off at sunrise and some other things. So the questions above is easily by explaining my own setup.
Now I could have used a Paris module to control lamps and I actually do here in the office but just in a test setup . In our house and for lamps on the outside I use low cost wireless modules from Nexa and Proove
Well you all recognize them. Low cost single way communication modules working over 433 MHz. Reliable enough for lights IMO. But they could of course equally well have been Z-Wave, KNX, X10 or some other solution.
The CAN4VSCP Roma module will control these things and it sits on my desk at the moment working pretty well. It will be available in the store also one day I hope.
At the moment I us a Tellstick from Telldus AB to control lights connected this way. There are other similar products available and Arduino solutions that can do it as well
Well this solution just let me execute a binary on a Linux machine to turn on/off a group of lamps. There are similar devices available for all other vertical solutions. So to control KNX units with the VSCP daemon find an executable that can do that and the same for Z-Wave (OpenZwave) or whatever solution you want to integrate. Or write your own script or executable that does it. It is usually not a big deal.
But it of course does not end with an executable. The VSCP daemon can do many other things. Call an URL/send events/start timers etc etc. You can add anything and you should be able to add everything because the world consist and will consist of many different things,
Turn on lights at sunset
So lets look at the first point. This can be done in many ways of course but if you enter the coordinates for your location in the VSCP daemon configuration file (dm.xml) in the Automation section the decision matrix will be feed with two events that are of interest for this type of control
Sent when astronomical sunset-twilight happens at the location set by the coordinates. The definition of twilight is
Nautical twilight is the period when the center of the Sun is between 6 and 12 degrees below the horizon, when bright stars are still visible in clear weather and the horizon is becoming visible. It is too dark to do outdoor activities without additional lighting.
You have to enable the events also if they are disabled in the configuration file.
Restating the VSCP daemon with
and then opening
in your web browser (replacing 192.168.1.6 with your server ip) will show you the calculated times
We see that today when this is written the sunset is at 15:57 and the sunset twilight is at 16:44 two times one can use to turn on lights because it’s getting dark outside.
For indoor light I use sunset and for outdoor light I use twilight sunset for this. It all of course depends on how dark one want it to be before lights are turned on.
So setting this up in the web interface
Priority has flags set to zero so we don’t care about it.
Class is set to 20 which is CLASS1.INFORMATION and corresponding flags are set to 0xFFFF meaning all bits should be checked.
Type is set to 45 which is Sunset and corresponding flags are set to 0xFFFF meaning all bits should be checked.
GUID has mask all set to zero so we don’t check it.
On control we see that we don’t check index/zone/subzone but that we enable this row.
In the “when-section” we select when the action should happen. Her from the beginning of time to the the end of time and all weekdays and all times. As you see it is possible to have different schemas for different weekdays and for different time of year.
And then we have the action to perform. In my case I execute an external file and turn on lamps in section 1. But there are many actions to choose from and Send Event is one. Typically used in his case to send to a group of Paris modules to instruct them to switch some relays on.
You can have many rows that trigger on the same event and therefore easily mix technology and control KNX, Z-wave, VSCP and other alongside each other.
that is on several times ten second apart. A way to enter this without having a new DM row for each. This is possible on all fields in allowed time. So it is easy to do things at certain days of the month etc.
For the curious I did this so lights definitely will be turned off as I had some interference with the radio signal some times.
And then again we have the action which in this case turn off section 1 instead of on.
And yes turning on something at a certain time is just the same but with another action and also here one can send events or do other things.
Time time is a resource that is limited. When I did the DM of the VSCP daemon a long time ago an external nice and user friendly interface to edit it was planed. Not the web based interface that is available to day which is targeting a technical user. Actually editing is possible remotely also today so it is only the UX code missing. That will probably come in place one day. Giving this functionality the attention and usability it deserves.
An even more exciting feature that will come to this functionality, probably in the next release, is scripting right inside the VSCP daemon. That will make this an extremely cool cat.
Hopefully this gave some lights of the magic’s of the VSCP daemon DM.