![\"Screenshot](\"https:\/\/i0.wp.com\/grodansparadis.com\/wordpress\/wp-content\/uploads\/2016\/02\/Screenshot-from-2016-02-14-220026.png?resize=580%2C801\")
<\/a><\/h2>\n<\/h2>\nMake measurement event come out as a plain number over the MQTT channel.<\/h3>\n
Sometimes, and especially if your device is a low end device, it can be nice to publish measurement events from the VSCP daemon to it as plain numbers. You can do this with the simplify<\/strong> feature.<\/p>\nFirst look at the driver\u00a0 entry in \/etc\/vscp\/dm.xml<\/strong><\/p>\n<!– Level II MQTT driver –><\/em><\/strong>
\n <driver enable=”true” ><\/em><\/strong>
\n\u00a0\u00a0\u00a0\u00a0 <name>MQTT2<\/name><\/em><\/strong>
\n\u00a0\u00a0\u00a0\u00a0 <path>\/usr\/local\/lib\/vscpl2drv_mqtt.so<\/path><\/em><\/strong>
\n\u00a0\u00a0\u00a0 <config>session2;publish;vscp-pub;192.168.1.9:1883<\/em><\/strong>
\n\u00a0\u00a0\u00a0 <guid>00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<\/guid><\/em><\/strong>
\n <\/driver><\/em><\/strong><\/p>\nWe see that this driver defines\u00a0 a publishing MQTT channel with<\/p>\n
\n- topic<\/strong> = vscp_pub<\/em><\/li>\n
- session id<\/strong> = session2<\/em><\/li>\n
- broker is at\u00a0 address<\/strong> = 192.168.1.9<\/em><\/li>\n
- broker use standard MQTT port\u00a0<\/strong> = 1823<\/em><\/li>\n<\/ul>\n
Nothing strange here. Normally VSCP events would be available if you subscribe to the topic vscp_pub on this broker. On the console typically like<\/p>\n
mosquitto_sub -h 192.168.1.9 -v -t ‘vscp-pub’<\/strong><\/p>\nThis is just the same as we described above. But now lets define a simplify variable like (\/srv\/vscp\/variables.xml or in the web interface of the VSCP daemon).<\/p>\n
<variable type=”string”><\/strong><\/em>
\n\u00a0\u00a0\u00a0\u00a0 <name>MQTT2_SIMPLIFY<\/name><\/strong><\/em>
\n\u00a0\u00a0\u00a0\u00a0 <note>Feed temperature measurements to “the thing”<\/note><\/strong><\/em>
\n\u00a0\u00a0\u00a0\u00a0 <value>1040,6,0,1,0,0<\/value><\/strong><\/em>
\n <\/variable><\/strong><\/em><\/p>\nWhen the MQTT driver loads it looks fore variables named like it’s name + “-” + keyword and configure itself from the variables. This configuration actually overrides the configuration done in the diver configuration string.<\/p>\n
It also add extra configuration possibilities and SIMPLIFY is on of them so<\/p>\n
MQTT2_SIMPLIFY<\/strong><\/em><\/p>\nis a variable with name “SIMPLIFY” that is destined for the driver with name “MQTT2”.<\/p>\n
The content of\u00a0 a simplify variable specify the event we want to send on the MQTT channel as a plain number.\u00a0 In our case we have<\/p>\n
1040,6,0,1,0,0<\/strong><\/em><\/p>\nwhich boils down to<\/p>\n
\n- 1040<\/strong> – This is the VSCP class<\/strong>. In this case CLASS2.MEASUREMENT_STR<\/a><\/li>\n
- 6<\/strong> – This is the VSCP Type and six is “temperature”.<\/li>\n
- 0<\/strong> – This is the sensor index<\/strong>. Only events with this sensor index will be published.<\/li>\n
- 0<\/strong>\u00a0 – This is the zone<\/strong>. Only events with this vallue will be published.<\/li>\n
- 0<\/strong>\u00a0 – This is the sub zone<\/strong>. Only events with this value will be published.<\/li>\n
- 0 – This is the unit<\/strong>. Only events with this value will be published.<\/li>\n<\/ol>\n
You can use CLASS1_MEASUREMENT<\/a> and CLASS2_MEASUREMENT_FLOAT<\/a> also if you which for this functionality and the format for them are here<\/a>.<\/p>\nSo now when you restart the VSCP daemon CLASS2.MEASUREMENT_STR<\/a> events will come out as plain numbers on the MQTT channel. We can test this in the TCP\/IP interface by sending<\/p>\nsend 0,1040,6,0,0,-,0,0,0,1,0×35,0x35,0x35,0x2e,0x30,0x32<\/em><\/strong><\/p>\nwhich will come out as<\/p>\n
vscp-pub 555.02<\/strong><\/em><\/p>\nif you subscribed using mosquitto_sub -h 192.168.1.9 -v -t ‘vscp-pub’<\/em><\/p>\nSend plain numbers over a MQTT channel and have them automatically translated into proper VSCP events.<\/h2>\n
You may just want to send plain numbers instead of a full VSCP event to the VSCP framework.\u00a0 Typically this can be some stupid device that just is capable of sending out plain numbers. The simplicity mode can make these kind of devices a bit more useful also. YES you want at least the unt of your measurement to come along with your data in a standardized way.<\/p>\n
To use this feature we us the first driver entry we specified<\/p>\n
<!– Level II MQTT Driver –><\/strong><\/em>
\n\u00a0\u00a0\u00a0 <driver enable=”true” >\u00a0 <\/strong><\/em>
\n\u00a0\u00a0\u00a0 <name>MQTT1<\/name><\/strong><\/em>
\n\u00a0\u00a0\u00a0 <path>\/usr\/local\/lib\/vscpl2drv_mqtt.so<\/path><\/strong><\/em>
\n\u00a0\u00a0\u00a0 <config>session1;subscribe;vscp-sub;192.168.1.9:1883<\/strong><\/em>
\n\u00a0\u00a0\u00a0 <guid>00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<\/guid><\/strong><\/em>
\n <\/driver><\/strong><\/em><\/p>\nHere we subscribe to a MQTT channel vscp_sub on the broker located at 192.168.1.9 on port 1883. We name the session “session1”.\u00a0 Remember that all drivers MUST have a unique session name.<\/p>\n
So things publishe form other devices on topic vscp_sub will be received by the driver and normally this is VSCP events on the standard string form<\/p>\n
send head,class,type,obid,time-stamp,GUID,data1,data2,data3…<\/strong><\/em><\/p>\nyou can read mode here about this format<\/a> used n the TCP\/IP interface of the VSCP daemon among other places.<\/p>\nBut now we want to send just a number and get a VSCP events. So for this we use the simplify feature again.<\/p>\n
We start out just as above by specifying the SIMPLIFY variable.\u00a0 As you see we now referee to the first driver entry MQTT1<\/p>\n
<variable type=”string”><\/strong><\/em>
\n\u00a0\u00a0 <name>MQTT1_SIMPLIFY<\/name><\/strong><\/em>
\n\u00a0\u00a0 <note>Allow for sending plain numbers <\/note><\/strong><\/em>
\n\u00a0\u00a0 <value>1060,6,0,1,0,0<\/value><\/strong><\/em>
\n <\/variable><\/strong><\/em><\/p>\nOnly 1060 is different than above, We could have used 1040 here alos to get CLASS2.MEASUREMENT_STR<\/a> event but to be not to repetitive we use CLASS2.MEASUREMENT_FLOAT<\/a> for this example.<\/p>\nAnd using VSCP Works to check the incoming event gives the expected result<\/p>\n
![\"Screenshot](\"https:\/\/i0.wp.com\/grodansparadis.com\/wordpress\/wp-content\/uploads\/2016\/02\/Screenshot-from-2016-02-14-223204.png?resize=580%2C239\")
<\/a><\/p>\n <\/p>\n
If we set\u00a0 CLASS2.MEASUREMENT_STR<\/a> (1040) instead we got the same end result<\/p>\n![\"Screenshot](\"https:\/\/i0.wp.com\/grodansparadis.com\/wordpress\/wp-content\/uploads\/2016\/02\/Screenshot-from-2016-02-14-223204-1.png?resize=580%2C239\")
<\/a><\/p>\nAnd you can use one of the other measurement types also of course. Read the docs.<\/p>\n
Make measurement event come out as a plain number over the MQTT channel.<\/h3>\n
First look at the driver\u00a0 entry in \/etc\/vscp\/dm.xml<\/strong><\/p>\n <!– Level II MQTT driver –><\/em><\/strong> We see that this driver defines\u00a0 a publishing MQTT channel with<\/p>\n Nothing strange here. Normally VSCP events would be available if you subscribe to the topic vscp_pub on this broker. On the console typically like<\/p>\n mosquitto_sub -h 192.168.1.9 -v -t ‘vscp-pub’<\/strong><\/p>\n This is just the same as we described above. But now lets define a simplify variable like (\/srv\/vscp\/variables.xml or in the web interface of the VSCP daemon).<\/p>\n <variable type=”string”><\/strong><\/em> When the MQTT driver loads it looks fore variables named like it’s name + “-” + keyword and configure itself from the variables. This configuration actually overrides the configuration done in the diver configuration string.<\/p>\n It also add extra configuration possibilities and SIMPLIFY is on of them so<\/p>\n MQTT2_SIMPLIFY<\/strong><\/em><\/p>\n is a variable with name “SIMPLIFY” that is destined for the driver with name “MQTT2”.<\/p>\n The content of\u00a0 a simplify variable specify the event we want to send on the MQTT channel as a plain number.\u00a0 In our case we have<\/p>\n 1040,6,0,1,0,0<\/strong><\/em><\/p>\n which boils down to<\/p>\n You can use CLASS1_MEASUREMENT<\/a> and CLASS2_MEASUREMENT_FLOAT<\/a> also if you which for this functionality and the format for them are here<\/a>.<\/p>\n So now when you restart the VSCP daemon CLASS2.MEASUREMENT_STR<\/a> events will come out as plain numbers on the MQTT channel. We can test this in the TCP\/IP interface by sending<\/p>\n send 0,1040,6,0,0,-,0,0,0,1,0×35,0x35,0x35,0x2e,0x30,0x32<\/em><\/strong><\/p>\n which will come out as<\/p>\n vscp-pub 555.02<\/strong><\/em><\/p>\n if you subscribed using mosquitto_sub -h 192.168.1.9 -v -t ‘vscp-pub’<\/em><\/p>\n You may just want to send plain numbers instead of a full VSCP event to the VSCP framework.\u00a0 Typically this can be some stupid device that just is capable of sending out plain numbers. The simplicity mode can make these kind of devices a bit more useful also. YES you want at least the unt of your measurement to come along with your data in a standardized way.<\/p>\n To use this feature we us the first driver entry we specified<\/p>\n <!– Level II MQTT Driver –><\/strong><\/em> Here we subscribe to a MQTT channel vscp_sub on the broker located at 192.168.1.9 on port 1883. We name the session “session1”.\u00a0 Remember that all drivers MUST have a unique session name.<\/p>\n So things publishe form other devices on topic vscp_sub will be received by the driver and normally this is VSCP events on the standard string form<\/p>\n send head,class,type,obid,time-stamp,GUID,data1,data2,data3…<\/strong><\/em><\/p>\n you can read mode here about this format<\/a> used n the TCP\/IP interface of the VSCP daemon among other places.<\/p>\n But now we want to send just a number and get a VSCP events. So for this we use the simplify feature again.<\/p>\n We start out just as above by specifying the SIMPLIFY variable.\u00a0 As you see we now referee to the first driver entry MQTT1<\/p>\n <variable type=”string”><\/strong><\/em> Only 1060 is different than above, We could have used 1040 here alos to get CLASS2.MEASUREMENT_STR<\/a> event but to be not to repetitive we use CLASS2.MEASUREMENT_FLOAT<\/a> for this example.<\/p>\n And using VSCP Works to check the incoming event gives the expected result<\/p>\n <\/p>\n If we set\u00a0 CLASS2.MEASUREMENT_STR<\/a> (1040) instead we got the same end result<\/p>\n And you can use one of the other measurement types also of course. Read the docs.<\/p>\n
\n <driver enable=”true” ><\/em><\/strong>
\n\u00a0\u00a0\u00a0\u00a0 <name>MQTT2<\/name><\/em><\/strong>
\n\u00a0\u00a0\u00a0\u00a0 <path>\/usr\/local\/lib\/vscpl2drv_mqtt.so<\/path><\/em><\/strong>
\n\u00a0\u00a0\u00a0 <config>session2;publish;vscp-pub;192.168.1.9:1883<\/em><\/strong>
\n\u00a0\u00a0\u00a0 <guid>00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<\/guid><\/em><\/strong>
\n <\/driver><\/em><\/strong><\/p>\n\n
\n\u00a0\u00a0\u00a0\u00a0 <name>MQTT2_SIMPLIFY<\/name><\/strong><\/em>
\n\u00a0\u00a0\u00a0\u00a0 <note>Feed temperature measurements to “the thing”<\/note><\/strong><\/em>
\n\u00a0\u00a0\u00a0\u00a0 <value>1040,6,0,1,0,0<\/value><\/strong><\/em>
\n <\/variable><\/strong><\/em><\/p>\n\n
Send plain numbers over a MQTT channel and have them automatically translated into proper VSCP events.<\/h2>\n
\n\u00a0\u00a0\u00a0 <driver enable=”true” >\u00a0 <\/strong><\/em>
\n\u00a0\u00a0\u00a0 <name>MQTT1<\/name><\/strong><\/em>
\n\u00a0\u00a0\u00a0 <path>\/usr\/local\/lib\/vscpl2drv_mqtt.so<\/path><\/strong><\/em>
\n\u00a0\u00a0\u00a0 <config>session1;subscribe;vscp-sub;192.168.1.9:1883<\/strong><\/em>
\n\u00a0\u00a0\u00a0 <guid>00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<\/guid><\/strong><\/em>
\n <\/driver><\/strong><\/em><\/p>\n
\n\u00a0\u00a0 <name>MQTT1_SIMPLIFY<\/name><\/strong><\/em>
\n\u00a0\u00a0 <note>Allow for sending plain numbers <\/note><\/strong><\/em>
\n\u00a0\u00a0 <value>1060,6,0,1,0,0<\/value><\/strong><\/em>
\n <\/variable><\/strong><\/em><\/p>\n<\/a><\/p>\n<\/a><\/p>\n