Jump to content

fisix

Members
  • Posts

    89
  • Joined

  • Last visited

Everything posted by fisix

  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. interesting failure mode. i knew this going in, but it's always nice to be reminded why i've coded in controls that don't rely on Alexa/networking.
  12. Another update: After replacing the caps, the PLM has been working flawlessly. Yay! Thanks again for everyone's help and commiseration.
  13. Alright fellas, just an update. The system went back into the mode where none of the programs that required transmissions from switches/sensor BACK to the ISY were working, AND, on top of that, I couldn't run any of the programs using the various Alexa devices around the house. Just to remind, last time, the device-->PLM programs weren't working, but I could still verbally control things through Alexa... so, it at least seemed like signals from the PLM were getting transmitted out to the devices, but signals from the devices weren't being received by the PLM. I didn't do a lot of testing this time, unfortunately, but given the info you all provided before regarding the PLM failure rates, and how old mine was, I went ahead and ordered the caps to perform a repair. I did look at the LED light, and it didn't look dim to me... but whatever. In any event, tonight I pulled the old caps, installed the new ones, and then hooked everything back up. Initially, I noted that the device-->PLM programs still weren't working, but PLM-->device controls WERE working, and now I could control devices using Alexa (meaning, I could run the "then" parts of programs and control devices). So, I thought maybe I had made some headway, but things still weren't back to normal. Finally, I again went through the Restore Devices process. The process completed with no errors, and now all the programs are working as normal... meaning that both the PLM--> devices and devices-->PLM communications appear to be working. That's great, but I'm not feeling very confident about the reliability of the system at the moment. Which is a bummer after years of it being bullet proof. So, right now I'm in testing mode. If you guys have any thoughts on what might be happening, other than the caps going bad in the PLM, I'd love to hear it. Some possibilities: 1) some other component in the PLM is going bad - it seems like this would be tied to the Rx channel, but it would be pretty far upstream because it appears to be broken for both wired and wireless Rx signals. 2) some electrical component in the ISY is going bad - this could be tied to the Rx channel from the PLM to the ISY (Maybe the daughter card in the PLM is going bad?). This could be the issue - the PLM is plugged into the wall, and the ISY is plugged into a UPS - their grounds aren't the same, so I guess there's a chance that a power surge/outage could have caused a differential voltage to build up between them, enough to damage the communication components, even if they are only linked by transformers or optoisolators. 3) some logic component in the ISY is going bad - this could be a memory issue, but it'd have to be pretty mild to basically make the state machine crap out but still allow control signals to be transmitted to devices using the GUI. 4) some device in my group of devices is somehow corrupting the communication channel. I don't know how this might happen, but from other threads it sounds like some of the Insteon devices can go bad just the PLM does and perhaps send out noise on the communication channel... which could basically fuzz the system and generate erratic behavior. Just something to mull on while I wait to see if the system falls back into non-working mode. This last time, it took 2-3 weeks for the system to die, from when I last Restored Devices. Thanks everyone.
  14. Mine is V1.5 1130. Which makes no sense if I interpret 1015 as the tenth week of 2015. Unless there's a time warp. And V1.5 I don't think goes back to 2011... let alone the 30th month of that year. I'm working on finding a backup. Thanks for the links!
  15. How do I check if the link database is the PLM is empty? I was trying to diagnose last night but didn't really find a way to drill down into the functioning (or not) of the PLM.
  16. It's either 6 years old or 4 years old. I purchased one with my 99i, then got another when I upgraded to the 994i. I can't find the 99i or the other modem... so I can't tell what the date is exactly, I guess. That'll suck if it's going bad.
  17. All is good on the western front. Restore devices worked fine. Used this: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_.28PLM.29 Thanks!
  18. Ok, I figured it out. I restored a single switch, and now it works fine. That means I probably need to restore all devices to be safe. Sigh.
  19. Well... actually, I was able to reload the remotelinc, and now the programs tied to those switches run properly. I'm not sure what I'm seeing. I'm guessing there's some kind of link mapping that's now wrong for the fast on/off (multiple switches), and for the motion sensor. Maybe a data munging, or maybe the PLM is funky and needs to be remapped. Should I try "restore devices"? I've just now backed up the ISY, and the last backup I have is from version 4.5.4 of the firmware. Not sure how compatible the backups are...
  20. Hard boot didn't work either. I tried to replace cables and place the modem in a different socket, to see if that helped, but nothing. Clearly the motion sensor is wireless, but is perhaps the fast on/off feedback through the wireless channel rather than through the wired? I can control everything through the UI, as far as I can tell, but the remotelinc and the motion sensors aren't working. Could the dual band modem have lost its wireless band? It's the typical one from smart home, and it may be about 7 years old... Is there a way to diagnose the modem? Unfortunately, I don't have an extra one around...
  21. Firmware and UI are 4.6.2 and match. I'm going to go through both the reboot and the hard power boot and I'll report back. I've tried both but had no luck. I tried to get an 8 scene remotelinc to connect while rebooting and such before, but no joy. The ISY can send control signals to devices, can read device statuses properly (on/off), and if I run the "then" part of a program, the device does what it should, but the ISY just can't trigger any of the programs (none of the "if" conditions tied to device status/controls work). I just tried the reboot. Didn't work. Error log is below, and will try the hard boot next. Error Log: 2017/09/25 22:32:11 System -5 Start 2017/09/25 22:32:13 System -170001 [Network] Established
  22. I should add - it's just the programs. My tie-ins to Alexa are still working. Could a power outage have done something weird with the module that links the ISY to the power lines?
  23. Weird problem that seems to have just started today. None of my programs are executing - it's as if the ISY isn't receiving anything back from the various sensors/switches in the system. Including motion sensors, light switches (I have some programs tied to fast on fast off), and others. Any hints on what to try/look at?
×
×
  • Create New...