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

wswartz

Members
  • Posts

    81
  • Joined

  • Last visited

Everything posted by wswartz

  1. I have two garage doors, both controlled with a home made remote opener (an ESP8266 controller and a relay). One is using MQTT for receiving an ON command (the "shed"), the other is set up with it's own web server and simple POST with an ON message will close the contacts (the "garage"). I want to migrate the garage opener to MQTT like the shed. Doing so allows me to integrate with Home Assistant and thus, work with my Apple HomeKit for voice activation via Siri. For the garage, I have a TriggerLinc that senses the status of the door. If it's open, it turns on a button on a KeypadLinc in the house. It was easy to set this button to also open and close the garage door. I had a program that said, if the button was switched on or off, run a network resource. The network resource in turn sent a POST to the garage opener's URL to open the door. Easy! However, with a move to managing the garage opener via MQTT and HA, I'm not sure how to make this happen. I tried to create an automation in HA that would send the MQTT command if the button state changed. However, just by virtue of the TriggerLinc changing the button state caused the automation to perform the opposite result (ie: close the door, button turns off, automation sends MQTT, door opens back up - ugh!). I'm thinking my solution lies somewhere here: https://www.home-assistant.io/integrations/isy994/ Maybe create a variable in the ISY that keeps track of the button push and make that a sensor in HA? Just making that up (and not even sure how I'd make that happen)... Is there a better solution? Thanks!
  2. It was the power supply. I was able to get another one and the ISY came up with no issues. Thanks to everyone here for your suggestions and support!
  3. Thanks for the input above. I’m back from my trip and was able to unplug the unit leave it off overnight, then plug it back in. Unfortunately, just got the power LED, nothing else. So at this point, I think it’s toast. Looks like I’m going to have to get something new to manage my 80+ Insteon device network. My install has been rock solid for over 10 years and I haven’t paid any attention to what’s new. Is the eisy a direct replacement for the isy994i? My PLM is a 2413S any issue there? (yes, I need to do some research and catch up, but hoping for a quick jump start here).
  4. I was doing some work on my network and had to unplug my ISY. After plugging it back in, it didn’t come up. I’m getting a green power light, but nothing else. Ethernet lights don’t blink and I can’t ping the unit. On top of all that, it happened an hour before I had to leave for a week long trip and my poor family is left at home with no home automation (gasp, the horror!). I’m not in a position to do much diagnosing, but I’m guessing it’s dead and I may need to move to a the latest eisy. To help get a sense of what I’m in for… 1. If anyone has some diagnostic suggestions, please provide. 2. While have a backup of my system, my unit is still on v4.9.0. From what I’ve been reading, I would need to have been on version 5 to migrate. Is there any option to migrate with v4.9.0? Thanks.
  5. ...the PLM???? I've had this issue for a number of years: about every 4-6 months, things that rely on a program to run will stop working. For example, a program that watches for a switch to turn on that will then turn on a bunch of other switches. When these programs would stop working, I would simply reload the PLM and everything would go back to normal. Even when this would happen, I could still see the devices in ISY and use the interface to control them. This issue happened again earlier in the week and I performed my standard PLM restore. Except this time, only about half my network was reachable. That is, some devices reported back during a query from the ISY, and others didn't. Those that didn't reply to the query were not controllable from ISY. At this point, I did a full reset of the PLM - removed power from the PLM, shutdown my ISY, did a factory reset of the PLM, and applied power to the ISY. After this, things were much better - most of the network is now visible with the exception of a few stray switches. So, at this point, you're wondering, how old is this thing? It's a 2413S v2.0 and it's been working fairly well for the last 8 years - well past it's normal life span I'd imagine! To my questions: 1. So, it sounds like the PLM is the culprit, but I'm a bit confused. While half of the network seemed unreachable, why did the other half still work? I'd imagine if the PLM was dead, it would not work for anything. While I've had to reset my PLM in the past, I've never seen half my network be unreachable when the PLM was acting up. 2. I'm investigating the various repair services available from nilachidatasystems on eBay and I've read a few comments here. Should I consider sending it in for a rebuild? 3. I'm comfortable with a soldering iron and replacing components myself. If it's just replacing caps, I can do that. If it's replacing IC chips, I'd rather have someone else do that. Could the caps alone cause communications issues like the ones I'm seeing? I would hate to replace the caps just to have to send it in later to fix something deeper. 4. I've read in the forums here that there are instructions for replacing the caps, but I've just found posts from folks saying they've done it. I'll continue to search, but If anyone has a link handy to instructions, please forward. Thanks, Bill
  6. wswartz

    Lost devices

    Thanks for your suggestions. Here's what I've done in the last few days... 1. I fixed the majority of the non-responding devices by adding a range extender to the circuit. This brought 3 switches back that weren't working. I really don't understand this since there are 5 other operational dual band switches within 4 feet of those that weren't responding. Plus, this area has been working well for the last 7 years. It's in a basement bedroom near the utilities. Nothing has changed there (no new equipment, changes in electrical). 2. The dimmer module was the victim of mistaken identity. I thought I pulled one when I really pulled another. Reset the module and deleted what thought was the instance in ISY. The Event View helped me figure that one out (thanks!). When I went to re-add the module, it said it already existed. Sure enough! Did a Restore Device with it's proper ISY instance and that one is working again. 3. I did the PLM Link Table test as requested. Did it 3 times with the following results: 426, 306, 172. Wildly different? Not sure what to make of that. 4. This is the kicker... an I/O Linc. From the event viewer, this is what I get when I try to do a query (address is 30.DF.27): Sat 01/16/2021 01:57:45 PM : [INST-TX-I1 ] 02 62 30 DF 27 0F 19 01 Sat 01/16/2021 01:57:45 PM : [INST-ACK ] 02 62 30.DF.27 0F 19 01 06 LTSREQ (01) Sat 01/16/2021 01:58:16 PM : [INST-TX-I1 ] 02 62 30 DF 27 0F 0D 00 Sat 01/16/2021 01:58:16 PM : [INST-ACK ] 02 62 30.DF.27 0F 0D 00 06 (00) Sat 01/16/2021 01:58:25 PM : [INST-TX-I1 ] 02 62 30 DF 27 0F 0D 00 Sat 01/16/2021 01:58:25 PM : [INST-ACK ] 02 62 30.DF.27 0F 0D 00 06 (00) Sat 01/16/2021 01:58:32 PM : [INST-SRX ] 02 50 14.7B.37 00.00.01 CF 13 01 LTOFFRR(01) ...and a Restore Device: Sat 01/16/2021 01:58:34 PM : [INST-TX-I1 ] 02 62 30 DF 27 0F 0D 00 Sat 01/16/2021 01:58:34 PM : [INST-ACK ] 02 62 30.DF.27 0F 0D 00 06 (00) Sat 01/16/2021 01:58:38 PM : [30 DF 27 1 ] Memory : Write dbAddr=0x4009 [15] cmd1=0x20 cmd2=0x15 Sat 01/16/2021 01:58:38 PM : [INST-TX-I2CS] 02 62 30 DF 27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB Sat 01/16/2021 01:58:38 PM : [INST-ACK ] 02 62 30.DF.27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB 06 (15) Sat 01/16/2021 01:58:47 PM : [INST-TX-I2CS] 02 62 30 DF 27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB Sat 01/16/2021 01:58:47 PM : [INST-ACK ] 02 62 30.DF.27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB 06 (15) Sat 01/16/2021 01:58:56 PM : [INST-TX-I2CS] 02 62 30 DF 27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB Sat 01/16/2021 01:58:56 PM : [INST-ACK ] 02 62 30.DF.27 1F 20 15 00 00 00 00 00 00 00 00 00 00 00 00 00 CB 06 (15) Sat 01/16/2021 01:59:00 PM : [30 DF 27 1 ] Memory : Write dbAddr=0x4009 [15] cmd1=0x20 cmd2=0x15 - Failed I'm guessing that last line can't be good, eh? As I mentioned in a previous post, I was able to replace this I/O Linc with a spare (it was managing my main water valve, so it's pretty important!). So at this point, everything is back up and running. But if there are any suggestions on how to recover this non-working I/O Linc, I'd be interested. Thanks, Bill
  7. wswartz

    Lost devices

    Not that I'm consciously aware of. I have done this once. I can try again. BS
  8. wswartz

    Lost devices

    Update: One of the modules was an I/O Linc. I replaced it with a spare and it is back to normal. I factory reset the original module and removed it from ISY, then tried to re-add it. It won't install. Same story with a dimmer module. I either have some modules that work but won't communicate, or something with my ISY.
  9. wswartz

    Lost devices

    Sorry, meant to add that. Version 4.8.0. And yes, using the ISY Launcher.
  10. wswartz

    Lost devices

    I have about 80 devices in my network that have been running well over 10 years. In the last week or so, a portion of my house began to stop responding. They are devices of all types - dimmer modules, dimmer switches, on/of switches and one relay module. I have pulled some of the modules and brought them to an area with great signal. In ISY, it can't query them. I've tried to reload them, even removed them from ISY, factory reset, then tried to re-discover. They won't seem to come back online. When I went to discover, I never saw the box that says they were being added. The screen flashes for a moment, then it goes back to the main page. In one case, I removed a dimmer module that isn't working and put a brand new module in the same socket and added it to ISY - worked great. Almost seems the ISY is holding on to some old configuration and won't allow a factory reset device to get added in. Any thoughts as to why I can't get these devices back online? Thanks, Bill
  11. @Teken I have 123 devices in my network. I ran the PLM link count (from: Tools->Diagnostics->Show PLM Links Table) 5 times with the following results: #1: 980 #2: 312 #3: 473 #4: 634 #5: 461 I did a search of the wiki here-> https://wiki.universal-devices.com/index.php?title=Main_Page for "link" or "links" and found no relevant information regarding a correlation between links and devices. If you can guide me to more specific documentation, that would be great. As far as the date sticker on my PLM, there are 3 stickers: #1: "QC5" - imagine it's a quality control sticker #2: Address of the device ("xx.yy.zz") #3 Sticker with the Model, rev, and another number - the sticker reads: "2413S", "Rev 2.0", "1438". Not sure what that last number is. The "Rev 2.0" is a printed sticker on top of the sticker (and in a different typeface). There could be a date below it - I didn't take it off to look. Thanks for your assistance.
  12. Well, frankly, I'm not clear exactly how the HA/ISY integration works. I installed this integration on HA: https://www.home-assistant.io/integrations/isy994 My impression is that HA is calling ISY and the ISY is talking to the PLM. But I could be wrong on how that works.
  13. I have a 2413S Dual Band v2.0. I believe it's over two years old - I didn't see a date on the back of the unit. It's my second PLM that replaced one that did experience power supply issues. Totally get that the PLM is a finicky beast, but I can't ignore the correlation. Add HA and now having to restore every other week or so. Guess I could remove HA for a bit to see, but I'm getting so much out of using it.
  14. About every 6 months or so, for some reason I have to restore my PLM. I find that after some time, my programs stop working - but a PLM restore puts everything right again. It hasn't been a big deal to me since it happens so infrequently. However, in the last two months, I've had to restore my PLM three times. The only change in my setup has been the addition of Home Assistant which I installed just about two months ago. My main purpose for adding HA was so I could monitor the ESP8266 temp sensors I built. But when I discovered I could integrate my ISY with it as well, I really got interested. At this point, I'm not running any automations from HA - just using it to monitor status and turn on/off the occasional switch. Would the addition of HA be the cause of my frequent PLM restores? Anyone else experiencing such an issue? Thanks.
  15. Hello? Looking for some sample code, anything that shows how to do a subscription using ISYlib. I can probably figure it out from there. Thanks!
  16. So, from what I've been seeing, I need to use websockets to subscribe to the ISY. I looked at the mentioned libraries. While the code for Psisy is on Github, I couldn't' find any documentation. There is a link for information on the library, but the link is dead. I was able to get ISYlib to work a little bit - wrote a few lines to print print some info on my ISY which worked. But I'm not a programmer - I have to Google for every line of code I write. I found the documentation on ISYlib to be extremely light and searching for additional examples both here and on Google came up wanting. Wondering if there is a source for more documentation on ISYlib - or better yet, anyone have some example code that would do what I'm trying to accomplish? Thanks, BS
  17. Figured out the URL's... reading... thanks.
  18. Thanks for the reply. I'm getting a "404 not found" for every link in the Legacy section. Do you have a better place to get this information? Bill
  19. I'm interested in saving the ISY log to a file that I can use to view or store in a database. My thought would be to have a script run every 5 or so minutes to grab the log via REST. My concern is that for each call, I'll get a full list of events that are duplicated with the last call. I guess that my script will need to pull a log file, then dedup what was pulled from the previous call, then save the difference. Is this a correct assumption or is there a way to just get the last updates to the log? Bill
  20. Thanks for all the suggestions! Since I wrote this, I was poking around my box of extra Insteon stuff, and came across a Synchrolinc, still new in the box - SCORE! But I have number of other current sensing projects around the house so I'm excited to try these alternatives. Based on what I read, I ordered one of these from Amazon: https://www.amazon.com/gp/product/B00I9IFJOM/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1 I'll pair that up with an I/O Linc and see how well it works. I'm also interested in trying this current switch in conjunction with an Arduino based controller. Maybe something based off an ESP8266 that could send an API call to the iSY for further action. Has anyone considered something like this: http://henrysbench.capnfatz.com/henrys-bench/arduino-current-measurements/acs712-arduino-ac-current-tutorial/ ...using a Hall effect sensor and Arduino? More invasive than the current switch of course. Just wondering if there are advantages of going this way. Thanks, Bill
  21. Appears none of the suggested alternatives provided above are available. Wondering if anyone has other ideas on how accomplish the same function as the SynchroLinc (2423A5)? Either another source for the product, or maybe something more DYI, like an Arduino circuit that would work in it's place.
  22. Great thread! Wanted to jump in and share my TTS solution. Probably not easy to replicate, but works really well... Using Cisco Call Manger Express with 13 IP phones throughout the house. Phones are also touch screen capable and are my control interface to a number of ISY programs and scenes. For TTS, I use software by Cepstral: http://www.cepstral.com/ I tested a number of TTS solutions (both free and paid) and this solution seemed to be the most clear and understandable. I still need to convert the TTS audio into a format that the phones can consume. I do this with some scripts that run the audio through FFMPEG. Then, using the same process outlined by Thanatar previously, the ISY can provide triggers to the audio alert system. The kids have affectionately named the system, "Jarvis" (not original, but they think it's cool), and "he" has almost become another member of the family. Here's a sample of what Jarvis does for us: - Wakes the kids up (and if they don't get up, he wakes up mom/dad and tells specifically which kid isn't up) - Tells kids when to go to bed and if they are goofing around instead (via motion sensors) - When the bus comes in the morning (motion sensor outside) - Alerts on water in the basement, under sinks, and water in basement windows wells - Alerts on intrusion - If our chickens are free-ranging, alerts that it's time to put them away (sensor on chicken door) That's just the short list, there are a bunch more. Finally, Cepstral does offer a voice that works with the Raspberry Pi. Go to their demo page (http://www.cepstral.com/en/demos) under the "Voice" drop down and listed to the US English voice called "Callie". Last I checked, they offer this voice for only $35. The voice I'm using is a UK English voice called "Lawrence" and he has that English butler kind of sound. Thanks, Bill
  23. Stu, Tell me more about this please. With the exception of my receiver, all the rest of my the audio/video equipment on a UPS which is then connected to a FilterLinc. The receiver is by itself on the SynchroLinc. My goal for this: separate rooms (theater and game room) in the basement. Game room has motion sensors that turn off basement lights if no one is there. But if we're watching a movie (ie: the receiver is on), I want the lights to stay on. I have no FilterLinc on the receiver because I assumed it would also filter out Insteon signals for anything that was behind it. And, I'm pretty sure I can't have the receiver on the UPS as Insteon wouldn't get past that either. Any solutions for doing SynchroLinc behind a UPS? Thanks, Bill
  24. Stu: It's a receiver. Larry: Restoring the device worked. Seems all is well now. THANKS!
  25. Several months ago, I installed a SynchroLinc to monitor the state of a load. It was working as expected until this past weekend. Since then, the ISY won't detect when it switches state; ie: if switched on, the ISY shows it's still off and visa versa. The SynchroLinc itself seems to be working fine (green led when load is on, red when off). When the SynchroLinc is turned on, and the ISY says it's off, if I do a query, it will update to show the proper state. I've rebooted the ISY a few times and had to reload my PLM for an unrelated problem recently. Does this indicate a communications problem? Not sure if that would be the case as my house is pretty much all Insteon and nothing else seems to be having issues. Thanks, Bill
×
×
  • Create New...