... I now need to monitor something that is not attached to my
LAN...periodically send an HTTPS post ... how would I do it?
Exposing a secured HTTP server from a private network on a public network would likely be just as complex as doing the same for MQTT.
Consider embedding the data in a HTTP request. Most private networks use firewalls already setup for this purpose.
An example for sending temperature:
http://www.myprovider.com/storemydata?temperature=28
This is a very simple example and needs code support on a public server. Essentially that public server code runs when someone or something uses the URL "www.myprovider.com/storemydata". The code would be looking for, in this example, "temperature" and store it's argument "28".
Later, using a different URL (for example "www.myprovider.com/getmydata"), different code would read the stored temperature data and integrate it into a web page.
Considerations:
- Can the Tasmota firmware pull web pages in order to send data? And if so, can Tasmota embed data into the URL?
It appears websend (search this page for websend) and webquery (search the same page for webquery, more can be found in this thread) are features of Tasmota. These commands appear intended for Tasmota to Tasmota as well as Tasmota to other IOT devices (i.e. Philips Hue Hubs) control. As information can be sent to control other devices, it follow information can be sent for posting to any HTTP server that understands the content.
- Can something be built inside the private network to subscribe to Tasmota MQTT data and generate the URL to support sending specific data such as temperature using a URL request?
Almost certainly. From many to choose from, consider NodeRED. This is a graphical programming environment which supports MQTT and allows for customization using java script programs.
Instead of using the fictitious, in the above example, "www.myprovider.com" consider using a service like X. This older NodeRED/Twitter tutorial may help even if it is a little out of date.