I’m creating a new, dedicated topic for my Edgebridge application, which was originally discussed in this topic:
Edgebridge is an application you run on an always-on computer on your LAN that provides two useful functions:
Gives you the ability to send HTTP(s) messages to endpoints outside your LAN (similar to a Proxy)
- Normally, Edge drivers can only communicate with endpoints on your LAN
- Initiate these requests from either my webrequestor (github | topic) driver or from a custom Edge driver
- Use cases: need to retrieve info from any internet endpoint that provides a RESTful API, e.g. SmartThings API, weather data, etc.
Provides a simple mechanism for LAN-based applications and devices to integrate with Edge drivers.
- Use cases: motion notification from external sources such as Blue Iris, device monitors such as phone presence trackers or pingers, generic triggers from applications or devices
- Edge device drivers are available for easy integration for motion, presence, and basic triggers
Edgebridge supports both http and https request forwarding.
Please see my readme file on github for complete details.
Today I’m announcing an update to edgebridge with the following new features:
- standardized logging output with control of console vs file logging
- configurable timeout for forwarded requests
- forwarding of request body data now supported in POST and GET requests
- Optional SmartThings Edge device to monitor edgebridge online/offline status
If you are a current user of edgebridge, you can download the new files from the github repository when you are ready. Be sure to update your edgebridge.cfg file, as it can contain new options.
Please note that the updated edgebridge application is required to use the optional SmartThings edgebridge online/offline monitoring device.
I have also added instructions to the readme file for setting up autoloading at boot time on a Raspberry Pi.