architecture VS TextBelt

It looks like Home Assistant refuses to add support for this.

Read here ha install

It’s all clearly defined in ADR-007 https://github.com/home-assistant/architecture/blob/master/a...

The TL;DR: Authentication for devices and services are via the UI only (to deal with OAuth2, refresh tokens, auto-updating IPs via mDNS). Automations/scripts/scenes are both YAML or UI.

Regular Docker installs are not unsupported. HA Supervised installs, if they don't meet the specific requirements, are unsupported.

Just make sure you follow the link at the top for the requirements and have all of the requirements insyalled before running the script.

A good write up / discussion was held on GitHub about this.

You can read more about it here.

Yes nest stream urls only last 5 minutes and we need to rearchitect streams https://github.com/home-assistant/architecture/issues/482

There is an architectural issue we're working through in https://github.com/home-assistant/architecture/issues/482 -- stay tuned. Once that is resolved, the "preload stream" checkbox will work to get it all ready before you open it.

I doubt you'll find a free SMS texter. Textbelt seems to be low-hassle and open-source. There's an option for standing up your own server to make it "free". I'd look into email options as well. It looks like most carriers support some kind of email-to-text path.

I use paid service textbelt.com (also www.twilio.com is there), they have standard plugin for many languages.

# Path: lib/sms_demo/sms_handler.ex defmodule SmsDemo.SmsHandler do use GenServer def send_message(to_phone, message) do GenServer.cast(SmsDemo.SmsHandler, {:send, {to_phone, message}}) end def receive_message(from_phone, message) do GenServer.cast(SmsDemo.SmsHandler, {:receive, {from_phone, message}}) end def start_link(_) do GenServer.start_link(__MODULE__, [], name: __MODULE__) end def init([]) do {:ok, %{}} end def handle_cast({:send, {phone, message}}, state) do textbelt_url = "https://textbelt.com/text" textbelt_key = Application.get_env(:sms_demo, :textbelt_key) replyWebhookUrl = Application.get_env(:sms_demo, :webhook_url) params = %{ phone: phone, message: message, key: textbelt_key, replyWebhookUrl: replyWebhookUrl } HTTPoison.post(textbelt_url, Poison.encode!(params), [{"Content-type", "application/json"}]) {:noreply, state} end def handle_cast({:receive, {phone, message}}, state) do # TODO: Do something with the message {:noreply, state} end end

I was recently introduced to the SMS service TextBelt which is a pre-pay and simplified service to provide the ability to send and receive SMS messages from code.

I was looking into some side project ideas and stumbled upon one called textbelt where the guy uses something like twilio in the backend and sell 10x per SMS. It is kinda arbitrage for SaaS products. This guy is legit and also has 5 to 10K $ per month stripe verified indiehackers project. More over he doesn’t even promote his product and moved on. Yet this is so popular enough to bring in 5k a month. Do you guys think its possible to reinvent something like this and promote to make a worthwhile side project ?

You can look into this: https://github.com/typpo/textbelt

Can your monitoring system run shell scripts and curl in response to events? If so you could use a service like Textbelt to send SMS messages from it.