Author: admin

It is now possible to use tokens instead of numbers in events published topics from a driver and from the VSCP daemon itself. This is accomplished by using {{class-token}} and {{type-token}} instead off {{class}} / {{type}} so a topic for the above can look like

vscp/{{guid}}/{{class-token}}/{{type-token}}/{{nickname}}

Note that also {{nickname}} is set here to make it easy to filter on events from a specific node.

The current list of substitutions that can be used is

{{driver-name}} – Name of driver receiving ten event,
{{guid}} – Full GUID on standard form.
{{guid0}} – {{guid0}} – A specific GUID position.
{{guid.msb}} – MSB of GUID.
{{guid.lsb}} – LSB of GUID = nickname for can4vscp.
{{ifguid}} – GUID for interface the event is received on.
{{nickname}} – Nickname for node sendning event.
{{class}} – VSCP class
{{type}} – VSCP type.
{{class-token}} – VSCP class token.
{{type-token}} – VSCP type token.
{{head}} – VSCP event head.
{{obid}} – VSCP event obid.
{{timestamp}} – VSCP event timestamp.
{{dt}} – VSCP UTC datetime string.
{{year}} – VSCP event year.
{{month}} – VSCP event month.
{{day}} – VSCP event day.
{{hour}} – VSCP event hour.
{{minute}} – VSCP event minute.
{{second}} – VSCP event second.
{{clientid}} – Client id set for driver.
{{user}} – User set for driver.
{{host}} – Host set for driver.

There will probably be more added as we walk the path against a release.