paulbates

Larry's right. Use Control rather than status. Each time the switch is switched, the 30 minute timer is restarted. Since its a basement, a suggestion is to dim the lights as a 5 minute warning before turning them off, so someone isn't really still in the basement isn't left "in the dark". I do this for second floor stairway lights. If its not dimmer, flash them on and off once or twice as a 5 minute warning Paul

If you followed the procedure for Java, that's the other thing i know of I'd submit a request to UDI and add a link to this post so they can see what you tried Paul

The change to your system you mentioned could be in the firewall/virus software. That can cause the symptoms you are seeing. You address that with the firewall/virus software by letting it accept the ISY as ok to run. Before trying your step 1, look at the firewall/virus package you have and make the suggested changes, before you try to launch the finder/admin console. Paul

Hi Denis Not a problem. Most virus scanning software are very wary of any java app. Take a look at this link and see if it helps Paul

The only caveat is that I've had cases were excessive line noise "confused" even dual band devices. I'm not suggesting a course of action different than lilyoyo, but currently the evidence does not exclude local line noise as a problem.

With the LEDs removed? If the LEDs are creating the noise that could explain it Paul

I know with my togglincs, especially one on the outskirts of my insteon network, ... they can "lose their marbles" and need to be factory reset, and then restored. Like every 3 - 4 years, more often if there is a power outage with brown outs. What you describe can also sometimes indicative of a noisy load problem. If the problem persists across several devices, it could be that. Is it an LED bulb, etc? Paul

Yes.. that's what I've said.... or, hey "what's one more language or OS"? That's why I suggested asking the polyglot folks or io_guy... if you can post the api tech reference from the company, and what you want to see in the ISY, someone may do it as its a value add to the ISY's node portfolio... eg, you will probably not be the only person interested Paul

I've been using it for 2 1/2 years. But I would start by checking the current v4 thread to see if the new sensor basic function work there. I think I've read they do, but not 100% sure.

I meant V5 of ISY firmware versus v4. I've seen comments that the support is a little different for the new sensor on the 2 versions.

I don't think its nefarious.. I think they are heads down on developing their Cloud API, . This "story" doesn't show up on their "backlog". I have to agree that the whole thing is just ridiculous. Its a standalone device with a specific message behavior set. I believe that Insteon firmware still can not be field upgraded... so "it is what it is"... Just tell UDI what "it" is

We have the same issue and litter box is in a bathroom with a fan. I've been considering putting an MS inside the litterbox. Like larry, my MS are all original model and haven't bought one in a while. Since I'm on V5 I'm thinking about getting one of the new ones at Menards. I know there have been trouble with it sending offs and settings... however what I'll do is create a program that sees if its switched on, and then run the fan for 20 minutes and then turns it back off... that will ignore the "off" commands. For this application, I don't care about the options or if I can set them or not Paul

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