The Connect API documentation (v1.0.1) only documents 6 functionalChannelType values:
DEVICE_BASE
DEVICE_SABOTAGE
DIMMER_CHANNEL
SHUTTER_CONTACT_CHANNEL
ALARM_SIREN_CHANNEL
ACCESS_CONTROLLER_CHANNEL
However, real devices expose channel types that are entirely undocumented. Example from a live getSystemState response:
"functionalChannels": {
"0": { "functionalChannelType": "DEVICE_OPERATIONLOCK" },
"1": { "functionalChannelType": "DOOR_LOCK_CHANNEL", "lockState": "LOCKED" }
}
Additionally, there is no dedicated reference section for functionalChannelType at all. The 6 known types only appear incidentally within JSON examples (e.g. getSystemState, DEVICE_CHANGED). A complete, searchable reference is entirely missing.
Impact
Without a complete reference of all functionalChannelType values and their respective:
- state properties (e.g. lockState, windowState, dimLevel)
- associated control endpoints (e.g. which path to use for which channel type)
...it is impossible to implement generic device control via the plugin API without reverse engineering live device responses.
Request
Please provide a complete reference table covering all functionalChannelType values, including:
- Their state properties and data types
- The associated
/hmip/device/control/* endpoints
- The required request body parameters per endpoint
- A dedicated, searchable section in the documentation (not embedded in examples)
The Connect API documentation (
v1.0.1) only documents 6 functionalChannelType values:DEVICE_BASEDEVICE_SABOTAGEDIMMER_CHANNELSHUTTER_CONTACT_CHANNELALARM_SIREN_CHANNELACCESS_CONTROLLER_CHANNELHowever, real devices expose channel types that are entirely undocumented. Example from a live
getSystemStateresponse:Additionally, there is no dedicated reference section for
functionalChannelTypeat all. The 6 known types only appear incidentally within JSON examples (e.g.getSystemState,DEVICE_CHANGED). A complete, searchable reference is entirely missing.Impact
Without a complete reference of all
functionalChannelTypevalues and their respective:...it is impossible to implement generic device control via the plugin API without reverse engineering live device responses.
Request
Please provide a complete reference table covering all
functionalChannelTypevalues, including:/hmip/device/control/*endpoints