Jump to content
AT&T to end email-to-text ×

fisix

Members
  • Posts

    89
  • Joined

  • Last visited

Recent Profile Visitors

1627 profile views

fisix's Achievements

Member

Member (3/6)

10

Reputation

  1. not just for sending, also for receiving. the point is having basically push notification for an email notification that shows up in your iMessage texts, so that the eisy notifications work basically the same as the SMS notifications did. for me, i don't want to check email, and i don't want to rely on a 3rd party app to get the notifications (for security reasons, device management reasons, and for other family-related reasons). anyway, here's one link showing the steps someone using an iPhone can use to receive emails as iMessage texts. my guess is that you'd want to set up a dummy email account on gmail or wherever that wouldn't get spam. https://www.idownloadblog.com/2016/04/29/add-new-email-to-imessage-in-ios/
  2. it looks like you might be able to link an email address to iMessage (if you're an iPhone user), so if you notify via that email address, it'll push/show up as a text on your iPhone. i don't see a great single link for instructions, but if you search on link email to iMessage, you'll see some instructions and videos and such.
  3. quick related question. does our current texting algo use sms specifically, or possibly mms? there's a push in telecom to end sms and move to mms. so, when ATT says they're ending email to text, are they ending the service only for sms? anyway, wondering if any of the below might work going forward: Common Carrier Gateway Domains: AT&T: SMS: number@txt.att.net MMS: number@mms.att.net Verizon: SMS & MMS: number@vtext.com T-Mobile: SMS & MMS: number@tmomail.net Sprint: SMS & MMS: number@messaging.sprintpcs.com Boost Mobile: SMS: number@sms.myboostmobile.com MMS: number@myboostmobile.com Cricket Wireless: SMS: number@sms.cricketwireless.net MMS: number@mms.cricketwireless.net Virgin Mobile: SMS & MMS: number@vmobl.com ah, both sms and mms: https://www.att.com/support/article/wireless/KM1061254/
  4. Has anyone implemented a notification process that uses the IF This Then That app/service?
  5. hi folks, i'm fairly new to the eisy. i upgraded (seamlessly from a 994i, still in use to access an encrypted zigbee link to my power meter) to the eisy mainly because the networking portal service was ending for the 994i. i remember something about text messaging costing a lot to maintain, and making that whole process more efficient being part of the push to the new hardware. i still use the text messaging to get push notices when certain things happen around the house, but the timeliness of the sms is more miss than hit of late, both before and after the recent database server shutdown (so, i don't think my issues are related to stuff that's happened since Dec. 27 or so). also, email messaging isn't something i believe i can use or rely upon. is there a push notification mechanism that's better than legacy SMS from the eisy? maybe i need to update something post-transition that i haven't updated yet? any help or suggestions for workarounds is appreciated. lack of timely event-driven push notifications in some form or fashion is a fairly significant devaluation event for my uses.
  6. Thanks Brian, more great info. I see a few nice looking switching 5V 2A warts that cost the same as the UD 12V one (with Prime shipping) but come with a range of additional plugs, including a 2 screw terminal plug that I can attach to any wart with the 5mm/2mm barrel plug. I'll probably go with that, just for the sameness and the additional plugs. I looked for some 12V warts with similar amenities and the normal safety features, but either they were the kind of wart that blocks other plugs or they didn't look/spec out as super sturdy.
  7. Thanks all - great info. I guess I'll go with the 12V wall wart... I hesitate to switch up from a 5v supply - that's lasted me this long without issues (will an internal regulator be working harder/hotter with a 12V input?), but seems alright if UD suggests it.
  8. Sorry, and one last question - the wall wart I have is a 5v 1A one that the 994i came with. Is there a way for me to purchase a new one, and/or is there perhaps a better way to power the 994i? Thanks!
  9. Ah - appears to be a power supply issue. I have a programmable power adapter (with a range of plugs) and once I used that to power the 994i, it booted right up. Scary though. Is there a way for me to backup the firmware image as well as the user settings, in case the on board memory dies? Would I just contact UD and ask for a new SD card to be shipped to me, then rely on the user setting backup to get the insteon and the smart meter integration back up and running? Thanks!
  10. I have my 994i hooked up to a UPS, but after a ~4 hour power outage (I was away), the 994i won't boot back into a stable state. When I power cycle it, regardless of what cables are attached (modem/network), the Power LED is almost solid blue with no other lights coming on (it's flashing at a high frequency). I haven't been able to access the device over the network. How do I proceed trouble shooting it? Does this seem like a wall wart issue (not providing enough power), or an internal storage/sd card issue? If I have a backup just prior to moving to the 5.x series of firmware, will reloading that onto a re-imaged sd card (with the most recent 4.x firmware) bring back both my insteon setup/programs and my zigbee access to my smart meter? Thanks for any help.
  11. aww. miss Grant. hopes and dreams talk, where did they go wrong?
  12. this is the guy i saw. this might be the talk i saw - sometimes there are breakout rooms with more demo/detailed stuff, so i'm not sure.
  13. i found and skipped through the talk you're referring to - that's not the talk i saw. the one i saw was by a fairly clean cut guy, running the talk by himself (though he had a helper), in one of the small rooms upstairs in Paris? - different talk, different people. he had a laptop, SDR dongle, and a 2x4 with two? retrofit plastic outlet boxes and an incandescent light bulb receptacle screwed to it. there was a lamp cord and two? dual band switches wired up to the light bulb, all plugged into the wall. he ran his software on the laptop, enumerated the device(s) (just a bunch of command line text to me, similar to what was shown in the Shipley talk), and then he toggled the light on and off using his laptop. i think he talked about how useful/not useful it would be to use the technique to cause mayhem or to get access to something important... he thought the enumeration could be useful, but that the wireless range was rather poor for a safely distant enumeration process (like in a car down the street or similar). i think i remember people in the audience discussing a previous demo that failed (perhaps the Shipley talk). i don't think this guy and his work were based on Shipley's work, but i do think it was meant to show that the proof of concept was doable fairly easily. whenever i broached the subject of protocol security with the smarthome folks on Alton, it was treated dismissively, and i think they tended to make public statements to that effect. that treatment of the subject was not warranted. what i took away from the talk i saw was that the insteon protocol was inherently insecure, but that it wasn't easier to leverage into unwanted access or vandalism than someone with a rock or basic lock-picking tools... as long as you didn't allow insteon devices to turn off your security system. kinda the same thing people have learned with Alexa - don't allow Alexa to unlock a deadbolt or open a garage door if you don't want an intruder to just yell their way into your house. likewise, don't allow an insteon device state change to turn your security measures/monitoring/alerts off. anyway, i think we're future proof in terms of getting centralized control of an insteon network; even once the smarthome manufactured PLMs and hubs die out, there are inexpensive ways to hack that access back into life. it'll be interesting to see what happens to Smarlab's IP. with freedom to operate, i really think powerline and dual band devices could be a $400M market, as long as someone can make the devices less expensive and smaller without making them unreliable. securing the protocol would probably be a necessity (if getting devices in many homes is the plan), but i'd want the ability to enable backwards compatibility.
  14. weird. i watched a demo maybe 5 years ago at DEFCON and they had free reign over an insteon network - the protocol was simple to control once the hardware to access the network was worked out. i believe they used an SDR dongle for the wireless band, but noted that it wouldn't be too difficult to create a powerline module.
  15. 1) there are no falsehoods in my post. i'm just not in the state of denial you seem to be in. 2) insteon devices were never "cheap" - how many of your friends and family have insteon devices that you haven't installed for them? the reason why that number is low or zero is because very few if any middle income consumers wanted to make the $$ investment needed to have a reasonably complete smart-controlled home based on insteon devices. compare x10 and Hue or alexa dot, google home, etc. those devices (aside from Hue) are roughly half the price of an insteon wall switch, and the Hue was an actual light fixture. 3) maybe you haven't installed insteon devices in old (1980s) housing, but the outlet boxes are shallow and the apertures for the switches themselves are narrow. an insteon switch about 0.5" shorter in depth and even just 1/4" narrower side to side would have been a huge reduction in installation woes. size always matters. i don't know why you care about zwave so much. 4) did insteon improve in quality since the purchase by the current owner (at least, current in January 2022)? no. did insteon improve in quality since 2007 or so? maybe? did they ever solve the PLM issues? not that i can tell (from posts on this and other boards). my personal PLM has improved, but i'm the one who improved it (with properly spec'd and quality caps). 5) the insteon hub and its integration with other devices has always been poor. insteon didn't adapt (meaning make purchase and installation of their devices easier) throughout any of the home assistants - they just kept selling pretty much the same old stock they had on hand; zero development of devices the new install base was looking for, and really poor advertising. in fact, insteon reduced their product line (because they ran out of old stock?) as time passed, and right at the time the market was looking for devices that pushed the edge of automated control. maybe they were trying with Nokia, but that seems more like it was a paper mache mocked-up attempt to make the company look like it was worth buying. 6) i know they had a 240v load controller - i have one, and i use it to control my ancient, inefficient pool pump. what the 240v load controller can't do is select a particular flow rate, such as what's been offered in new, much more efficient pool pumps for at least a decade now. most of the new pumps have an interface of some kind that provides for two way communication, but insteon never worked out a way to partner with any of the pool companies to get their protocol integrated with a pump, even as an after-market module. instead, insteon continued to sell fairly expensive fan links based on a fully electrical control module while even the cheapest fans in Lowes have zwave, zigbee, or some other wireless protocol built into them. management failure after management failure, vision failure after vision failure, basic business skills failure after basic business skills failure.
×
×
  • Create New...