Added possibility to define the data type of Homematic

[p0l0]

Description:

The Homematic CCU needs that we send the correct XML-RPC Data Type for setValue, but parsing the yaml will always return a string.

This example request will be ignored by CCU:

<?xml version="1.0"?>
<methodCall>
	<methodName>setValue</methodName>
	<params>
		<param>
			<value><string>INT0000001:1</string></value>
		</param>
		<param>
			<value><string>ACTIVE_PROFILE</string></value>
		</param>
		<param>
			<value><string>2</string></value>
		</param>
	</params>
</methodCall>

the value should be a int:

<?xml version="1.0"?>
<methodCall>
	<methodName>setValue</methodName>
	<params>
		<param>
			<value><string>INT0000001:1</string></value>
		</param>
		<param>
			<value><string>ACTIVE_PROFILE</string></value>
		</param>
		<param>
			<value><int>2</int></value>
		</param>
	</params>
</methodCall>

Homematic component uses pyhomematic and pyhomematic uses xmlrpc.client.ServerProxy, an as stated under https://docs.python.org/3/library/xmlrpc.client.html#xmlrpc.client.ServerProxy, python data types are converted into the correct XML-RPC Type.

I added an optional value_type parameter where you are able to define the desired data type. Supported data types are (I just used the same naming as XML-RPC Types):

• boolean
• dateTime.iso8601
• double
• int
• string

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9513

Example entry for automation.yaml:

- alias: changeProfile
  trigger:
    - platform: time
      at: '00:00:05'
  action:
    - service: homematic.set_device_value
      data_template:
        address: 'INT0000001'
        channel: 1
        param: 'ACTIVE_PROFILE'
        interface: groups
        value_type: 'int'
        value: >
          {% if ((states('sensor.week_number')|default(0)|int) % 2) == 0 %}
          1
          {% else %}
          2
          {% endif %}

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[homeassistant]

Hi @p0l0,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[ghost]

Hey there @pvizeli, @danielperna84, mind taking a look at this pull request as its been labeled with a integration (homematic) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

[pvizeli]

Please add this to the library. Home Assistant consume data only

[pvizeli]

I see, that is for the service call.