paulbates

Yes, factory reset as jrainey suggests... search the web for the brand and model of your router + "manual pdf".. that should get you the manual.... then search that for the factory reset directions. If you can't find factory reset directions and you don't see them when looking at the routers configuration page.. you might have to go through the menus and delete specific configurations you might have made (if you did). Probably the most important things to delete are firewall rules / ports opened static dhcp assignments (where you gave your network devices a specific local IP address every time)... and logs.. logs will have a lot info about your network's history / behavior If any of those things apply to you and you can't factory reset for some reason, go and find those items under the configuration pages and manually delete if possible. You're on the right track.. factory reset any network devices you replace, hard drives etc. Or destroy if that's possible Paul

A couple of things potentially going on at the same time: For the PC & java, did you clear your java cache when upgrading java < I'd start with this to see if you can get the AC working normally. Any messages about "safe mode" coming up? You didn't mention it so I'll guess no Did you try bringing the system up with no PLM? (you'll get safe mode... that's expected with no plm) Paul

Hi Ben What you described in your setup will allow the iolinc to receive Insteon signals, but I would not expect it to change how many 'all on's you're experiencing. The 'all on' travels via RF as well. The 'all on' is considered less about random noise or powerline problems and more about Insteon message collisions. Collisions are considered to be caused by interactions of how ISY programs are written and interact with certain Insteon devices. Here is UDIs recommendation for writing ISY programs so that 'All ons' are either minimized or eliminated. This could be any ISY program, especially those that interact with wireless sensors. Paul

Insteon devices can be sensitive to line noise. So even if the openers are creating noise only when they're in motion, the effect of the noise might "confusing" the iolincs. Depending where your openers are wired electrically, you might get away with one filterlinc, plugging a small 1 to 2(or 3) power adapter from a hardware store into it, and plugging both openers into that. If the total draw of the openers (whatever the spec for one is * 2) is less than that amount supported by the filterlinc, you might get a filterlinc back in exchange for a $2 adapter. Again, depends if the they both plug in to the same outlet nearby each other.

Do you think the upgrade to 5 and the lack of status line up at about the same point in time? IIRC, the API can be different in places on V5 vs V4. Can you check with the 2 mobile app vendors to see if they support 5? Paul

There are some options to baseline your programs to the actual date: If you want to run the V4 family of ISY Firmware, you can set up the isylink program on an external computer and it can be configured to load month, day and year into separate ISY variables. You can work with that in your program. If you are willing to run the V5 family of ISY Firmware, there are enhancements to its admin console and program/variable features to use month, day and year in variables Paul

Jeff Correct. Insteon is a packet based, digital network, but its is not internet (based on the devices you buy from SmartLabs).. there's no bridging/routing translation from the ISY / PLM from internet to the Insteon network. So that diagnosis makes sense... the ISY can talk through the PLM to generate insteon network messages that work.. but the ISY can not talk to the internet to connect to the hub for the things that the hub supports. Paul

No problem... Didn't see initially that you are a new user, welcome to the UDI Forums! Let us know if it gets resolved or if we can help more. DNS is a pretty specific error... is your ISY DNS configured the way you meant? Paul

No changes to your internet or router? If you log into the Admin Console and go to the system tab you'll see Clock at the top. There is a Synchronize Now button for syncing your ISY with the its NTP server. If you press the button and get an error, that means your ISY can't see the internet. Give that a try and we can go from there based on the result. Paul

Hi Sandry The ISY can't receive data from an external source directly. It requires a "middleman" host and application: Write a program that parses the XML and pushes it into the the ISY using V4 or V5 variables via the rest API. Note that decimal data is not supported by V4 and data has to be multiplied (by a multiple of 10) before pushing into the ISY If you have V5, ask for help in the Polyglot and Nodelink section of the forum in having a nodeserver written for this. Its possible that a polyglot developer or io_guy (nodelink) will add this capability to the growing number of supported devices. Your application looks one way, device->isy, and fairly straight forward. V5 handles decimal numbers. Paul

My understanding is that its ISY only, but for reason. There is a staggeringly long thread here on the forums about it. I don't anyone has done a poll, but my interpretation is that some ISY Insteon users have seen it and its mostly associated with the ISY processing event from wireless devices like motion sensors that send their messages twice. Motion sensor sends a message> ISY receives that message and > ISy sends another insteon command like turning on lights.. at the exact moment that... > Motion sensor sends its second copy of the same On... collision. Michel has published specific directions about avoiding that and I've always followed it. My interpretation is also that a majority of ISY Insteon users, like me, have not had it happen. To me, what happened to you was directly attributable to the HomeSeer/ISY interface issue and was resolved. Is there a lingering risk, sure. But how long have you had your ISY before this even and no All On problems? Paul

Ben That topic has been kicked around here but I don't know that I saw anyone verify that there is a newer iolincs don't respond to the all-on message. They remain a single band device. The manual doesn't address the all on, but none of the manuals do for things like switchlincs where it has been addressed. My guess is that its probably addressed, but in reality I don't know. Many of my +50 devices are older ( 7 - 10 years old) and include 3 iolincs, but I've not had an all on so I've not addressed it. Here is a Smarthome thread about this topic. Paul

To add to Michael's spot on assessment.. Your PLM was transmitting 2 messages / sec. That's a broadcast storm that saturates the powerline with little room for anything else, all in with latency and acknowledgements. There were no acknowledgements back from the ISY scene messages. However, if other devices, especially wireless devices like motion sensors, door sensors or especially thermostats were transmitting messages (they double transmit in some cases); those find their way onto the powerline and the likelihood of an "all on" from colliding messages is about as high as it gets. And those devices typically send device-device messages or scenes that all do get acknowledgements, which would very likely get blocked and create 3 retries when the saturated powerline can't cope with the broadcast storm. That gets ugly pretty quickly Paul

I have 2 iolincs in my garage. About the same age, plugged in side by side, one for the garage door and one for a hydreon rain sensor. I had a similar problem with one of them, had to query etc. They are not dual band, just powerline only. As techman indicated, I had an extra access point and plugged it in the garage circuit with line-of-site to some dualband switches in the house. According to manual, the iolinc remains an rev 1 protocol device, meaning that an older access point can solve this problem if you have one in a spares box. Or, plug a lamplinc, range extender etc in instead. I did that probably 4 years ago and that was the end of it Paul

Sean I'd recommend putting a additional short post over in Nodelink with Nodelink, Generac and V5 as tags, and simply point a link back here. That way those looking through nodelink will find it. That's a likely place they'd start. The post does belong here, but its very well written and helpful to the Nodelink crowd as well Thank you for taking the time for a thorough "how to". Nice job! Paul

Not sure this one is written down however its straightforward logic. If the condition is fully true or fully false, the program folder is solid green for true and red for false. In some cases, the use of multiple conditions may make the folder true or false, but only partially. That's what the band means. Its associated with "Or" being in your conditions somewhere If your folder has multiple conditions with "Ors", double check the overall conditions. Mine are consistently red when they're false and green when true. See the example: The month is march, so its overall true, but its not the other months, so not all the conditions are true.. so a green stripe. Can you share an image of your folder conditions? That will help Here is an example I have: The blue line shows a folder conditions for allowing programs in the "Humidity Frost Control" folder to run protect my windows from internal frosting by controlling humidity and only run in winter months. Since its March and one of the allowed months, its a partial green... its currently one of those months (but it can't be all of them) The black lines show the status of programs. One or the other of the program sets needs to run, but not both at the same time. I'm either cycling the fans periodically, or they need to be full on ..only one can be fully true and running. They are coded to be one or the other.. so they are solid colored. (There are 2 thermostats shown, FR for family room and US for upstairs. They are different parts of the house and responding based on sensor input.)

You're right that its there, and it is supported via the ISY Rest Interface https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface#Thermostat_Commands Its either finding an app the uses this information, or creating something , maybe through HAD that uses it. Paul

Eliminating the load is step one. Also, sometimes Insteon switches need to be factory reset. I would probably do the load investigation first, if that yields nothing, factory reset (followed by a restore device) If neither of those helps, I would call it defective Paul

Yeh, got Mike. I get that zoning is more involved and a great opportunity for the ISY to manage comfort. My thermostats use 3 optional remote sensors and added one of those shared for outside, and one each on opposing floor living space for each the two thermostats. I set the associated interior remote for "averaging" with each thermostats onboard sensor, let the thermostats handle it and that got me relatively close to even temp distribution across the house. Did you look at ekeypad? It supports elk as well, but not sure if it solves this particular sensor reporting requirement Paul

I get notifications several times a day that include HVAC activity and temps. I use pushover notifications and the pushover app to get notifications on my phone of key events. Pushover doesn't let me see what the temperature is at any one moment, but I do get notified that key ISY programs are taking action and associated values (indoor temp, outdoor temp, humidity, etc) and alerts when key events or if key thresholds are crossed.. if HVAC is on and indoor temp>74 or indoor temp<60. I can review those messages any time I want. And If I didn't get the messages several times a day I would know that something happened to the ISY or its internet connected. If you are trying to catch temperatures out of range, this is a good "event driven" way to do it, vs checking all of the time. Paul

What is the load being controlled? Based on what you listed, the path heads that way. If you remove or unhook the load, or use some other load, what happens? Paul

It’s a limited interface. To fill in a little more, the communication is effectively one way from the linked first alert to the bridge. Also good to know is that the battery alert works only for the unit linked to, not the others... and it’s not possible to know which smoke/co detector triggered, just that one did. Sent from my iPhone using Tapatalk

You can certainly unplug them and see. I still get use out of one in my garage to extend to 2 iolincs I have out there. It works ok without it, it works perfect with it based on level three diagnostics. Paul

The ISY is extremely powerful for integration with the programs tab. The next closest is probably homeseer. But after 10 years and 3 versions of HS, the ISY is better/easier for me in that regard. My preference is to have published integration points (Nodeservers= Nodelink, polyglot) and not custom coding to maintain for my house. Having moved to V5, I've gotten away with exactly that on the ISY. I do have a pi, but all I did was set it up out of the box, install mono & nodelink and configure... I don't think about it and upgrade it once a year (or every major vulnerability). Both of my kids have graduated and I'm closer to thinking of selling, and keeping the integration at that higher-level will let me sell the integrated active automation (HVAC, Sprinklers, Lighting controls, Attic fan, etc) as a feature that can be turned over to either a techie buyer, or find a support contact for them. Removing coding off of the tech support responsibilities list will make that plausible (eg.. not having to know specifically .net, python, etc..). Things related AV will most likely come with me, and are in their own integration bubble.. eg Harmony-alexa.. a new owner will have their own. Paul

I've had Simplisafe for 2 years. It gets an 8 from me as an integrated alarm system and a 3 for iot integration. The good Easy to install System - works Monitoring - works App - works (pin authentication) Integrated smoke/co Has cameras, I don't use them The bad Bespoke Simplisafe monitoring (COPS).. No Alarm.com, etc Very low level iot. They have tons of requests and long threads asking for iot (IFTTT, Stringify, etc) integration, and 3 years of "we'll ask the team"... I gave up I have a Rube Goldberg machine in gmail to parse their email and IFTTT using maker. I can have my ISY know the state of the system, but can not control it from the ISY. Paul