MrBill

if you log multiple devices into the same pushover account they are all covered by the single $4.99 fee, and still individually addressable via pushover.... it's the best $4.99 I've spent on home automation...

Log into the portal. Use "Select tool" then select "Occupancy Node Server" and then "Occupancy" you should see a window like this: Click the "Add a Geofence" button at the top. Type your wife's name, when asked to to name it. I also choose to add mine to the "Home" folder. If you didn't create a "home" folder you may want to do that first, having such a folder does the logic for you... i.e. 'away' if all devices are away, 'home' if at least one device is home. I added test: Test immediately populated in my ISY's device tree: Use this button: to get the url's for that row. you can test them by pasting them into a normal browser window. then install them in Locative or whatever app on your wife's phone.

email to text is unreliable. there are a couple hundred threads lately on this very topic. two possibilities: switch to using Pushover. Will take a little bit of a time investment to learn and get things where you want them. This has also been recommended in most threads on the topic. Install a dedicated email client on your phone to use with a specific separate email address, where you can have full notifications enabled. (Spark is a good choice on iOS). This search might help you locate other relevant threads.

I believe Broadlink RM4 Pro speaks at 433Mhz but I'm not sure to all devices. I don't have one to experiment. Many users use konnected.io to utilize older alarm systems.

That sounds like Firmware and UI (i.e. admin console) versions not matching. Are your ISY's at both locations using the same versions? do you use the IoX launcher or local copies of the admin console? Windows or Mac?

I agree with @kzboray , AutoDR is the only scene that's "factory installed" and can't be removed. You can however rename it, I renamed mine "~Auto DR" which drops it to the bottom of the list where it's just ignored.

Home Assistant with both the Universal-Devices integration and the Home Kit integration will allow you to add Insteon and other ISY devices to HomeKit. (note: although the name of the Home Assistant integration includes "ISY994" the integration works with Polisy and eisy, and will continue to work with all UD hardware. The naming convention including ISY994 with Home Assistant will likely be a problem for a long time to come, it will break everyone's existing installs if they suddenly change that.)

Heartbeats are alive and well as far as I know. I believe the program that @Techman posted must be manually started after it's added, or run via a reboot. In my experience it doesn't seem to get started on it's own, but it does seem to refresh the wait as long as it's running... i.e. full green program flag: The program that I've always used on all my wireless devices looks like this: hb.FrontDoor - [ID 0066][Parent 0072] If 'Door Switches / Front Door / Front Door- Heartbeat' is switched On Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched Off Then Wait 24 hours $iDoor.FrontDoor.HBmissed += 1 $iDoor.FrontDoor.HBmissed Init To $iDoor.FrontDoor.HBmissed Wait 2 seconds Resource 'NotificationNS.DoorTrouble.FrontDoor' Run Program 'hb.FrontDoor' (Then Path) Else - No Actions - (To add one, press 'Action') For recessed door sensors the wait is 24 hours as their heart beats every 21 hours if set the the maximum in the device configuration. Leak sensors and surface mount open/close sensors, I use 25 hours for the wait. I track three things for each wireless sensor using integer variables: Missed heartbeats, Battery days, and transmission count. Some sensors seem to randomly miss a heartbeat or two occasionally so I include that info in the notification the ISY sends me via Pushover so that I know if I want to rush to change the battery. The worst sensors for missing random heartbeats seem to be the surface mount open/close sensors, never have figured out why. In the last line of the program, I loop back to the same then body to ensure it's always waiting. this program will start up by itself at the next heartbeat, but should definitly be included in "run at startup" or run during startup by another program. I choose the latter because Daylight Savings time shift will stop programs running, I have a program that detects a DST time shift and restarts all the programs that should always be running... that program is also run at startup. the notification sent looks like this: The battery days program is a just a simple program that runs at 12:12 am (I offset it from midnight by a few minutes just because I've always done offsets when something doesn't absolutely need to occur at midnight to minimize load spikes.) Each time it runs it just adds 1 to all the battery days variables for each device. The transmission count program is included below, but simply counts each type of transmission. It's not really needed but I did it for judging how low the battery in the device might be. All the counters for a device are reset when I change the battery in a device. FrontDoor - [ID 005B][Parent 0033] If 'Door Switches / Front Door' is switched On Or 'Door Switches / Front Door' is switched Off Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched On Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched Off Or 'Door Switches / Front Door / Front Door- Low Bat' is switched On Or 'Door Switches / Front Door / Front Door- Low Bat' is switched Off Then $iDoor.FrontDoor.TransCount += 1 $iDoor.FrontDoor.TransCount Init To $iDoor.FrontDoor.TransCount Else - No Actions - (To add one, press 'Action')

Are you using the same portal username and trying to add a second geofence for another user? or are you using multiple portal usernames? If this, I'm not surprised it doesn't work.

For all the switches in the scene and the one that's not right click them in the device tree and choose "Restore Device", do them one at a time and wait until the ISY is finished before moving on to the next. When you started out fresh did you do it by factory resetting the PLM and each device then adding it to the eisy?

The biggest caveat when upgrading from v4 to V5 is whether the programs use "Adjust Scene". If those programs will require manual intervention. Network resources should be fine after upgrade. If not you can go back to 4.9 while you figure out what needs to happen, just make certain you have a good backup. (to go backward "manually Upgrade" again but load the 4.9 firmware file, you likely won't need to restore the 4.9 backup afterwards.) If any programs are intentionally disabled make not of those, as they will need to be re-disabled after the upgrade. If he has 300 series z-wave (Z-wave version 4.81.00) then 5.0.16C is the last version that supports, 300 series. An un-written step that's helpful is to go to the programs tab, click on "My Programs" or whatever the top level folder is named and then right click and "Copy Folder to clipboard", then paste in Windows Notepad (or any simple editor) that won't try to add formatting, and Save As..... This gives you a reference copy of your programs should one need fixing later. After upgrade do two things immediately, Open the admin console, then: Check Help > About to make sure UI and Firmware version match. If they don't solve that before doing anything else. This must be correct before #2... or #2 will give invalid results. Navigate to the programs tab > Summary sub-tab and look for the color YELLOW. If you find any that program needs manual intervention and most likely has "Adjust Scene". Then disable any programs intentionally disabled and you should be done. Good luck, let us know if you have an issue.

newer devices seem to to detect network changes and ask for a new IP via DHCP much sooner. ISY994's will eventually but you'll likely get tired of waiting. Not sure how Polisy/eisy behaves in that sense...

Have you restarted the ISY since the new router? If there is no static assignment in the ISY that should get it a new IP in the new range via DHCP.

are you using the same address block on old vs new router? such as 192.168.x.y is x the same? on both? or is your new router using 10.10.x.y vs 192.168.x.y? Did you have your ISY configured to use a static IP address? Can you see your ISY listed in the device table of the router? do you know if it's getting an IP address? What model is the older router? What model is the new router?

Help > About... do the firmware and UI versions match? If so, open a ticket... https://www.universal-devices.com/my-tickets/

can confirm. I had AT&T for 20 years and thought AT&T was bad at delivering emailed text messages. Switched to Verizon a few months ago and tested (actually I have a permanent test message sent at 12 noon everyday), I've found that Verizon is FAR worse than AT&T. I highly recommend Pushover (although I haven't tried UD mobile Push notifications). There's several methods to get a message sent via Pushover from basic Network Resources to the Notification Node Server and more. Pushover is almost free, pay once for the app ($4.99) and no monthly fees.

Yep... you restore a 994 backup in eisy. The answer can get more complicated based on insteon PLMs and z-wave devices and z-wave thinks is the controller.

then you didn't remove them from scene's. Further more if you have an All off button that included the switch the change may need to write too all all buttons. removing something from a button means that you are deleting a relationship with a scene.

Assuming the switch is still hooked up, you would want to remove the devices from the scenes they are included in included in, then delete the device no longer in use. If the switch is not still hooked up it would be best to use a pigtail cord so that you can hook it up and then remove the links. Don't worry too much about what the ISY updates, it knows what it needs to do.

@PapaBear if you power cycled your comcast modem and that is also your router, you may need to power cycle your UD device. The IP address UD was using may not still be available, you may need to force it to get a new IP address. In the future don't power cycle comcast when you update a UD device, it shouldn't be needed.

i've never seen one.. I just leave stuff out. I was surprised the night i discovered timer language can be quite terse.

off topic chatter: When setting timers you can omit a lot.... Try "Alexa, 5 minutes"

But are you turning on the SCENE with Alexa association (same for programs)? Turning on one of the controllers via alexa/program will not turn on the scene. The scene itself must be told to turn on. the "Controller" designation only applies when the switch or button is operates locally.

when you clear the cache are you checking the box "Installed Applications and applets" if not, please try that.

That might work but it's a band-aid, and not the correct solution. the first time start.jnlp run it should install an icon on the desktop that calls javaws the properties of the icon should look something like: "C:\Program Files\Java\jre1.8.0_351\bin\javaws.exe" -localfile -J-Djnlp.application.href=https://isy.universal-devices.com/launcher/isy.jnlp "C:\Users\bill\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\14\7f87040e-61f20201"