mirror of
https://github.com/fhem/fhem-mirror.git
synced 2025-03-03 16:56:54 +00:00
HMCCU: Enhanced get channel command
git-svn-id: https://svn.fhem.de/fhem/trunk@10066 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
parent
44b9294cab
commit
b40854f2d8
@ -3,7 +3,7 @@
|
|||||||
*** HMCCU/HMCCUDEV - Modules for FHEM - Homematic CCU integration ***
|
*** HMCCU/HMCCUDEV - Modules for FHEM - Homematic CCU integration ***
|
||||||
=======================================================================
|
=======================================================================
|
||||||
|
|
||||||
* Document covers HMCCU/HMCCUDEV/HMCCUCHN version 2.0 (RPC server)
|
* Document covers HMCCU/HMCCUDEV/HMCCUCHN version 2.1 (RPC server)
|
||||||
* Please read carefully before using the modules.
|
* Please read carefully before using the modules.
|
||||||
* Last modified: 25.11.2015
|
* Last modified: 25.11.2015
|
||||||
|
|
||||||
@ -60,11 +60,14 @@ update of CCU readings in FHEM or use the external RPC server.
|
|||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
The module HMCCU no longer requires the XML-API CCU addon. The FHEM module requires
|
The module HMCCU no longer requires the XML-API CCU addon. The FHEM module requires
|
||||||
the packages LWP::UserAgent, Time::HiRes and File::Queue. The RPC server ccurpcd.pl
|
the packages LWP::UserAgent, Time::HiRes, RPC::XML::Client and RPCQueue.
|
||||||
requires the packages File::Queue, RPC::XML::Server, RPC::XML::Client, XML::Simple
|
The RPC server ccurpcd.pl requires the packages RPC::XML::Server, RPC::XML::Client,
|
||||||
and IO::Socket::INET.
|
RPCQueue and IO::Socket::INET.
|
||||||
All module files 88_HMCCU* and the RPC daemon ccurpcd.pl must be copied into the
|
All module files 88_HMCCU*, RPCQueue.pm and the RPC daemon ccurpcd.pl must be copied
|
||||||
folder FHEM under the FHEM installation directory.
|
into the folder FHEM under the FHEM installation directory.
|
||||||
|
|
||||||
|
NOTE: RPCQueue.pm is a bug fixed copy of File::Queue and part of the HMCCU installation
|
||||||
|
package. It's not available via CPAN!
|
||||||
|
|
||||||
|
|
||||||
====================================
|
====================================
|
||||||
@ -170,9 +173,9 @@ device states as "true" or "false" these values can be replaced by "open" or
|
|||||||
"closed" by setting "substitute" to "true:open,false:closed". The attribute
|
"closed" by setting "substitute" to "true:open,false:closed". The attribute
|
||||||
'substitute' is ignored if the same attribute is defined in a client device.
|
'substitute' is ignored if the same attribute is defined in a client device.
|
||||||
|
|
||||||
Get values of channel datapoints:
|
Get values of channel datapoints (supports multiple channels):
|
||||||
|
|
||||||
get <name> channel {<channel-name>|<channel-address>}[.<datapoint_exp>]
|
get <name> channel {<channel-name>|<channel-address>}[.<datapoint_exp>] [...]
|
||||||
|
|
||||||
Attention: There's no blank between channel and datapoint. If datapoint is
|
Attention: There's no blank between channel and datapoint. If datapoint is
|
||||||
not specified all datapoints will be read. The command accepts a regular
|
not specified all datapoints will be read. The command accepts a regular
|
||||||
@ -384,9 +387,9 @@ Get value of datapoint:
|
|||||||
|
|
||||||
If no datapoibt is specified all datapoints for specified channel are read.
|
If no datapoibt is specified all datapoints for specified channel are read.
|
||||||
|
|
||||||
Get multiple datapoints of channel:
|
Get multiple datapoints of channel (supports multiple channels):
|
||||||
|
|
||||||
get <name> channel <channel-number>[.<datapoint-expr>]
|
get <name> channel <channel-number>[.<datapoint-expr>] [...]
|
||||||
|
|
||||||
Parameter <datapoint-expr> is a regular expression. Default is .* (query all
|
Parameter <datapoint-expr> is a regular expression. Default is .* (query all
|
||||||
datapoints of a channel).
|
datapoints of a channel).
|
||||||
|
Loading…
x
Reference in New Issue
Block a user