Frank_YYZ

Well, that worked like a charm! Thanks Techman.

I've recently switched to the eisy from the isy993 and have noticed that the email messages sent by the eisy are not formatted the same as my emails from the isy. I have several Insteon water sensors and open/close sensors and, if any of them have not sent a heartbeat in the last day, I send out a daily email reminder showing me which ones are not working. The contents of the email Customization page is shown below. The isy produced a nicely formatted message, one sensor per line. However the eisy puts everything on one line and is virtually unreadable. Sample daily messages are shown below. I tried to force <new line> insertion adding {nl} or ${nl} to the end of each line. That didn't work, but I'm totally guessing here! Can anyone tell me how to insert a new-line into an email output message? Is there a complete list of pseudo-ops somewhere? Or maybe UDI can fix things so that the eisy more closely mimics the isy? NOTE: I don't know if this makes any difference, but I used a Google server to send my old isy notifications. However, using the exact same values didn't work on the eisy. So I used the "Default" settings. (UDI server.) They worked first time so I never pursued the matter of getting my Google email server working. Regards, Frank Appearance of old daily email from isy993: 2024/01/05 12:59:00 Heartbeat for a Wireless Sensor not received when expected. Check sensor / battery. Time since last heartbeat received: 1 Sump Pump ................. 0 days 2 Main Valve ................... 0 days 3 Furnace Room ............. 0 days 4 Kitchen Sink ................. 0 days 5 Condensate Pump ....... 0 days 6 Fridge .......................... 20 days 6 Raccoon Trap .............. 0 days New daily email from eisy: 2024/06/20 12:59:00 Heartbeat for a Wireless Sensor not received when expected. Check sensor / battery. Time since last heartbeat received: 1 Sump Pump ................. 0 days{nl} 2 Main Valve ................... 0 days ${nl} 3 Furnace Room ............. 0 days 4 Kitchen Sink ................. 0 days 5 Condensate Pump ....... 0 days 6 Fridge .......................... 9 days 6 Raccoon Trap .............. 0 days By the way, the failed "Fridge" sensor is, I believe, an Insteon issue. It is a new Rev 3.0 device and I can't get it to send heartbeat messages. I have a second new, Rev 3.0 device that does exactly the same thing. All my older devices have worked fine for years. I will eventually get around to contacting Insteon about this.

I sent in a request to Support@..... and this is what I got back. (See below.) I will send in an official ticket after I've spent some time doing further testing. I unearthed some older posts (dating back to 2020!) that show that this issue was affecting the 2440 back in the isy days. Seems odd that the 2440 will only accept programming commands from a remote dual-band device, not from any PLM. The unusual thing below is the statement that the 2440 should be placed into "multi-link" mode (fast flashing) rather than normal link mode. There is no indication on how to do this in the 2440 manual. Or anywhere else that I could find. Simply pressing the DIM - BRIGHT buttons again, or each individually, doesn't work. (It exits Link mode.) However, by futzing around with one of my units, I somehow got it into a state where I had a fast flashing LED. (The LED was on 95% of the time.) I have no idea how to replicate this! I was well away from the PLM and managed to get it to accept all 17 links. It took most of an afternoon, since it would only program one or two links before bombing out. (I used multiple "Write Updates to Device" operations.) The interesting thing is that, when the 2440 timed out, pressing DIM-BRIGHT caused it to reenter this fast flashing mode! I verified the links using the "Show Device Links Table" with the Start option to verify one or two links at a time. No luck replicating this with any of my other units yet. But I learned long ago that writing/verifying links has to be done during the day when most of my LED/CFL lights are off and there is little background Insteon traffic. Frank, -- Response from UD -- Thank you for the details. Please note: We never use the forum for details. Too many exchanges cause more confusion In order to better serve you, you must submit a ticket: https://www.universal-devices.com/my-tickets If you have changed your PLM, I suspect you have green/gray 1011 icons next to your RemoteLincs. What you need to do is to put them in programming mode (Press/hold till blinks. Click again till it blinks faster) and then right mouse click | Write updates to device.

Great idea. I created a log and sent it to support. (Also included, below.) Don't junk your RemoteLincs just yet, in case they come up with a fix. Maybe I'm old fashioned, but I really like these older remotes. Good range. Large enough to not be easily lost between the seat cushions. Easy to prepare a fancy label so you know what the six buttons do. And all six of them still worked reliably after more than a decade. By the way, here is the Level 3 Event log. I tried to do a full RESTORE. Then a WRITE UPDATES. Both failed really quickly, with no error message. (The address of my Remotelinc is 0A.1F.56 ) Mon 06/17/2024 10:53:22 : [VAR 2 1 ] 82 Mon 06/17/2024 10:53:30 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:53:30 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00) Mon 06/17/2024 10:53:39 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:53:39 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00) Mon 06/17/2024 10:53:48 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:53:48 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00) Mon 06/17/2024 10:54:09 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:54:09 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00) Mon 06/17/2024 10:54:18 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:54:18 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00) Mon 06/17/2024 10:54:20 : [VAR 2 1 ] 81 Mon 06/17/2024 10:54:27 : [INST-TX-I1 ] 02 62 0A 1F 56 0F 0D 00 Mon 06/17/2024 10:54:27 : [INST-ACK ] 02 62 0A.1F.56 0F 0D 00 06 (00)

Hi Brian, Weirdly, I had the opposite effect here. With my old isy994i, I had a slightly easier time programming my 2440's when I placed them close to the isy's PLM. But since my upgrade, I've tried both the direct PLM approach (using my new USB PLM) and placing them next to a remote dual-band device. Nothing works. As I mentioned, the eisy simply gives up while trying to write the first link without any sort of error message. Unless anyone else has had success, it's time to contact support. Frank

A previous post described some issues users had with the Model 2440 RemoteLinc after upgrading to the eisy. https://forum.universal-devices.com/topic/42484-remote-linc-2440/#comment-375646 However, this post doesn't solve my situation. I have six Model 2440 RemoteLincs of various F/W revs. (1xV.33, 2xV.35, 3xV.7C) Before upgrading to the eisy, I had a couple of units that simply wouldn't update with my isy994 , but the other 4 updated fine. (I was running isy994 V4.8.x All six units used to update fine using older isy FW.) I am now running an eisy (v5.8.3) with a brand new USB 2413U PLM. (V9E). My six controllers can still control most of my scenes, although they will always report back with a flashing LED status after every keypress since they are still trying to communicate with the old isy994 serial PLM that no longer exists! All of my old 2440's have transmitters that work perfectly since they can control scenes from quite a distance. The eisy can program all of my other wireless devices. (2x2342 remotes, 1x2843 open/close sensors, 6x2852 Water Sensors) whether they are located right beside the PLM or across the house near a dual-band device. (A 2635 ON/OFF module). But whenever I try to either Restore or Write Updates to a RemoteLinc, it makes a half hearted attempt to write the first link and then quietly stops without any sort of error message. (The "Writing" icons simply switch back from green to gray. I have tried the following: 1) Replacing the 1.2 V rechargeable batteries with new 1.5 volt batteries in case it was a signal strength issue. No change. (I should note that I've used 1.2 volt rechargeable AAA cells in these remotes for 16 years with no problems.) 2) Placing the 2440's directly beside my dual-band PLM. (At various distances.) I even unplugged all of the dual band devices near the PLM in case the repeated RF signals were causing confusion. I normally program my wireless devices across the house, near my PC and close to a dual-band device. This used to work for all wireless devices. It still works for everything except the Model 440 remotes. I'm reluctant try to delete and re-add one of these remotes from scratch . This would remove a lot of the links in my wired devices that still allow my existing remotes to control some of my scenes, rendering them completely useless. I believe that this is a SW issue with the Insteon module in the eisy, but would like to try any suggestions before I start a ticket. Frank

FWIW, I managed to get my newly downloaded copy of Agave running on my old Android Nexus 5. I got a few spurious "Agave has Stopped" messages when I first downloaded and tried to run it, but it seemed to be very much alive and let me go through the initial setup routine. I then manually downloaded my isy-994 configuration to the phone from the Settings screen and all is well. I once had a case where Agave kept crashing and I found that rebooting the phone fixed the issue. It's been running solidly ever since. Tried to load Agave on an old IPad and couldn't find it on the Apple App store. (But I have no idea if it was ever in the Apple Store.)

I also really like Agave and use it all the time. You didn't mention if you were in the Kingdom of Apple or the Empire of Google. I just looked it up on the Google Play Store and it was there. I tried to install it on one of my old, gronky Android phones. (An old Nexus 5 which, like every other old Nexus, crashes on just about everything.) I use this phone as a dedicated Tempest Weather Display. There it only hangs every couple of days. Agave installed OK but then STOPPED when I tried to run it. I would probably blame my phone for this rather than Agave. Don't know if this helps at all. Frank

Have you tried clicking "Things", then "Switches/Dimmers". Find your device and click on it. Select the "Options" box. It allows the entry of Custom Status and Custom Buttons. Try entering what you want the states to read. (You have to pass through all the fields and then press "Save".) This works for Scenes as well as devices. Frank

Just to let everyone know, James fixed the free version of Agave and it now displays folders with hidden scenes without crashing. I'm not sure exactly when the change happened since my Android phone quietly updated the app in the background without telling me. But it's as good as before. Much appreciated.

I have just downloaded the Android free version. I've been using the paid version for a while with absolutely no issues. It's always quick to sync itself to the isy when started and has always been responsive and solid. But I've noticed a problem in the new release that didn't exist before so you may want to hold off on updating. I have a lot of Insteon devices and scenes so I place all of my scenes into Rooms. (Referred to as Folders on the isy). Most Rooms display and operate correctly but, in the new version, trying to display three of my Rooms causes the program to immediately crash and restart at the Favorites screen. At first I thought that starting the Room name with a "|" was the problem but I renamed two of the crashing folders with no change. In addition I found that a folder innocuously named "Garage" was also crashing the App. I have a total of 24 Rooms defined and, for the life of me, I can't see what's different about the three Rooms that now crash the App. EDIT: I did some checking and the three folders that crash each have a "hidden" scene. In my case, the hidden character is a "~". So maybe having a hidden scene in a folder now causes the App to crash? I've tried the following. It didn't help. 1) Refresh Data . 2) Reset Agave Data and re-enter all isy login info again to allow a fresh reload. Since James has issued this as freeware, it might be a while (if ever) to get this issue fixed. But, does anyone have an idea of how I can get a copy of the previous version? It seems that, if the free version doesn't work, there should be a way to get access to my paid version. Frank