v0.5.1

[0.5.1] - 2024-12-18

Added

• Text over TCP: Added support for C++ and hex style control characters to e.g. add a new line, tab or a carriage return
  • C++ style characters can be escaped with a single additional backslash (e.g. \\n)
  • Hex style characters can be escaped with "0\\\" (e.g. 0\\\0x09)

Full Changelog: v0.5.0...v0.5.1

v0.5.0

[0.5.0] - 2024-12-15

Added

• Added text over TCP entity. This protocol is used by some home automation systems, IoT devices or tools like win-remote-control
  • Example: 192.168.1.1:1234, "Hello World"
• Option to change the default http requests user agent in the advanced setup settings

Full Changelog: v0.4.0...v0.5.0

v0.4.0

[0.4.0] - 2024-11-07

Added

• Send wake-on-lan magic packets to multiple addresses by separating them with a comma
• Support for all parameters from pywakeonlan (interface, port, ip_address)
  • Example: XX:XX:XX:XX:XX:XX,interface=192.168.1.101

Full Changelog: v0.3.1...v0.4.0

v0.3.1

[0.3.1] - 2024-10-19

Added

• Ignore http requests timeout errors if fire and forget mode is active

Changed

• Run http requests commands asynchronous in a separate thread to prevent potential websocket heartbeat timeouts if the server takes longer to respond

Full Changelog: v0.3.0...v0.3.1

v0.3.0

[0.3.0] - 2024-09-20

Breaking changes

• 🎉 This integration can now also run on the remote. From now on each release will have a tar.gz file attached that can be installed on the remote (see Run on the remote as a custom integration driver)
  • ⚠️ Running custom integrations on the remote is currently only available in beta firmware releases and requires version 1.9.2 or newer. Please keep in mind that due to the beta status there are missing firmware features that require workarounds (see link above) and that changes in future beta updates may temporarily or permanently break the functionality of this integration as a custom integration. Please wait until custom integrations are available in stable firmware releases if you don't want to take these risks.
• When running as an external integration driver the working directory when starting driver.py should now be the root of the repository. The path in docker-entry.sh has been adjusted. The configuration json file is therefore now created in the root of the integration directory. Existing users have to move config.json from the intg-requests directory

Added

• Support for HTTP delete and head requests
• Support for adding json or xml payload data to a http request (see Adding payload data)
• Added an option to ignore HTTP requests errors and always return a OK/200 status code to the remote. Helpful if the server doesn't send any response or closes the connection after a command is received (fire and forget). The error message will still be logged but at debug instead of error level
• The wake-on-lan entity now supports an ipv4/v6 address or a hostname (ipv4 only) as a parameter when running as an external integration
  • This feature is not supported when running the integration on the remote due to sandbox limitations
  • Discover the mac address from an ip address or a hostname may not work on all systems. Please refer to the getmac supported platforms. Docker containers need to be run in the host network (--net=host)
• Add build.yml Github action to automatically build a self-contained binary of the integration and create a release draft with the current driver version as a tag/name

Changed

• Due to the custom integration driver upload feature setup.json has been renamed to driver.json and moved to the root of the repository
• Add custom user agent for http requests (uc-intg-requests)
• Corrected the semantic version scheme in driver.json (x.x to x.x.x)

Full Changelog: v.0.2-beta...v0.3.0

v.0.2-beta

[0.2-beta] - 2024-06-26

Breaking changes

• This integration now uses a configuration file to store the setup state and advanced settings (see below). Existing users therefore need to run the integration setup again to create this file. Just open the integration settings and click on "Start integration setup". You don't need to enter the advanced settings.

Added

• Added a more granular http status code response handling
• Added optional parameter to send form data in the request body as key/value pairs (see README)
• Added optional custom global entity-independent timeout and ssl verify option in the integration setup. For self signed ssl certificates to work the ssl verify option needs to be deactivated.

Changed

• Only return an error response to the remote if the http response code is in the 400 or 500 range. Otherwise display the status code in the integration log if it's not 200/Ok

New Contributors

• @Kat-CeDe made their first contribution in #1

Full Changelog: v.0.1-beta...v.0.2-beta

v.0.1-beta

[0.1-beta] - 2024-04-27

Added

• First release which supports http get, post, put, patch and wake on lan

Full Changelog: https://github.com/kennymc-c/ucr2-integration-requests/commits/v.0.1-beta