paulbates

VLANs can have the same effect. The discovery packet is not IP, so IP routers will drop it.

The purpose of the finder is to locate the ISY by a non IP ethernet frame using a very standard method. For this feature to work, the ISY and the PC using the admin console have to be on the same subnet eg 192.168.0.x. The finder sends the magix , the ISY on the same subnet should see it and respond. If that's not happening, something's not right network wise. If I access the ISY from the outside of my house, I run into needing to manually enter its address in the finder and save it. A couple of things to do: An appliance type device like the ISY should always maintain the same IP address. You can set a static IP address in the ISY under the admin console / configuration. Or... most routers allow you too assign IP addresses to specific devices via DHCP, so they always have the same. I suggest you do the router method, as you have an existing network of IP addresses and there's a change you could pick one that's taken... had to remedy that if it happens You shouldn't have to, but you can save the address of the ISY in the finder. If you set the address (first bullet above), and a blank finder window pops up and you enter the manual address... press the save button right away. Brian's suggestion above, to use the launcher... it pauses when it first comes up making it easier to enter and save your address the first time To your point, its odd that this is happening. If the ISY and pc are on the same subnet, it should not happen, its using a very basic ethernet feature. Paul

If I understand correctly, there are 2 approaches but I think only one will work Make each participant a controller in the scene. I don't think this will work All have to be controller capable... not all older plug in modules are (doesn't look like you have any) Complicated by plug in modules where whatever's plugged in gets physically turned off (again, only if plug in modules were added in the future) A device can only be a controller in one scene.. not workable if devices are shared across the different groups you have Turning any device on turns them all on In summary... its an approach but I don't see it working the way you want, unless there are other ideas suggested Write programs for each group: If DR Pen BF Foyer is switched on or DR Pendant - BF - Din is switched on or ..... (add all the rest of the partcipants) Then Set <keypad key> on This will likely do what you want, again if i understand the requirement. You can also write an additional program that uses Status instead of Switched/Control, also use AND instead of OR for each participant.... it would catch all participants being turned off and turn the keypad key off Paul

Its a warning message, not necessarily a problem. To @jec6613 's point, it shouldn't be a problem if your BD router and internal network devices are safe and properly secured. Two choices: Go into the Admin Console and disable port 80 / http: on the ISY and the warning will go away.... but, as pointed out.. it puts a load on the ISY slowing everything down. Opening the admin console will take a long time and it will operate slowly. For grins and giggles, last year I tried running my V5 nodeservers on SSL inside of my LAN. I got sluggish performance and performance/time out warnings from my nodeservers. I reverted to http port 80 for internal communications. Ignore the warning and be sure not route anything outside of your house on port 80. Route as little a possible outside of your house at all, even on https: port 443. I have zero ports open to the outside and use the ISY Portal for access. Paul

UDI is coming out with a device in the fall, Polisy, that will provide a device ready-to-go as the nodeserver host.. I’d think about that. Paul

Eric Its a core capability of V5 that allows modern network appliance type devices like sprinkler controllers, thermostats, rumbas, cars, etc.... intergrate with the ISY. Network Applicance <-> Nodeserver Device (e.g. Raspberry Pi) <-> ISY. If you look in the UDI Forums under polyglot or Automationshack / Nodelink, you'll see all sorts of devices that can integrate with the ISY via nodeservers Paul

Awesome that you upgraded well! For the passwords... admin is just your local admin account and passwords. The others (1-9)are related to nodeservers... I haven't needed to use them yet. Paul

The S in the product number means its a relay. I have one of these (2466S) and it only presents on/off/responding for Status in a program. I would delete and readd the switch as recommended by oberkc. Paul

Yeh, can't explain that one. You should open a ticket with UDI and provide a link to this thread. Paul

If its an insteon dimmer then it will be 0 - 100% status. In the case of your program, you'll want it to be 0% = off. Not sure why that changed now. Paul

My recollection is that the little triangle option for variables showed up in V5... been a while though. Definitely do not attempt remotely. I would suggest waiting till the first part of the weekend or when you have a couple of day period free to make sure nothing breaks (even though that's unlikely). My system has become "production" over the years and I can't risk the phone calls at work if something were to happen. Paul

Eric Its been good, I've been on it almost 4 years (I started on an original alpha). Some if it depends on your technology mix. I was insteon only and don't do a lot of direct control with scenes. I've observed that programs that control scenes and some z-wave devices can take a little more effort to migrate. The biggest thing is backups... start with a clean backup of your current V4 setup before you attempt to migrate. Then once you migrate, don't start new programs (like the above) even though its tempting. Give everything at least a few days to make sure its working and all programs have run. Then once it looks like you migrated what you had successfully, move on to updating programs. The reason is, any changes you make to your ISY on V5 can not be backwards migrated to V4, if you were to decide you didn't like V5. However most people who have migrated to V5 have been good with it and moved on. Paul

Eric Which version of ISY Firmware family do you have, V5 or V4? I think some of the features that the other members are mentioning may be limited to to V5 Paul

There's a little bit of a learning curve, but another option is a notification service like pushover. The assoicated apps let you file notifications in folders you define ... security, hvac, irrigation, etc. Normally notifications are almost instant, the longest is <10 seconds that I can observe. It saves clogging up your email and texts as well. Once you have the basic Network Resource setup, its a copy/paste + new text to make a new one, and replace a line in the ISY program. Others here got me started on pushover and I'm very happy with it. Paul

Ok. The device looks ok and it doesn't make sense that the program would switch query back and forth with status. The only other option I can think of is disabling the program, and completely recreating it, eg... it sounds like something is wrong with the content of the program within the ISY. If that works, delete the original, disabled program. I see what you're doing with the device status, by running a separate program, it will ensure that the delay and off are run.

Is the device Insteon, Z-wave or ? Does the switch seem to function correctly when you turn it on and off from the admin console? What happens if you query t a few times from the admin console (leaving 3 - 5 seconds between retries)? It could be a device or communications problem. Edit: Turn on the event viewer when trying the on/off and query above (Tools/Diagnostics/Event viewer... set to level 3 device communications)... any errors? Post results here. Also, while you should figure out what's going on, you can probably get rid of that statement. Since the sensor and program could retrigger while the light is on already from a previous run of the program, its not clear that the statement is affecting how the program performs.

Yes, but historically its known for reliability problems like you are seeing. That's why the suggestion is to move to forward through your gmail account. One of the things you have to do with your gmail is go to the account and set it for "allow less secure apps" or it won't allow the ISY to proxy through it. I don't know if this was suggested above or not, but this is how I used notifications through my gmail account and I had to set it Paul

Ok great. Another thing is making sure that the "Use Default" box on the SMTP settings dialouge got unchecked. Paul

After you deleted the line, do you press "Save Changes" on the left before re-adding it? I would try that.... and press "Save Changes" again after re-adding it. Paul

The launcher matches the UI to the firmware version. I agree that it seems odd that if you are 4.7.0 the ac is a different version. But my suggestion is to follow Michel's directions as written... one of the goals should be to getting to the latest FW. Paul

Ok. One of Michel's steps was to update the firmware to the latest 4.7.3 after installing the launcher (with the UD icon) and making a backup of the ISY. Paul

Your firmware is 4.7.3 and admin console is 4.6.2? I would close the admin console, clear java cache and run the launcher again Paul

When you see your ISY come up in the finder, are you getting a choice between launching the admin console or dashboard? Paul

My suggestion is to open a ticket with this information and UDI will work something out with you that you'll be happy with Paul

Hi My suggestion is that you post this in the mobilinc section of the forum so that Wes (InsteonNut) will see it. There are some additional questions to answer too: which version of moblinc (X), and how you are using your geofence: which portal (ISY or mobilinc) you're using (if any), was it working previously and then stopped? is the ISY varable a state variable?