Everything posted by MarkJames
-
End/beginnin
Ahh - damn Any idea what exists that is similar to a Keypadlinc (8 buttons)? I guess I'll get out there and start exploring options.
-
End/beginnin
Well - that would be kind of mean. Leaving new owners with a problem that I know about. I wouldn't feel right doing that.
-
End/beginnin
They are the same - yes. But that's not going to help long term if they cease production
-
End/beginnin
As many have pointed out Insteon products seem to be done. I understand that the line is being picked up by Nokia but not all devices will still be available. I have a fairly large installation. Probably 80-100 Insteon devices. Many of my lights depend on Insteon control. This change in availability of Insteon products couldn't come at a worse time for me. I'm getting ready to sell my home and I have a couple of devices that are not working and I can't find replacements for - an 8 button and a 6 button Keypadlinc to be exact. I'm wandering around looking for KPL's that I can burgle from one location that I don't use as much to ones that I use a lot. I guess I'm going to have to move to a different technology to make things work again. I'm okay with moving to Polisy from my current 994 if that's what it takes. Can anyone point me in the right direction to start replacing some of my failed Insteon with something that I can integrate with or without PolIsy? Thanks
-
Keypadlinc 6 to 8 button
All changed over successfully. When adding it ISY identified it as an 8 button even though I had changed it but it correctly recognized 6 buttons. So all is well. Thanks everyone, for the help. mark
-
Keypadlinc 6 to 8 button
That should have been my next question - what would ISY recognize it as. I guess you're saying that it sends a different ID depending on how it's configured. It would be a lot more convenient to have it just be recognized as a 6 so that I can directly replace it in ISY. Thanks again. [edit above] in my previous post I wrote that 3 ISY devices had failed. I meant to say '3 Insteon devices had failed'
-
Keypadlinc 6 to 8 button
Thank you - will give it a try. The new ones don't come with a manual the way the old ones did and I wasn't clear on whether the old steps would still work. Will give it a go. For some reason I had 3 ISY devices fail in the last month - things had been going along pretty good for a year or two with no failures so this caught me off guard.
-
Keypadlinc 6 to 8 button
Admittedly I'm being lazy here but often there is nuance in these devices so I'm asking. When I first started using KPL's you could convert them between 6 and 8 button. They've stopped coming with both plates now and are sold separately. I have an older 6 button that has failed. I have a new in box 8 button that I'd like to replace it with. I wouldn't care about the extra buttons except for that I had engraved custom buttons made for the 6 that won't fit the 8. Does anyone know if it's still possible to convert an 8 to a 6 programmatically? Or has that been discontinued? Thanks
-
What does this mean
That seems possible too. It's the response I always get, though, and I have some 27 network resources that I test out all the time. One would think that I'd get variations of HT, HTT, and all sorts of truncated responses if that was what was happening. But it's always just HT. It doesn't bother me - it works fine. I have a 1500ms timeout - which I thought was excessive. Do you think upping it even higher might get the rest of the response?
-
What does this mean
Not sure.... I only send network resources to tasker via autoremote and I've only ever received the HT response. I have nothing to compare it to
-
What does this mean
You got it. My network resources temporarily stopped working so I went in to the configuration screen and tested the one that I was suspicious of. A normal response looks like this but for a few hours I was getting that other message instead of the HT message. I was getting it with every resource, not just the one I was looking into. I rebooted the ISY and my laptop as well but it persisted. A few hours later it went back to normal. I think the website that the resources were being sent to had some issues.
-
What does this mean
Funny - when I get that message I don't get success. The message doesn't get sent - or at least it doesn't get received at the other end. When I get nothing but an 'HT' then I get success. This error message went away after a short time. I had searched it out but only found references to Cross Origin Resource sharing and that's above my paygrade. I speculated that it was a problem with the receiving web page.
-
What does this mean
I started getting this when I send network resources HTTP/1.1 200 OK Access-Control-Al
-
Net Module Rule 9:400
So if I send myself an elk variable using an email customization it works fine. Something like ${elk.zone.1.name} - I can send that to myself with no problem But if I send the same thing via network resource it fails with a 400 error. I can send ${var.1.1} but if I send ${elk.zone.1.name} I get a Net Module Rule 400 error. Any idea why? To send variables I have to leave URL encoding off. If I turn it on then it sends the text ${var.1.1} instead of the value of ${var.1.1}
-
Alexa responding with "I'm not quite sure what went wrong"
Ticket submitted. Thanks
-
Alexa responding with "I'm not quite sure what went wrong"
My issue with google home has been going on for weeks.
-
Sorry, it looks like Universal Devices is unavailable right now
Thanks - I'll go check it out.
-
Sorry, it looks like Universal Devices is unavailable right now
This message has been driving me mental. It started about a month ago. My ISY is linked to my portal account fine. I've unlinked and relinked Universal Devices to my Google Home account any number of times. I've restarted my google home devices multiple times. I've confirmed that they're connected to the web just fine. Yet whenever I turn a device on or off it does, indeed, turn on/off but I also get the voice message 'Sorry, it looks like Universal Devices is unavailable right now' Any suggestions how to get rid of this?
-
Age of insteon switch
I'm in Canada so unless you got it from Aartech then nope. I got a new M1XEP today that it turns out I didn't need. Gotta ship that back. Got a new switchlinc today to fix a failed one and when I went to do that I realized it was on a light I seldom use so I just put a regular switch on it. I'm looking at some $400 in parts I have no use for lol. Aartech is usually good to deal with but I'm gonna have to pay to ship it back. mark
-
Age of insteon switch
That seems reasonable. I have a brand new switchlinc and it's number is 4118 - 41st week of 2018 I suppose. I looked and I have a brand new KPL I have yet to install from some time ago - still in the box labeled 4216 - so 42nd week of 2016. Thanks - that seems to fit. mark
-
Age of insteon switch
As I replace some of my original switches that have failed I find myself wondering just how old they are. I've had Insteon in the house for some 15 or more years. I removed one today that is a Switchlinc V2 #2476D. There is a small number on the label that says 0713 under the 2476D designation. There's another sticker that says V3.1 00618 and the insteon address on it is 0A.54.08 Is there a way to determine how old this is? Thanks!
-
Repair of 2413S PLM When the Power Supply Fails
Interesting. I hope that works and that the failure isn't just poor design. Having had Insteon devices from day zero I have a box full of failed PLM's, Filters, KPLs, SwitchLinc relays, dimmers, outdoor switchlincs and on and on. They're definitely far more robust now than their early products. The dual band are a big improvement too. Good luck!
-
Repair of 2413S PLM When the Power Supply Fails
Sadly no love from my dead EZFlora. Ahh well - it was worth a try. Thanks much for all the help. mark
-
Repair of 2413S PLM When the Power Supply Fails
Thanks Brian, I'll give it a go in the morning and hopefully I'll see a green LED again Much appreciated, mark
-
Repair of 2413S PLM When the Power Supply Fails
Thanks Brian, I'll try that this evening and post back. Actually now that you mention soldering to C13 - I should ask about that because C13 - was a problem for me as well. It it appeared to me to be connected to one end of the surface mount component labeled C14 adjacent to it and so I jumped them together. Was I correct to do so? If not I have no C13 - connection either lol. I'm glad you explained why this happened (ground plane in the center). I've desoldered quite a few things over the years and have generally had a higher success rate than I had with this one lol. Mark