Thermostat EXTRAS SETUP / STATE

[daleonov100]

Where I get an xml schema for thermostat extras? I'm interesting about valid object types and his attributes

[spike411]

I don't have any schema but I used the attached test thermostat + XML/code to test the various Extras types.
Unfortunately e.g. multiselect does not work and my notes have been lost with the old Control4 dealer forum.
I also remember the Weather Station (Weather Underground) driver used to use some picture/icon Extras type but that is no longer the case and it's not documented.

Maybe you will find it useful.

thermostat_test.zip
test_extras.txt
test_setup.txt
test_extras_setup_state.txt

[daleonov100]

Maybe you will find it useful.

Thanks!

[spike411]

I just checked that the old DriverWorks SDK OS 3.1.3 Proxy and Protocol Guide.chm had this section:
Understanding Extras

This seems to be missing from the online/GitHub version.

Although it had some formatting issues and wasn't 100% clear, it sure was useful.

[daleonov100]

Looks like the object type checkbox non-functional in ios control4 app.
This code works well on T* panels and android app, but not work on ios app.
Any clue? or this is known bug?

xml1 = [[<extras_setup>
    <extra>
        <section label="Extra parametes">
            <object type="checkbox" id="TH_EXTRAS1" label="Parameter1" command="extras" />
        </section>
    </extra>
</extras_setup>]]
C4:SendToProxy(DEFAULT_PROXY_BINDINGID, "EXTRAS_SETUP_CHANGED", { XML = xml1})

xml2 = [[<extras_state>
    <extra>
        <object id="TH_EXTRAS1" hidden="false" value="true" />
    </extra>
</extras_state>]]
C4:SendToProxy(DEFAULT_PROXY_BINDINGID, "EXTRAS_STATE_CHANGED", { XML = xml2})

[spike411]

I'm seeing the same! :/

BTW you have a typo in your XML: comand="extras" should be command="extras".

[daleonov100]

yes, I see typos, bad cut&paste :)

[daleonov100]

Interesting, what do I do to escalate this bug?

[spike411]

Seems like Control4 is more responsive on the dealer 'forum':
https://tech.control4.com/s/discussions

It seems to be an app-specific issue anyway, not really DriverWorks SDK issue.

[WWalshC4]

I've been watching this commentary - @spike411 is right that the best place to report non-Driverworks issues (like this one) is on the Control4 Tech Community.
For the documentation on Extras, I'll tag in @jmcgeeverC4 to see if that's something that we can add back into the P&P guide.