jeffpdavis1

Sorry. The devices are no longer available.

Sometimes it helps to visualize (and verify too) the items. The three devices in boxes are unused. I think I plugged that Insteon Hub in once (it came with something else that I wanted 7 or 8 years ago) and didn't even connect anything to it. Yes, pos. Two of the five LampLincs may be bad as you can see by my notes on the back of them. I tried again later and one of them worked correctly. I was suspicious when I removed them from service that the cause was something else and now I'm unsure. Still, probably not a deal killer I had forgotten how many of those FilterLincs I had. One for each of the UPSs scattered around the house among other things. Oh yeah, I have the Garage door close sensor too that I've been using with one of the IoLincs. I just have to retrieve it. I had some idea of the inflated value for the 2413S PLMs...maybe $150 but not $450!! I was originally thinking that my whole collection might be worth $1000-$1200 to someone. I don't know but somewhere in there might be fair.

Yes, the one I've been using for 3 years or so is V2.1, 1514. No problems with it at all. The one still the box is Revision 2.3 4216

I've got all of the following I want to sell as a lot. I'm not interested in in selling them individually. All but 4 items have been in use by me for the past 4 years. The unused items are 1x 2477D, 1x2466DW, the Insteon Hub and 1x 2413S. I was unsure of the original cost of the items listed as whole numbers so I estimated. I'm also unsure what a fair asking price is or how the transaction could take place. I'm hoping not to have to deal with ebay. Update: The devices are no longer available.

I am almost to the point where I was thinking the same thing. Not ISY. Not the locks. Not ISY z-wave dongle or network. It must be the missing siren. Any recommendation for an equally strong repeater like the siren. I've looked for a way to disable the siren and just have it be a repeater, but I admit not very thoroughly. Thanks for the clear concise evaluation.

I only have 5x z-wave devices: 3x Kwikset 914, 1x Aeotec Siren Gen5 and 1x Minoston miniplug. They were all communicating fine in my ISY 5.3.0 (Firmware and UI) with the upgraded Z-wave Series 500 dongle (Version 6.82.01) added on a few months ago. While we were away for a few days a neighbor could hear the siren going off from the street. She contacted us and we gave her the codes to enter and unplug/disarm the Siren. That fixed the main problem except for why the siren went off in the first place. In our normal away mode, it would go off for a while if and only if someone opened one of the doors and triggered one of the Insteon in-the-jamb Open/Close sensors. These events would have sent us a notification, but none of that happened. I was left to think when we returned that the Siren had just gone off in the weeds. Fine. I only got it over a year ago because I thought I needed a repeater in between the straight line of sight between the front door and back door. The back door lock wasn't always working with Series 300 Z-wave without it. My office (location of the ISY) is only about 15 feet from (nearly line of sight of) the front door lock, which works well. The third lock is also about 15 feet away from the ISY but through one wall into the garage. Also when we got home none of the 4 remaining Z-wave devices were working reliably, so I quickly ordered another Minoston miniplug to go where the Siren was and repeat the signal. That didn't solve the problem. So is it the device(s) or network? The third garage entry door never stopped working reliably...phew. That's one. For the front door I took it apart, removed and replaced the batteries and the put it back together and the front door was working fine...Update Neighbors, Queries all worked just fine. Well it should, it's only 15 feet away! For the back door, brought it back to within 12 inches of ISY, removed and added it back in. All queries and other tests of it worked...from < 3 ft. I moved it out 10 feet away into the long open area between the front door and its eventual destination 40 feet away. All tests still good. Moved it 20 feet closer to final destination...still good. Moved it the last 15 feet and couldn't communicate with it. The same scenario was repeated for the new repeater. Works at < 3 ft, and at 10 feet line of sight but not at 25 feet (around the corner but still only through one wall). Also, same scenario with the siren being removed and added back in to its formerly good spot. The neighbors seem to be updating correctly at each stage from the Front Door (Show Information in Event Viewer). And the same with the Garage Entry Door. If I go back to the Siren going off while we were gone, I wonder whether the siren malfunction was the cause or the effect of something else in the Z-wave network. I'm willing to do a dongle reset if needed and then add everything back in. Could the Z-wave dongle have just failed...sort of? Why does the back door lock work at closer ranges but not 45 feet away in direct line of sight of the front door lock. Did the back door lock (and not the other two) just fail coincidentally with the Siren inexplicably going off? Could it be something in the ISY z-wave dongle? I'd like to have smart locks that can be controlled with the ISY and its other 50+ insteon devices. What are some other troubleshooting steps that I can take?

Ok, thanks. I'll give them a call when the time comes.

When I get another ISY for the new house, I'd like to move the Climate, Portal and Networking modules to it. 1) I see that I can delete this ISY from my portal. I assume that will make it (and Networking that came with the subscription) disappear from the admin console, right? 2) If not, what do I need to do in order to detach all of them from the current ISY and hold them in limbo until I get the new one? 2) Any other consideration other than Admin/PW, email addresses in the Notifications, smtp sender email? 3) Is there a list of steps disentangling me from the ISY that someone else has already prepared so I don't miss anything? Thanks for the help, Jeff

I'm feeling better all the time. Mine is v9E as well.

In reverse order, I think it's working correctly now. The high ceiling fans come on with heat and turn off with no heat. Perfect. Ever since the first PLM went bad and I had no ready replacement, I've soured a bit on having a system that is wrought with these critical points of failure, the PLMs, especially since they have been so problematic. So I did my best to address it by keeping a spare one on hand. I'm not sure if that's the best response, but it was based on thinking the new one wouldn't have the same bad components. Maybe there are other strategies for that. That first time when the PLM failed, I bought two more so I'd be prepared. Ironically (it's actually a little funny now), both of the two that I bought were the ones with the bad capacitors. So my second one lasted a while, then the next one was installed and got the first (of the two) RMA'd. Now I'm on my fourth one, always with a replacement on hand RMA'd from the previous failure. This 4th one is supposedly beyond the bad batches and has the improved capacitors. I'm not sure if one of the numbers is the date code you refer to but it may be. Also, I was in error about the age of this one. It's actually only been in service since August 4, 2015, but received by me in February, 2015. Here is the information about it: Rev 2.0, "1438" date code?, Purchased 2/5/15, Rec'd 2/9/15, In service 8/4/15. My current spare: V2.1, "1514", Rec'd 8/10/15. I've taken to keeping the invoices and shipping documents, but Smarthome has always been really good about the exchanges. Let me know if you can decode the date codes. They look suspiciously like they may have a year in them. Thanks for your help.

I think you were right on this last suggestion. I might have stumbled on to trying it as a last resort but it sure is counterintuitive. What makes these thermostat adapters different from the other Intsteon devices that they would report something that coincidentally was what was in the ISY links table? It sure calls into question all the other times I've used the Compare to move on to some other cause. Earlier today I had used the program in the wiki to query the thermostats every 15 minutes just so that it would get the status and turn the fans on and off. I don't seem to need that any more. I'll know more after it's gone through several more cycles.

Yes, often I neglect that Diagnostics step but this time I hadn't. They all were identical. And yes, the "then" portion performs correctly. The one thing that I didn't mention was that in the last 4 years, I've replaced the PLM 2013S annually or sooner because of failures. Probably a familiar story for many. I'm now 13 months since the last one and it seems ok.

I have had the older Venstar T1900 and the Insteon 2441V rev 2.2 for over 4 years now with little trouble. I have tried to use the status info, like calling for heat, from the T1900 to drive other events, like turn the ceiling fan on/off, and it seemed to work fine a couple of years ago. For some reason or another I disabled the simple program I had created a few years ago to do just that but now I want to enable it again. I've also noticed that in the past year or so MobiLinc HD used to display "Heating" after manually increasing the SetPoint from the app without having to refresh the particular TStat display. Now it will only display heating if I refresh it. The program mentioned above simply says if Status tstat is calling for heat, set ceiling fans on else set ceiling fans off. If I query the Thermostat main node from the Admin Console, the program indeed fires and operates correctly turning the fan on or off. My question is Has something changed in the way the ISY994 v.4.4.2 responds to the 2441V Insteon Thermostat adapter's status or is the adapter no longer reporting the status without being queried for it. If the latter, then is there something I can do to troubleshoot that or reset it somehow to start sending its status again without being prompted. I'd sure rather not have to get another Thermostat, as this is only one of three in the house. Thanks for the help. Jeff

The one that's operational right now says V1.B on the back of it and v9B in the PLM Info/Status box. My spare that I got in Feb 2015 says V2.0 on the back. How do I tell what the version is that compares with "v.9E" or is the v2.0 enough to confirm it has the corrected capacitors? Perhaps I should call it quits on the current one, replace it with the v2.0 I have, get Smarthome to send in a replacement under warranty and then keep the new one as the next one in rotation.

25.29.36 v9B / Connected Does the firmware tell you anything? I was thinking that this doesn't answer the question of cause. There were a couple of GFCI outlets that were thrown inside because of landscapers using their portable concrete mixer. Neither of those outside circuits were shared by the ISY or PLM but still it happened a couple of times. I noticed nothing in the ISY system when it happened. Any other guesses as the cause? I know they're supposed to last 2 years but the last two have been under a year or at least closer to one year than two.