mirror of
https://github.com/fhem/fhem-mirror.git
synced 2025-03-04 17:36:39 +00:00
00_MQTT2_SERVER.pm: add allowfrom attribute
git-svn-id: https://svn.fhem.de/fhem/trunk@25416 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
parent
e0db8a4ebc
commit
c3ce835930
@ -33,6 +33,7 @@ MQTT2_SERVER_Initialize($)
|
||||
no warnings 'qw';
|
||||
my @attrList = qw(
|
||||
SSL:0,1
|
||||
allowfrom
|
||||
autocreate:no,simple,complex
|
||||
clientId
|
||||
clientOrder
|
||||
@ -672,6 +673,22 @@ MQTT2_SERVER_ReadDebug($$)
|
||||
<b>Attributes</b>
|
||||
<ul>
|
||||
|
||||
<li><a href="#allowfrom">allowfrom</a>
|
||||
</li><br>
|
||||
|
||||
<a id="MQTT2_SERVER-attr-autocreate"></a>
|
||||
<li>autocreate [no|simple|complex]<br>
|
||||
MQTT2_DEVICES will be automatically created upon receiving an
|
||||
unknown message. Set this value to no to disable autocreating, the
|
||||
default is simple.<br>
|
||||
With simple the one-argument version of json2nameValue is added:
|
||||
json2nameValue($EVENT), with complex the full version:
|
||||
json2nameValue($EVENT, 'SENSOR_', $JSONMAP). Which one is better depends
|
||||
on the attached devices and on the personal taste, and it is only
|
||||
relevant for json payload. For non-json payload there is no difference
|
||||
between simple and complex.
|
||||
</li><br>
|
||||
|
||||
<a id="MQTT2_SERVER-attr-clientId"></a>
|
||||
<li>clientId <name><br>
|
||||
set the MQTT clientId for all connections, for setups with clients
|
||||
@ -741,19 +758,6 @@ MQTT2_SERVER_ReadDebug($$)
|
||||
also the SSL attribute.
|
||||
</li><br>
|
||||
|
||||
<a id="MQTT2_SERVER-attr-autocreate"></a>
|
||||
<li>autocreate [no|simple|complex]<br>
|
||||
MQTT2_DEVICES will be automatically created upon receiving an
|
||||
unknown message. Set this value to no to disable autocreating, the
|
||||
default is simple.<br>
|
||||
With simple the one-argument version of json2nameValue is added:
|
||||
json2nameValue($EVENT), with complex the full version:
|
||||
json2nameValue($EVENT, 'SENSOR_', $JSONMAP). Which one is better depends
|
||||
on the attached devices and on the personal taste, and it is only
|
||||
relevant for json payload. For non-json payload there is no difference
|
||||
between simple and complex.
|
||||
</li><br>
|
||||
|
||||
</ul>
|
||||
</ul>
|
||||
=end html
|
||||
|
Loading…
x
Reference in New Issue
Block a user