telljcl

Very good to know - thanks!

Thank you - excellent!

I do have an ELK, and have various sensors etc... driving ISY programs, so this could certainly be an issue. I don't have ELK providing any voice feedback though, other than programs residing solely on ELK. I've got a lot to learn here apparently, so I'll appeal again for any basic links on how to convert over to Polisy and away from the ISY. My system consists mainly of Insteon, with Zwave where there was no alternative (locks, a few watt-counting modules), an ELK (alarm features plus controls some valves, garage doors, etc...) and Alexa integration via the ISY portal. So I'll need to figure out how to put all of this together on the Polisy some how. Thanks for all the detailed responses provided here!

Yes indeed - it helps a lot! Thank you for taking the time to post it!

It does appear to me that Insteon is down and/or out, but I always defer to experts on the forum such as yourself. I'm asking for information here, not trying to supply it to others in this case, because, as you point out, I don't know much about it. So, no, I don't want to move on to bigger and better things as you mention, just trying to get a handle on the current landscape and learn what I can do with my present system (which works pretty well, as I mentioned), or learn what options are available should I not be able to replace failing modules etc... Could you be so kind as to point me to a resource link for running "ISY" on the Polisy, restoring a ISY backup to it, and then using my 2413s (or my spare which I re-capped some time ago) with it?

I used to use "Venlink" for PC, then I think "ioguy", IIRC, changed it to "Nodelink", which I still use on PC, but I read off and on about issues with using it with Polisy, and why ioguy said he was running into issues, but apparently that has been rectified - good to know for sure. As far as "ISY on Polisy" - what does this mean? Can I replace the ISY with Polisy, and still use programs etc? If this is possible, is there a way to use another PLM instead of the 2413s (I think that is the one), since they are hard to come by and apparently also discontinued? Sorry for basic questions - my system has actually been running pretty well for years now (excepting zwave wonkiness) so haven't been keeping up. Thank you

I have a large number of insteon devices, and have been using it since it's inception - 15 years maybe? Don't have many spares left in my inventory, either. ZW has been very hit and miss for me (mostly miss - I have the ZW500 board in my 994) and I don't think that is a viable alternative as my Insteon devices die off. I bought a Polisy when they came out to run an app to control my Venstar T.Stats instead of running it on my PC, but the app never came out for Polisy so I haven't used it. So - what is the future, if any, for ISY / Insteon / Polisy? I see something about running ISY FW on the Polisy? I'm way out of the loop I guess, so any help bringing me to the present WRT the whole situation would be appreciated. Thank you in advance.

Fixed as of this morning and working like it did before.

Any ideas on how to report this to Amazon where somebody will actually be able to fix it back like it was? Thanks

Yep - that's it.

Thanks - at least I know it isn't on my end only. Tried the "open / close" but forgot it doesn't work quite the same way so that's a no go...

Still doing the same thing... Thought Amazon might resolve, but hasn't happened. Will try changing from a "raise / lower' to an "open / close" and see if it is any different... The value and state is always correct when looking at the Alexa app (or of course within the ISY), but verbal responses from Alexa when she calls the variable by name are what is corrupted.

Thanks for your response. Yes, device state is correct within Alexa app, and the name is normal as well. I've tried renaming it to something different, then back, and as mentioned, deleted it all from Alexa and ISY portal and re-added it all back - no change. I hadn't changed anything when it started adding all these characters after the correct name of the device. About 3 or 4 days ago it started. Anyone else seeing a similar issue?

Venstars have inputs for std. 10K thermistor remote sensors, as well as options to use wifi remote sensors which also have onboard and remote thermistor terminals. I suppose this would work? One thing I like about the venstars - they are very configurable - deadbands, #stages, temp. calibrations, remote sensor capable etc... I'm not against using something else, but just hadn't even considered using more of what I already have.

Thanks very much for the details. I'm new to floor heat, but it looks pretty simple as it's just 120 or 240 on / off with a sensor in the floor somewhere. I have Venstars for my HVAC units, and I like the way those work (local control via ISY (thanks to @ioguy) as well as internet / app). I didn't think about using those, but I guess it wouldn't be too difficult and in fact would be nice not to have to route line and load voltage through the thermostat's physical location. Could just put some 24v coil relays in to control floor zones I guess?

I have a state variable that I ask Alexa the value of, and also tell her to set, which has worked perfectly for quite some time. It is set as a "raise lower" device in the ISY portal, with 0 being "off" and 100 being "on". I can say "What is xxxxx set to" or say "Set xxxxx to 85", and it worked perfectly. A few days ago she started saying: xxxxx (the expected name) and then about 10 seconds of various characters and symbols read one at a time, very fast, then the percentage the variable is set to at the end. Deleted the variable from Alexa, also from ISY portal, added back, still same thing. The value is reported or recorded into the ISY just fine, but Alexa reads it aloud with a gibberish description after the actual name I have it called in Alexa / ISY. Any thoughts on why this is all of a sudden happening? Thanks!

I realize this is an older thread but was wondering if there is anything new - either with the work that @simplextech has done with the NUheat or clone thermostats or other (hopefully local) systems that will play nicely with ISY and / or Polisy? Getting ready to do a fairly involved renovation and looking at the best way to automate / monitor / integrate floor heat with my ISY and connected devices. Thanks!

Great ideas! Thanks for the varied approach solutions. I haven't gotten into Arduino (too many boxes, servers, interfaces, adapters, bridges... already - just can't get excited about learning another one), so that is above my pay grade at the moment. The @KeviNH suggestion looks close to what I was thinking. I have an Aeotec multisensor but it seems to pretend it is there even when I unplug it, WRT queries from the ISY. Maybe I need to experiment further with it. I have Zooz relay ZW box that does report as "gone" if I unplug it, but that is a larger more power hungry box for this purpose. I'll try the syntax used in the example. Regarding @larryllix's I/O lincs and garage doors, I already have ELK sensors on each door, so I know when they open and close etc... so predictively I can be fairly certain of what's going on using the timing of opening and closing of a particular one, but for various reasons I want to be more sure.

Want to be able to know if a specific vehicle is there or not. Seems like a wireless (zw or insteon?) Device in the vehicle where I could check "is responding " in a program, (since if car is gone it would be out of range) would work but zw devices I have don't seem to work with the "is responding" function. I'm sure there must be something easy I'm missing? Thanks for any help.

I hate z-wave, but have it to accommodate some locks and now this high amperage switch. I want to replace a non-HD Aeotec power-monitoring switch in the same location with this one. I can add this switch no problem from my desk (near the ISY), but it won't work when located where it can't be directly reached from the ISY itself. Most of my locks and several other Zwave devices are actuated via a number of Aeotec repeaters or other ZW switches acting as repeaters, since they are distant. I tried pairing the device from a distant location where other zwave items work, but it won't communicate from there through the mesh back to the ISY. When adding the Aeotec HD switch when near the ISY, the ISY gives me a message (after the pairing starts) about needing to switch on "secure adding" and then turning it back off after pairing, which I've done. It won't pair w/out doing this. If there is a way to force the Aeotec HD switch to pair to the ISY in non-secure mode I haven't found it - apparently it only will pair in secure mode? I guess I could try deleting my repeaters and re-pairing to the ISY in secure mode, but they barely work as is, and I've heard secure slows things down even more and reduces the already miniscule range. I'm out of ideas. Any suggestions? Thanks!

Thanks Michel - I'll check level 3 event viewer, but only programs I see running "Then" are ones that are supposed to be. As far as I can tell, anyway. It takes a while of ISY "Up time" before this issue arises.

Not sure at all what's going on, but to my knowledge nothing about my setup has changed. Noticed Alexa / Portal was not working a few days ago, but that has since started working again, but around the same time I noticed my ISY is not communicating with Nodelink. No ip addresses etc... have changed. It seems the ISY gets "busy" with something after it's been running awhile after reboot, and eventually (takes hours to maybe a half day to get to this point) begins refusing communication from things like Nodelink. The ISY itself gets very sluggish responding to things, if at all, and if you bring up Admin Console it says "busy" at the bottom continually. Any ideas on what could be going on? I'm on the latest 5.0.16c, and have been for months. When first booting ISY and then launching Admin Console, it takes about 5 minutes for the ISY to finish being "busy" (checking device states?) then seems to work properly ("busy" at bottom left not lit, says "ready".... for awhile, anyway, before the above happens). I"m not sure it always took this long on boot, but maybe. I know when I first click the "programs" tab, it takes about 45 seconds to load that page, but I have a lot of programs. That's nothing new. FWIW I have a Polisy, and one test node I put on it that the ISY communicates with, but I don't use it and it isn't in any programs or otherwise used. Was hoping Nodelink would run on Polisy but that doesn't look to be happening - don't really have a use for it so perhaps I should delete node and shut down Polisy, but it has been in this configuration for months. Thanks!

Good to know - thanks for the clarification. I wish it was possible to replace dimmers with on/off and vice versa (in those cases where you weren't using the dimming function), but I could see the issues which could arise in programs, but if you replaced an 8 button with a 6 I could see similar problems (but maybe you can't - I did 6>>8).

Makes sense, but usually the option box won't show devices that aren't the same (like replacing a plug in dimmer module with a plug in on/off module). Since it showed up in the list of devices that were "OK" to replace it with, I assumed it was OK, but maybe you're right and I should just delete and reinstall. Don't have much in the way of interconnectivity with that device.

An old 6 button keypadlinc finally went out, and via the Admin Console I added the new 8 button, then used "replace with" to replace 6 button with the 8 button I just added to the system. All seems to work, but my 8 button KPL is now showing as a 6 in Admin console. Any way to add the missing 2 buttons for a total of 8? Thanks!