MrBill

Does your ISY have z-wave? If so, do you have any other z-wave devices? What firmware version are you using with your ISY?

I don't know of one, someone else might. The basic concept is this: Your Device tree currently consists of nodes that are mostly contained within the ISY for Insteon Devices, Z-wave Devices, and scenes. Node servers allow you to add other types of nodes, for example temperatures, garage door operators, Sprinkler zones, thermostats etc. If your ISY is on version 5.x and you have a portal subscription you have access to the Polyglot Cloud Nodeservers. so you can try a few out to get the hang of it. Log into your portal account at https://my.isy.io and look for the Open Polyglot tab in the far upper right corner of the page. That will open a new window and you can click Store to see the nodeservers offered in the cloud. Click the name of the nodeserver for more info. Try out a few. If the admin console is open when you install a nodeserver you MUST close it and reopen it before the node or nodes will appear. There are also a much greater list of nodeservers that will only run locally. The polyglot 2 store can be viewed here: https://polyglot.universal-devices.com/ but those need to be installed on local hardware. Polyglot2 can be run on a Raspberry Pi or UDI's Polisy. Polyglot 2 however is about to start to be phased out as Polyglot 3 is about to be released. Polyglot 3 will ONLY run on UDI's Polisy hardware (no more raspberry pi support). Polisy is also soon to run ISY software, meaning that the 994 hardware will be getting phased out as well. (don't panic the 994 is solid and will be supported for a very long time)... but if your reading along, the future of the ISY is Polisy which will run both the local nodeservers AND the ISY software all in the same box. Why are some nodeservers cloud, local or offered both places? The Cloud versions can't directly access hardware on your local network (other than the ISY via portal) these are mostly nodservers that log into or obtain there information from other cloud sources. Local nodeservers (Polisy) can talk to other hardware on your local network directly. Some nodeservers can work either place. For best experience with nodeservers make sure your ISY is upgraded the v5.3.4 (or 5.0.16C if you have a 300 Series z-wave board) before you start. (More details available for this sentence if asked.)

Mine are temps from two nodeservers... wirelesstags and MeteobridgeAuth. I don't have those nodes exposed to HA itself, because it adds alot of other values that I don't need HA to know about. So instead I use ISY programs to store the values in integer variables each time they change.. those variables are marked for for export to HA. Bottom line anytime they change they get updated because they changed. I'll let @Javi explain the UD Mobile answer, which is a more direct route. I have and use UD mobile for things I don't have previously configured in HA, I don't use it enough to explain in detail tho.

While @Michel Kohanim has suggested in similar situations to delete the file, I don't know if it was the same type of file or the same path. Would any file that erred during backup be OK to delete? I don't think its a questions forum member can answer. I've read this forum everyday since 2016 and I don't have anything in my bookmarks to use as a reference for this particular problem. My vote would be that you open a ticket by email support@universal-devices.com and ask this question. Don't worry this won't hold you up long... UDI support typically answers very quickly.

Class 10 used to the rating to look for... now it's the newer Application Performance Class A1 or A2 (which will also have a class 10 rating), A2 requires hardware support (which Pi4 does provide) A1 does not. https://www.sdcard.org/developers/sd-standard-overview/application-performance-class/

I purchased the 4gb version of this kit. Although when I ordered it was $104 and the 8gb model wasn't just $20 higher. I'd likely order the 8gb kit given current pricing. I've also since ordered but not yet migrated to a SanDisk Extreme SD card with an A2 rating. It's sitting waiting for the day the original SD card fails. The Samsung card included in that kit does not have an A2 rating, which is the new must have for SD cards used as disks. There is alot of noise online about not running HA on an SD card... many think they just fail and you must have an SSD instead. Well mines been running fine for 18 months on the original Samsung card. There's a Home Assistant add-on you can install that will backup daily and manage the backups on google drive, keeping however many days you want. So even if my SD card fails it won't take me long to have it back up and running from the backup.

You can start with a 3 of you happen to have one laying around, but if you;re buying one I'd recommend a Pi 4 with 4gb. Also you want to use the Image that includes the Home Assistant OS and supervisor. You can do it many other ways and even run under different OS's etc, but doing it with the HA OS and Supervisor will cut many many hours off of keeping things up to date, because in the configuration I'm recommending updates are literally push button simple. .

Home Assistant has a brief learning curve of learning how to design a dashboard. It's far easier to do today tho than it was in earlier versions and there are many tutorials on youtube. In fact I'd say that one problems with youtube is finding current videos that teach dashboard creation through the UI rather than than straight YAML code. However... once you learn how to make dashboards, you can make it look however you want it. You can have a "main menu" as you've described or just swipe left and right to different sub dashboards.. or both. You can have it your way... regardless of what your way is. Theme's too... there are many that others have done, that are downloadable, or you can design your own... or like I did customize a downloaded theme to my liking. Speaking of "earlier versions",. Home Assistant is open source and has a major release on the first Wednesday of every month. It's one of the largest and most active projects on github. Here's a link to the current months release announcement so so you can get an idea of how much happens every month. (beginning late 2020 the version number system changed to year.month.minor so currently we are on 2021.11 as the major release and I think they are up to about .5 with the bug fixes, or 2021.11.5. I used to load every release, major or minor, but I've gotten to the point that I wait until towards the end of the month and load the last or near last release of the month. An Example from my house is above, I chose this screen because it's all ISY stuff and a little bit of everything. The downstairs temp in the upper left, comes from a wireless tag via the ISY and the wireless tag nodeserver. The outdoor temp underneath comes from my outdoor weather station and a different nodeserver. The larger center fireplace button controls an Insteon/ISY Scene that actually determines if the fireplace can cycle. Setpoint in the upper right... is the display of a state variable. The chevrons below that temp Run Then or Run Else (one each) of an ISY program that increases or decreases the state variable by one degree. The rest of the buttons on the screen are either Insteon devices or scenes from the ISY, except the All off button, that actually runs a helper program that sends an Off to the All Off scene and also does one other thing. My dashboard is simple as far as dashboards.... go google "Home Assistant Dashboard Examples" and go down the rabbit hole for a nice long tour of what others have done.

There are free methods for those that want to explore installing and using them. $5/month is the easy way and also opens the door for Alexa and GH, but there are also alternate methods for that too. When I started with Home Assistant I was using it strictly as a custom front end to the ISY, basically customized mobile pages (replacing mobilinc, eKeypad, Agave, etc)... to the day it's the only mobile remote control option that's been Wife Approved.... and I tried alot of things to make using her phone easy for her. Since the beginning tho, there are frankly a lot more integrations for HA than there are nodeservers for the ISY. (1,858 built in core integrations and countless more available via the Home Assistant Community Store (all free). There's even one case where I stopped using the nodeserver for the ISY and started using HA integration instead because the HA integration is less finicky. I've also branched out and things the ISY doesn't support at all like Zigbee shades. If you have Insteon there's definitely a use case for both. The Universal-devices integration at Home Assistant provides better Insteon control than the direct Insteon integration... But I also may have been biased and not given the Insteon direct integration a very complete chance. Home Assistant also has a bunch of "Add-ons" that I keep discovering more that I need. Adguard Home is one, that I use and it just works.

agreed. Plus it's a pain to remember to check what we've come to know should be automatic. I've actually had to resort to sticky notes on vehicle dashboards! I had the idea to send myself a notification 30 seconds after either garage door closed to check the status, but the garage doors close a lot more often than just us leaving. We are both leaving in 1 hour so we will see what happens then.....

Thanks. I doubted 15.1.1 was the magic sauce but I had hope. I don't understand why apple seems to be ignoring this.

There is only one polyglot2 instance running on Polisy, you currently have it pointed to your ISY, you can redirect it to ISY on Polisy. Polyglot2 can only support one instance of ISY, either the 994 or ISY on Polisy but not both. Polyglot3 has more options and I'm not entirely up to speed on it.

Last night when we left and returned GeoFences worked correctly on both phones!! That's the first time it's worked that way for awhile...Both phones... leaving and returning. A greater sample size is needed but the common denominator was IOS 15.1.1 was installed on both yesterday (which claims it's only a bug fix for dropped calls on iPhone 12 and iPhone 13). For those who have installed iOS 15.1.1 what is your GeoFence experience?

Try Help > Manage Modules and/or Configuration Tab > Portals may be waiting for you to accept.

Never fear support will be on it!. They answer tickets within a few hours usually... maybe a little longer on weekends, but you'll get a reply today. UDI support is awesome!

Here is a better way to accomplish the same thing you have. Note: of course I just used some random devices in my system to create the example. aaa Test - [ID 00E6][Parent 0001] If 'Door Switches / Front Door' Status is On Then Send Notification to 'test1 ' content 'my alert' Repeat While $cTrue is $cTrue Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Else - No Actions - (To add one, press 'Action') Note that when using the "Repeat" statement.... "repeat" appears at the TOP of the loop that is repeated--and each line that is to be repeated is idented--. So when the status changes to On, the notification will be sent and then the repeat loop will start forever. Notice that I used "While $cTrue is $cTrue" which looks like it would never end, but alas the If statement will still terminate the program when the Status of the If statement changes to false. You could also use something like Repeat "for 999999 times". $cTrue is an Integer variable that is always set to 1, it never changes, thus the little c for Constant at the start of the name. If you do want to be reminded with another notification every 3 cycles you could extend the loop the way you did and move the notification inside the loop... like this: aaa Test - [ID 00E6][Parent 0001] If 'Door Switches / Front Door' Status is On Then Repeat While $cTrue is $cTrue Send Notification to 'test1 ' content 'my alert' Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Else - No Actions - (To add one, press 'Action') (or you could even nest a repeat under the repeat.... but lets keep it simpler) The method that you used to loop probably works fine in this case, because once the sensor trips I'm guessing the status is going to stay wet until you're there. It would take a long time to dry enough to get the sensor to actually turn off (if it even does... something in the back of me head says leak sensors must be manually reset). to be clear I do use Run Program <itself> (then) from time to time to create endless loops, that's how it was done before V5 when "repeat" came into being. Note: If the sensor can change status it's likely better to loop to the IF than the then.... in other words "Run Program <itself> (if)". In the case of "Run Program <itself> (then)", without testing I believe that once the second iteration starts, when the THEN block re-runs, I believe that the IF is no longer being tested to stop the program. There is two parts to this line: The first is who gets the notification the second is the content of the message... In this case we are interested in 'Leak Sensor Water Alert - Level 1' (I'm not sure why there is a space between the tick mark and the L that is weird....) That points to the top line of the next screen shot: so you would just click the RIGHT end of that line and edit the contents of the notification in the popup window. Note that ${sys.node.#.name) is the node name that triggered the program... in this case should appear instead of ${sys.node.#.name) Note however, as you have the program looping above, the replacement probably only works the first time the notification is sent and likely doesn't work on the repeated notifications after the Run (then path). First, you must move the dead sensor up to the root level. That is it must be under "My lighting" with the new sensor, The "replace" function does not work if any devices are in a folder such as "Leak Sensors". Second, Put both devices old and new in linking mode. Click the name of the OLD sensor, then right click it, and pick "Replace <Old Name> with" and there will be a context menu with the possible new sensors that you have already added to the ISY. I'm not sure what will happen if the old sensor is so dead it can't be put in linking mode, but try it with just the new sensor in linking mode and see if it works. You should only need to do this once, and it will include the related nodes such as heartbeat. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:INSTEON_Device#Replace...with

Correct. Try to get rid of them one device at a time. With wireless writes disabled, put one device in linking mode, then right click the device name and Write Updates to Device.

We need someone that's better than me at reading level 3 logs... there are many members that might but i'll tag @kclenden in case he's around.... He's an amazing link wizard. That new button you got... When you press it and turn it to grey the 1011 icons will turn grey, and they are inactive or deselected. When they are green the ISY will be trying to write them constantly, which slows down communications because each has to error out 3 (?) times. So keep them grey and see if you can put one device at a time into linking mode, then right click the device and write updates. I was surprised when you said this. Did you confuse Restore Device with Restore PLM? Really "Write updates to device" is all you should need but I did also suggest trying "Restore Device".

In the future watch for changes that require wireless writes and make sure to stay on top of them. Not sure what firmware version you're on, but there was a long time bug that was fixed around 5.2 (it existed for most revisions of 5). The bug was linked to wireless devices that were scene controllers and programs that used "Adjust scene" which would generate the need for wireless writes. Not sure what firmware version you're on but it should be 5.3.4 unless you have a 300 series z-wave board in which case the last firmware that works with the 300 series z-wave is 5.0.16C

I don’t have my laptop but I think you want “my products”

I hate to recommend doing it because if it doesn't solve the problem for you.... but it is a soft instant upgrade... Help > Purchase Modules.

code the code button seems to be working,... maybe a browser cache issue? That looks like it's cycling thru multiple devices, which is where Teken was going with his suggestion. just to be clear, "pro" is a feature level, it adds to the number of nodes and programs allowed and gives you these two buttons on the admin console ribbon The one on the right, shown in the off or deselected state is what teken is talking about. Do you have those two buttons?

Try putting device in linking mode and right clicking the device and doing "restore device".

Also, its not documented (other than somewhere in a forum thread) but Total Nodes = Scenes + Insteon + Z-wave + NodeServer Nodes + Folders "Programs" includes both programs and program folders combined. The reason "Folders" is listed last is because it was added later than the others.

Node server ISY-Inventory A very simple nodeserver that creates one node.