-
Posts
730 -
Joined
-
Last visited
Everything posted by MarkJames
-
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.
-
Well - that would be kind of mean. Leaving new owners with a problem that I know about. I wouldn't feel right doing that.
-
They are the same - yes. But that's not going to help long term if they cease production
-
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
-
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
-
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'
-
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.
-
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
-
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?
-
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
-
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.
-
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.
-
I started getting this when I send network resources HTTP/1.1 200 OK Access-Control-Al
-
Thanks. I just found it - it's been moved into a zip file with the ISY WSDK on the developers page. Thanks for trying, though
-
I had a file that I think I downloaded from somewhere on the UDI wiki that documented all the different values that the Elk returns for its status. The values are all numeric by type and indicate things like 'armed away', 'armed stay', 'entrance delay active' etc. I had stored this file on my QNAP but I got hit by the Qlocker ransomware attack a few weeks ago and lost it. I've searched and searched but can't find it. Any idea where I can find this?
-
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"
MarkJames replied to sdcrane's topic in Amazon Echo
Ticket submitted. Thanks -
Alexa responding with "I'm not quite sure what went wrong"
MarkJames replied to sdcrane's topic in Amazon Echo
My issue with google home has been going on for weeks. -
Thanks - I'll go check it out.
-
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?
-
Thank you.
-
I'm lusting after setting up a nodeserver but I'm also in the midst of deciding on whether we are going to sell our home. I've spent the last 24 years automating and re-automating and re-automating again to where it's a complex entanglement of a custom Java web page contorlling Elk, Sonos, ISY, Ecobee, Nuheat and Insteon managed by ISY and Homeseer along with some automation routines internal to the Elk. My wife always kids that if I die she'd have to sell the house because she doesn't know how any of it works. If we're going to sell I really need to simplify things for the next owner and adding PolISY is probably not the right step for me right now.
-
Thanks Dennis, I'll try that out. Hopefully this also brings it to the attention of the ISY team so they can address it. It's probably a feature that so few of us use that it got missed. [edit] Confirmed - that works perfectly. Thank you!
-
same result - sorry. The table is HTML so I c/p just one row and highlighted the substituted variables. Ignore columns 2,3,4 - they're ISY variables for my own use </tr> <tr style='height:8.95pt'> <td width=162 valign=top style='width:121.25pt;border:solid windowtext 1.0pt; border-top:none;padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'>${elk.area.2.name}</p> </td> <td width=79 valign=top style='width:59.55pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'>${var.2.13}</p> </td> <td width=89 valign=top style='width:66.4pt;border-top:none;border-left:none; border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'> </p> </td> <td width=89 valign=top style='width:66.4pt;border-top:none;border-left:none; border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'>Always</p> </td> <td width=165 valign=top style='width:123.45pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'>${elk.area.2.alarmStatus}</p> </td> <td width=165 valign=top style='width:123.95pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; padding:0in 5.4pt 0in 5.4pt;height:8.95pt'> <p class=MsoNormal style='margin-bottom:0in;line-height:normal'>${elk.area.2.armUpState}</p> </td>
-