Danfoss LC-13

[HansHofman]

Hi,

I use 24 Danfoss Thermostats
If I delete the Thermostat Clock it keeps coming back in the devices list.
Can this be made permanent and not keep coming back after a while.
I do not add or remove any nodes.
I do not use the Thermostat Clock I use json to set the correct temperature on event.

Here a snapshot from my devices.

Knipsel.JPG (83.17 KiB) Viewed 1060 times

Hans Hofman

[Egregius]

Yep, they keep coming back. I already have 111 unused devices upon 100 used.
I am also wondering how to avoid that.

[Egregius]

Another topic on the forum made me think...
I stopped domoticz and openen de Config/zwcfg_xxx.xml file.
I removed all the commandclasses I don't use.
For the Danfoss that was:

Code: Select all

<CommandClass id="70" name="COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE" version="1" request_flags="4" innif="true" change_counter="0">
    <Instance index="1" />
    <Value type="byte" genre="user" instance="1" index="1" label="Monday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="2" label="Tuesday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="3" label="Wednesday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="4" label="Thursday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="5" label="Friday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="6" label="Saturday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="byte" genre="user" instance="1" index="7" label="Sunday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
    <Value type="list" genre="user" instance="1" index="8" label="Override State" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
        <Item label="None" value="0" />
        <Item label="Temporary" value="1" />
        <Item label="Permanent" value="2" />
    </Value>
    <Value type="byte" genre="user" instance="1" index="9" label="Override Setback" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="127" />
</CommandClass>
<CommandClass id="129" name="COMMAND_CLASS_CLOCK" version="1" request_flags="4" innif="true">
    <Instance index="1" />
    <Value type="list" genre="user" instance="1" index="0" label="Day" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
        <Item label="Monday" value="1" />
        <Item label="Tuesday" value="2" />
        <Item label="Wednesday" value="3" />
        <Item label="Thursday" value="4" />
        <Item label="Friday" value="5" />
        <Item label="Saturday" value="6" />
        <Item label="Sunday" value="7" />
    </Value>
    <Value type="byte" genre="user" instance="1" index="1" label="Hour" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="21" />
    <Value type="byte" genre="user" instance="1" index="2" label="Minute" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="57" />
</CommandClass>

This instantly gives the advantage that no errors are shown when starting Zwave about the unsupported schedule class.
Will see in a few hours/days if there's no downside to this.