I’m wondering that nobody complains about the following:
Nabu Casa cloud generates a remote link in a very long form e.g.
jqfsdfsdazertyuiopqsdfghjl.ui.nabu.casa
I’ve tried to use this link in tasmota mqtt configuration in a host field but it doesn’t work.
it always cuts off the part after first dot from the left (or it could be cutting after certain length of the string)
Should we request from Tasmota dev to extend alllowed length of this field or I’m doing somethign wrong?
well, it brings their statement about “worry-less remote access” under question.
Any other experience about mqtt from outside? duckdns is one of them, have used it, but sometimes messy when struggling with ports and firewalls on internal side.
Sorry for not coming timely with an answer to your question.
In my particular case, this is scenario:
my underground garage doe snot catch WIFI signal from my apartment. so, I’ve setup a 4G MiFi modem/router with only few tasmota devices (garage door open/closed RF sensor, sonoff tasmotized RF Bridge, an ESP based relay for opening/closeing door., PIR RF sensor …) . All this is now in a separate network (not part of the same where Hassio is) and needs an access to mqtt broker which is at my home, integrated into Hassio.
same scenario for summer house in country side. 4G modem with relay/switch for watter pump, light, etc.
Setting up a Pi in those two external locations for few devices only would be like “shooting a fly with cannon” so I though they can access existing MQTT broker and my existing Hassio setup could do logic an automatization.
I anyone has experienced (and solved) similar case-study, is highly appriciated to know working solution.
At the moment duckdns seems to be only workable fix.