smorgasbord Posted November 5, 2024 Posted November 5, 2024 Just migrated from an ISY-99i to EISY, running 5.8.4, using the default (UD) SMTP server. Email to normal email addresses works. Email to 9876543210@txt.att.net numbers (ATT wireless SMS) doesn't work. However, from my email account, messages to that same ATT wireless numbers works. Error message attached.
Techman Posted November 5, 2024 Posted November 5, 2024 AT&T blocks most email to SMS messages. They use a very agressive spam filter. You should be able to use TEXT from the eisy however the message may not format properly. Have you tried using your own email server rather than the default server? Which ISP are you using?
smorgasbord Posted November 5, 2024 Author Posted November 5, 2024 My ISP is Frontier; My email provider is TutaMail, and I don't believe they provide SMTP services (encrypted service like ProtonMail). I don't know about the "TEXT" feature - can you explain/link? thanks
Techman Posted November 5, 2024 Posted November 5, 2024 My error, I see that you're using txt.att.net. Do you have the TLS box checked. You should also increase your timeout to 9,000 The above may resolve you issue. let me know
smorgasbord Posted November 5, 2024 Author Posted November 5, 2024 Can't do either TLS or increase timeout when using the default UD SMTP server.
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 FWIW, this was working on my old ISY-99i. Same program (backed up on ISY, restored in EISY).
Techman Posted November 6, 2024 Posted November 6, 2024 @smorgasbord Can you post a copy of your error log. You might also try rebooting the eisy. Being that your regular email account works, why not use those settings for the eisy rather than the default SMTP server
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 Well, now even sending to my regular email address is failing. I've rebooted multiple times. Here's the log for 2 Test sends, nothing really in there except what's shown in the error dialog. ISY Error Log.v5.8.4__Tue 2024.11.05 05.14.16 PM.txt
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 Alternatively, can I write messages to the console? The UD Mobile app has messages for PG3 starting and stopping. Can I write my own messages there? I'm trying to do some debugging on my programs with timers and countdowns and not being able to do the equivalent of printf is pretty frustrating.
Techman Posted November 6, 2024 Posted November 6, 2024 Just looked at your error log. Your SMTP settings are either incorrect or you don't have an good internet connection. Check your eithernet cable. Are your firmware and UI the same version? It's also possible that your migration got corrupted. There's no option to write messages to the admin console, not sure about UD Mobile. There are 4 eisy files in your windows temporary folder starting with UDI_TREE.STATE. You can delete them, which may or may not help.
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 (edited) I don't have any SMTP settings since I'm using the default via the check box. I have an excellent 1Gig internet connection. EDIT: Just swapped the cable. No improvement. EDIT: Firmware and UI are both v.5.8.4 I assume the UDI_TREE-STATE files are on the eisy - (they're not on my host, which is Mac). How do I access the folder to delete them? thanks again. Edited November 6, 2024 by smorgasbord
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 (edited) After a reboot I tried the Test function again. Got a new error: Also, maybe I should file a support ticket as this is a brand new, just installed today eisy. So, maybe there's an internal hardware problem? Edited November 6, 2024 by smorgasbord
DennisC Posted November 6, 2024 Posted November 6, 2024 The simplest solution would be to create a no cost Gmail address and use that just for sending messages from eisy. You will need to create an app password. There are instructions in the wiki. The best solution would be to use the Notification plugin along with Pushover. Check for more information in the Notification plugin write up.
Techman Posted November 6, 2024 Posted November 6, 2024 @smorgasbord Being that your email was working on your ISY It's probably best to submit a support ticket. You should get a quick response. https://www.universal-devices.com/my-tickets After you get it resolved, post the action taken.
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 So the plot thickens! In submitting a ticket, it took 4 or 5 tries for the Captcha to connect from my browser. At first I was thinking it might be that I have some sites blocked via my hosts file, but eventually the Captcha pictures came up and worked. I'm wondering if this sort of intermittent problem with the Captcha is connected with my email sending problem. I'm not running my VPN right now, but have in the past...
Techman Posted November 6, 2024 Posted November 6, 2024 Take a look at these issues with a MAC Universal Devices, Inc. Wiki
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 Thanks for that, but this Captcha thing isn't in the Admin Console, it's on UD's ticket website.
Techman Posted November 6, 2024 Posted November 6, 2024 I just logged onto the UD Ticket website and wasn't presented with a Captcha. https://www.universal-devices.com/my-tickets
smorgasbord Posted November 6, 2024 Author Posted November 6, 2024 Yeah, the Captcha is only for submitting a new ticket. And maybe it's only for the first ticket one submits.
smorgasbord Posted November 7, 2024 Author Posted November 7, 2024 After a few go-rounds trying different things with support, it looks like I did not have IPv6 enabled in my router. Enabling that seems to have gotten regular email notifications to work, although the ATT Wireless (9876543210@txt.att.net) email to SMS still fails. That's probably ATT's fault.
Solution Techman Posted November 7, 2024 Solution Posted November 7, 2024 @smorgasbord Try using Multimedia Messaging Service, which AT&T still supports. (your phonr number) @MMS.ATT.NET
smorgasbord Posted November 7, 2024 Author Posted November 7, 2024 So combination of enabling IPv6 on my router and @Techman's MMS.ATT.NET make text messages work! At least until I over use it and get blocked by ATT I guess. Thanks! Now onto groking the programming model.
Recommended Posts