svetter

So, bad thing is PLM doesn't connect. I'm doing first level diags. Mmmm.

Updated Java, cleared cache and applications, reinstalled latest start.jnlp and it still shows two entries for the eISY. But I am ok with that. The error went away. As for the triple button press I sang "staying alive" and had no idea what speed or how long I should hold each tap. But I am back in business and at 5.7.0.

BTW, thanks for pointing me in the right direction.

So the multifunction power button should be used when LED is RED? I tried when blue and nothing, I held the button until it turned red, then tapped three times and noticed it went through some sort of reboot and I was able to get in and change the admin user ID and password (and document both). Now my IoX finder starts with a connection error and lists my eISY as two devices. One with https://eisy,local:8443 and the other by the local IP address. The delete button doesn't seem to work, but I can log into either on the LAN console with the new User ID and password. Remote portal access is still working.

Folks, I am not able to access my admin console on the local lan for my eISY because I changed my admin user ID during migration and may have made a typo or just forgot to document. I see in the manual that for eISY you can "eisy simply use AC to change the password." What does AC mean? I'm able to access the device through the ISY portal, but that doesn't give me the credentials to change the admin user ID/Password Thanks!

I just received the new Insteon 2413U USB Modem and decided to bring up the Elsy while the ISY994 was still operational. I created a backup of the configuration and since I was just playing with Z-Wave at the time I wasn't concerned about migrating those devices, just the Insteon (of which there are plenty). After restoring the backup to the Elsy, the device got a socket error on restart. I powered cycled it and realized that the password had gone back to admin/admin, so I updated that. All my devices were shown. The Time Zone information was incorrect, so I reset that. I reset the PLM and got the battery operated devices synced as a separate step after all the writes were done. Programs started to work normally. The next day I added the two Zwave devices I had after a reset of the Zwave dongle and each device. The first device, a plug in controller added immediately. The second, a Lexiton outlet (after reset) popped up a dialog box asking for a PIN code. This may have been the reason I could not add it when I was testing, perhaps a bug or code level miss match. I set the security to low and it connected. Alexa migration required I delete the settings on the Portal for the old device so there wouldn't be duplicates, and asking Alexa to rediscover devices. Looks like I am set to sail now. Could someone point me to a good online source so I can learn about Z-wave pin codes? And maybe why one devivce used them and the other not? Thanks!

Thanks all. I upgraded to the latest levels, and I was able to connect the eisy and control a Leviton Plug in Dimmer with Z-Wave Technology. There is a wired in Leviton outlet just 15 feet away that I cannot reach, but I also had the same issue with the ISY. The best I was able to get was a "try again" message. I need to diagnose some more.

Thanks! I'll get the new firmware on it and walk through your suggestions. I appreciate the help! I do think something is wonky with the USB port. When I first opened the Admin console, There was no Z-Wave menu, but re-plugging in the dongle and a restart of the I0X caused the z-Wave menu to appear.

I installed a poisy zMatter card in the external dongle case I ordered from UD. The unit is not commected to Insteon Modem, I am just trying to add a couple of z-Wave devices I bought to test its connectivity. On the Admin concole when I Z-Wave --> Add a Z-Wave Device I receive the error shown. Firmware is 5.5.4 as shown. Any idea what could be wrong?

The following are instructions on how to assemble the Z-Wave+ & Matter Module ( https://www.universal-devices.com/product/zmatter-z-wave-matter-module-for-polisy-beta/ ) in a Zmatter enclosure ( https://www.universal-devices.com/product/zmatter-usb-enclosure/ ). You will need a small Phillips screw driver or jewelers screw driver to open the enclosure and attach the board and needle nose pliers to attach the antenna leads and tighten the antenna mounting nuts. Note: The Matter module will not fit inside the enclosure in its current form. It will need to be snapped in half along a scribe mark that is next to the antenna wire mounts and the two mounting holes. Before snapping, mark the module to identify the Z-Wave and Zigbee chip locations or take a picture of the board for later reference. Open the new USB enclosure by unscrewing the four 10mm M2 screws. Looking inside, note the position of the circuit board standoffs that receive these screws. The motherboard should have a total of six standoffs. Four of the standoffs (two on the USB dongle side, and two in the center) hold the motherboard to the case, and two (opposite of the USB dongle) are mounted directly to the board. If your enclosure has screws and not standoffs in the center location, contact UD sales for help. Insert the gold threaded antenna mounts in the enclosure case leaving the wire leads free. The threads have a flat spot that needs to align with the flat spot (nothch) on either of the holes in the side of the case. Clearance with the case and internal components will be tight, but with care they will slip in the mounting holes in the case. The two threaded antenna mounts are different, but it doesn't matter which side they go on. Apply a lock washer, washer, and nut then tighten. If you haven't already, snap the board along the scribe (see note above) and with the board outside the case, use your needle nose pliers to click/snap on the antenna wires to the mounts in the location that matches the Z-wave and Zigbee markings on the enclosure bottom. With the wires attached, insert the module into the motherboard connector. Use the included screws to attached the module to the two standoffs on the motherboard being careful not to pinch the wires. The holes will align with the module properly in the motherboard connector. Carefully tuck the excess antenna lead wires into the case without making sharp bends. Screw the cover on the enclosure with the original M2 x 10mm screws. Attach the antennas by screwing them on. The antennas are optimized and need to be attached to the correct side. Red band = Zigbee, Yellow band = Z-Wave. Take the rest of the day off!

Thanks again for your help on this thread. I've got a house full of devices, but still make the error to click write changes and not the button to the left of the drop down (which looks like a heading at first glance)

This is starting to match up to what I've seen. If I close the console and come back in, I see an old value. If I do a backup of the console and close it will be the new setting. This is for a scene using the switchlinc. For the device local setting I will check out what has been said in this thread and check back. I see the console go busy with a setting change, but when I use the switch the value hasn't been stored to the switch. The on value, as an example, stays at 100. Thanks all for your quick reply. Long haul Insteon user here. I even recall when Home Depot stocked them!

I was on the 5.3.0 console and firmware and when adding a new switch I wanted to set the local on level. Usually when I write a change I see the green bar appear, but this didn't happen. It also won't work on any other device. I am able to hear a beep, and add the device to a scene, but not change its on level. I updated to 5.3.3 and cleared the Java cache and still the same issue. Is this working differently in V5? I may not have noticed until now as the lighting program is mature and stable. Thanks!

I just migrated from 4.7.3 to 5.3. Scenes and Devices came over and the Programs seemed to be there in the Admin Console (which I use nearly 100% of the time). When I went through the Portal to use the version that looks like the phone app, I didn't see the programs. My light automation wasn't working. I discovered the programs were not saved from the admin console. When I saved them, they started working and show up in the app. So, saving the programs is an extra step I missed. As I don't use the Dashboard (but want to see the new 5.0 features) what is the difference between My Programs (empty window frame) and Program Manager (where I can see the list of programs I created but don't seem to be able to do anything with them)? I guess it is time to read the manual on the Dashboard.

And that is another thing.. I could never spell EZSrve. Thanks for letting it roll. I'll check it when I have access, but putting things together there is a high probability. I've deleted Scene 82, and the unsupported PLM (aka EZSrve). I bet it read it in from all the device links table when I was populating the ISY. I hope this will cut down on a lot of the network traffic and maybe get rid of the Red LED flash on some of the new devices that have multi-color LEDs. I was VERY excited when I heard my first SwitchLinc beep. I still have 8 devices on v.27 firmware. Finally got rid of my last ICON.

I bet this is the old EZServ! Ha! Certainly a different address than the PLM listed under PLM Info/Status. I don't miss the EZServ this much. The ISY links table has many devices to it, probably that Scene 82 I could never figure out. I really haven't messed with Houselinc since they dropped support and probably plugged the EZserv the last time. Consider it gone! It will go to the shelf with my original flip phone.

Interesting. I shows as XX.XX.XX Unsupported Device 3.19 I'm only running with one PLM, and I've watched it update every time I made a change to a device, so I just assumed this is now the ISY worked. It is most certainly listed under ISY, and in Scene 82, which I assumed, up to now, was the scene the ISY uses to do the nightly query. I haven't been bold enough to delete it, because I saw all the writes to it when I replaced a PLM that went bad. Prior to the ISY, the house was automated with the EZServ (which did the job) managed by HouseLinc. I did play with the 2412N, before getting a Hub, that is still not in any real service. I never had a computer running full time to control events with HouseLinc, so prior to this an X10 photo eye thing controlled automated scenes. I've been a fan of dedicated controllers.

I've been on the ISY for a few of years now (enough to be on its second PLM). For a while I used HouseLinc on its own PLM along side to the ISY until I had the new network working correctly. It wasn't running, I'd just plug in the PLM when the deskside was booted to check things. Then the HouseLinc wouldn't work with new firmware levels so I made the jump and learned ISY speak (still learning). I started with Insteon when it was V1, migrating from X10. The Switchlinc 2's were a great improvement. But, I digress. Though the actual problem turned out to be the way a Java app is different when launched by a browser with respect tot he looping, I agree with what you say about starting fresh, but Geez, with all the ramp rates, local vs. scene settings, it looked like a huge job. What I have been doing is when I upgrade a device that is no longer responsive, I would reset, then do a restore device. Not a clean cut from scratch, but at least what the ISY knew and not some leftover HouseLinc zombies. But, in the last two cases, this didn't work. Some of my oldest V2 devices were a couple of KeyPadLincs (all X10 long gone), perhaps V40 hardware, the first gen with the laser etched keypads. I installed the new dual band, reset it, and did a restore. I added them as new devices, and asked the ISY to replace the old with the new. After Err 0's Err 1's etc. I knew something was up. These keypads, though working fine, were originally programmed with HouseLinc. Then I tried to reset them and restore them. One of the restores changed a 6 button to an 8 button and none of the scenes worked from the device (they worked using a scene test). I reprogrammed the switches from scratch and everything works perfectly. There must be meta-data (like toggle modes, beep settings, etc.) that when written corrupted the device that would no longer communicate. I just have to remember to set the toggle mode before adding it as a controller to a scene next time . I was lucky that I discovered that creating scenes for KeyPadLinc buttons made far more sense than linking each button to multiple devices. If you change devices, you just need to re-link the scenes. This is a great forum. No one in my grill about a learning curve. Thanks!

Thanks! That is pretty much what I figured out - create a scene for the cross link. I guess it was the ISY's design approach to use scenes. As for the updates: The only device that shows it has an update pending is the PLM. The PLM shows up twice. Once under the ISY list, and the other under Scene 82 (which I have yet to research what that is). Maybe something the HouseLinc created that was imported with the links when I migrated over. It is a reasonable mesh (26 scenes, and >40 devices) and I didn't want to start from scratch. Devices that I have installed from a factory reset state and not migrated links to do not appear in it. Is it reasonable to delete Scene 82? If it has no special meaning to the ISY, I don't use it as it has no controllers except the PLM.

No, I completely backed out of using HouseLinc because it no longer understood new firmware switches, so completely migrated. In response to an earlier question I left unanswered, the PowerLinc Modem always seems to have 1010 next to it. This started about a month ago. I even did a factory reset of it, and File --> Restore Modem (PLM) and it is still there. Also tried Write Updates to Device. I contacted Tech Support and there was excellent response. Here is what I learned so far. There is a difference between launching the Admin Console from a Browser and Launching it using the ISY Finder. I don't completely understand the difference yet, but the hang condition does not happen when launched from the ISY Finder. Tech Support said this could be filewall issues, but I haven't looked into that. Overall, I am still looking for a way using the ISY that I can remotely link two devices as I could with HouseLinc. It makes sense when there are many devices, but it I have a 3-way switch and a single load, I would just link to link the load controller with the Aux. switch.

ISY and Admin both on v.4.3.26 The more I think about it, the more the default radio button to manually link devices is dangerous. I was exploring linking since that is something I haven't done in the ISY.. I was hoping I could remotely link devices much the way in HomeLinc.

I cleared the cache as a prevention in case I had a stale Admin Console. When I started this, the even log (level 3) had two entries in them, that the linking process was started (yes, before I pressed finish) and a row of hex data. When I forced the admin console to close, I lost this data. I am in the loop again. The progress meter ticks up to 99% and loops again, and the event viewer has 0 (no) entries. It appears the ISY is simply ticking off time and waiting for a device to start linking to interrupt it. It is very patient (more than me) and will wait for hours. Since I am again in this long time out loop, I will go have a beer.

So, I was able to reproduce the problem. I cleared my Java cache, then opened the Admin Console. Link Management --> Start Linking and then closed the admin console. When I re-opened it, I am back in the linking loop. It appears it has accepted the default and looking for devices to link and may not have a timeout!

Correction - force closed the admin console because there was no cancel button on Start Linking. So, the active event view would be forced closed as well. Let me clear logs and start again. May take several hours if it hangs again. Since I didn't have any devices in linking mode, is there a time out value for the operation? -Scott

Let me look deeper. I understand what you said. All I did was to close the dialog box with the default action because there was no cancel. Perhaps the UI took this as a start click.