CONFIG-EXAMPLE.txt 1.4 KB

123456789101112131415161718192021222324
  1. device config file example:
  2. "FAN_WZ": # device ID, must be unique in entire config file
  3. name: "Deckenventilator WZ" # pretty name
  4. "TX": # Transmit codes - not needed for InterTechno or EV1527 devices as calculated from RX codes for them
  5. "STOP": "is00F01DF0FD10" # each function name and code must be unique within the device
  6. "LOW": "is00F01DF0FDD0"
  7. "MED": "is00F01DF0FD0D"
  8. "HIGH": "is00F01DF0FDFD"
  9. "RX": # Receive codes
  10. "STOP": "i04E46C" # each function name and code must be unique within the device
  11. "LOW": "i04E468" # the function name is used as payload in cmdTopic, to send this command
  12. "MED": "i04E462"
  13. "HIGH": "i04E466"
  14. TX_interface: "UART" # force specific transmit interface, UART or MQTT
  15. statTopic: "T5/WZ/Deckenventilator/level" # output topic, when a RF code is received
  16. cmdTopic: "T5/WZ/Deckenventilator/set" # input topic, for sending RF codes
  17. add_statTopics_on: [ {"on_payload": "STOP", "topic": "T5/WZ/Deckenventilator/setTimer", "payload": "OFF"},
  18. {"on_payload": "LOW", "topic": "T5/WZ/Deckenventilator/setTimer", "payload": "1H"}
  19. ] # additional out topics on specific function, i.E. 1. on function "STOP" a payload "OFF" is sent on topic "T5/WZ/Deckenventilator/setTimer"
  20. add_statTopics: [ "test/123/bla", "test/234/blablu"] # list of additional out topics, where the original function name is sent as payload