srjacob

The PLM is still attached to the 994, and everything works fine, including the Elk interaction. I am concerned about several things: 1) the scenes in the admin console for the 994 seem to be using the new version of the admin console, not the version that I am used to for that device. The copyright date goes to 2025, and the scenes have an Action field in them, which they origionally didn't have. 2) The admin console scenes in the eisy (when migrated) have an action field of off, which the action field in the 994 was on. Almost every scene has this issue. 3) my concern is that if I put the PLM on the eisy, my scenes will be screwed up, and I don't want that. 4) I wonder if I did the migration correctly. If not, please tell me what I forgot.

I did follow the instructions I am NOT migrating Zwave, just Insteon. Therefore, the instructions don't indicate that I have to shut down the 994. Having both the eisy and the 994 up at the same time allows me to migrate the programs that use the Elk module to the Elk plugin. I have about 30 programs that use the Elk because the Elks controls an electronic gate.

I am trying to migrate from an ISY994 (Firmware Insteon V5.0.16C) to a eisy (firmware 5.9.1) and am running into a problem with Insteon scenes. What I did was do a file->Backup ISY from the admin console of the ISY994 and restored that file using file->restore IOX (the WIKI isn't really clear on this). What has happened is that even though the devices seems to come through, the scenes have an action filed (that the 994 never had), and the admin consoles for both the 994 and the eisy seem to be the same. I have to migrate the programs that use the Elk module to the eisy using the Elk plugin), and the scenes seem to be messed up. Did I do the migration properly, and somehow did UD slip a new admin console for my 994? I am running the 994 and the eisy on the same network (they have different IP addresses). The PLM is still on the 994, and the Insteon lighting network and the Elk communication with the 994 seems to work fine.. I am hesitent to move the PLM to the eisy because I don't want my Insteon scenes to be messed up and I still have to convert the programs that use the Elk plugin.

That worked fine. The programs did not come over properly because I used the Elk module on the 994 and the Elk plugin on the eisy. That difference means I have to convert the programs that use the Elk. The programs that only used Insteon came over fine. What didn't come over fine was the scenes. I have a separate post on that. The 994 works perfectly and I hated to upgrade to the eisy.

I recently migrated to eisyfrom ISY994. When I migrated my 994 to an eisy, I did a backup on the 994, and loaded that into the eisy (as per the instructions). Unfortunately, the scenes got messed up. I have attached a screenshot from the 994 and the migrated eisy scene. Same scene. What is going on with the migration? I should note that the PLM that is on the 994 has NOT moved. I don't want my Insteon scenes to be messed up and I still have to convert the programs that use the old Elk module to the new Elk plugin.

Is there any way to run multiple copies of IoX (one for an operational ISY994 and the other for an eisy)? I am trying to migrate programs from the Elk Module in the 994 to the Elk plugin on the eisy.

If somebody had told me the Elk stuff was intermixed with the network stuff, I would have looked therre. I think it is all here, and I can work with it. Now on to why the scenes are messed up. I have attached a screenshot. I don't know why there is Action, and what is the Default. When used the admin console for the 994, I get basically the same thing. The original admin console showed the scene correctly. I have not moved the eisy to the PLM yet. I wanted to make sure the scenes were correct and the programs that used the Elk module were modified. Does anyone know what is going on with the scenes, and why I am getting the same admin console for both the 994 and the eisy?

My configuration must be correct. I am getting the outputs, just not the zones. Yes, at one time my user code was not correct. I created a new one, and it works fine with M1ToGo. The debug log is attached, and the screenshot of the other things you asked for. ELK_7-14-2025_124815_PM.zip

I did all that with the configuration. It was already correct. I don't see anything relating to the Elk in the eisy Admin console. I think you misunderstand regarding simultaneous connections. What Elk is telling me is that I can have up to 30 simultaneous connections to the M1XEP (but they have only tested 4). That means I can 1 connection via the eisy, and 3 more with M1ToGo. If the M1 is in programming mode (via RP2), the other connections are blocked. I am still trying to figure out why my zones don't show up in the nodes list, and where in the eisy admin console the Elk stuff shows up. With the Elk module for the 994, it was easy. The eisy seems much more difficult.

OK. Yesterday I said I would email Elk and ask them "how many simultaneous connections can the XEP make"? Here is their reply from Brad Weeks: Now you know. My answers are in BOLD At Nodes from Elk plugin.txt

I have attached the Elk Plugin Debug Log. The restart you spoke of restarts the plugin, not the log. Anyway, I didn't see any errors. And yes, the IP address is correct and the non-secure port is enabled. And yes, I can run the 994 and M1ToGo simultaneously. I do it all the time. I didn't know you couldn't. My question to Elk had nothing to do with the plugin, but I asked them how many simultaneously connections can the XEP support. I'll probably get the answer tomorrow. ELK_7-13-2025_111019_PM.zip

I believe there can be only one programming connection to the XEP (thru RP2), but multiple non-programming connections. I often go into my M1 system through both the 994 and M1ToGo. I tried 1-2 and 1,2 for my areas. It didn't seem to make any difference. I have posed this question to Elk Technical Support. I have around 70 outputs. Some of these are real outputs (I control a gate using an M1KAM) and some are used as program flags. This is why I specified 100 outputs. If I make Elk programming changes later, I don't want to go back and reconfigure the plugin. In any case, I have disconnected the 994. Makes no difference. I configured the log for debug like you suggested. There was no RESTART on the top menu, you I am attaching the entire log. Steve Debug log file.txt

Done

I installed the plugin using PG3X and got the configuration screen. I configured it to my Elk, and clicked "save changes" . I still can't see anything about the elk plugin in the admin console (I had the Elk module working fine in my ISY994) and I am a newbe to eisy and polisy.

I have the M1G with the M1XEP interface. The Elk module worked perfectly on my ISY994. I did that, but the configuration in the admin console under plugins (plugin 1-the Elk) doesn't indicate these values, and doesn't seem to change the values once I come out and come back in to the plugin. Where, exactly, does the Elk plugin parameters show up in the admin console? How do I know the plugin was configured correctly.?

I successfully logged into the administrative console, and installed the Elk plugin, but I don't know how to configure it or use it in my programs. Also, my Insteon scenes are totally messed up. Steve

I just got an eisy and installed the Elk plugin. The documentation on using the Elk plugin isn't very good, and I can't figure out how to point the plugin to the Elk system. Also, there is no documentation on how to use the Elk zones and outputs in eisy programs. If someone can give me a clue on these things, I would appreciate it. Also, if someone could point me to the Elk plugin documentation, that would be great. Steve

That did it. I can now access the eisy. Now on to my other problems. My Insteon scenes are all messed up.

I rebooted the router and did that with the eisy. Nothing worked. I went to the router's DHCP table and found the IP address to be 192.168.0.151. I put the url (http://192.168.0.151:8443) into the IoX finder, and it could not find the eisy (I got an error message) like it told me to do in the wiki. How do I factory reboot and clear the eisy?

How can I reboot the eisy if I cannot get to the administrative console?

I don't believe the issue is either with the router or firewall. The eisy is within the network. The only thing the router does is provide the DHCP address. Anyway, I don't have another computer I could try. The DHCP address of the eisy is in my router's DHCP table. I do not have a VPN. No, I could not access the eisy via the admin console using your url.

YOUR WISH IS MY COMMAND. *** OS *** FreeBSD eisy 14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 #4 releng/14.1-n267727-74b6c983723c-dirty: Fri Nov 15 12:13:25 PST 2024 root@bsdev14.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64 *** Package Information *** ************ UDX ************ udx-3.9.0_9 Name : udx Version : 3.9.0_9 Installed on : Thu Apr 10 11:51:47 2025 EDT Origin : misc/udx Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : UNKNOWN Comment : Polisy/eisy Admin Service Shared Libs required: libsqlite3.so.0 libmosquitto.so.1 libcurl.so.4 Annotations : FreeBSD_version: 1401000 repo_type : binary repository : udi Flat size : 19.9MiB Description : UDX HW/Admin Service for Universal Devices eisy/Polisy <strong>Release notes for 3.9.0_9 - 03/21/2025</strong><br/> - Install dhcpcd during upgrade to 141 <strong>Release notes for 3.9.0_8 - 03/16/2025</strong><br/> - Wait for network/sanity check <strong>Release notes for 3.9.0_6 - 02/24/2025</strong><br/> - Change pydantic to pydantic2 <strong>Release notes for 3.9.0_5 - 02/20/2025</strong><br/> - Fixed Wifi setup <strong>Release notes for 3.9.0_4 - 02/16/2025</strong><br/> - Fixed mdns responder on polisy <br/> - Fixed devd for polisy <br/> - Fixed hostname for eisy <br/> <strong>Release notes for 3.9.3 - 02/07/2025</strong><br/> - MAJOR UPGRADE to OS 14.1 - WILL REBOOT MULTIPLE TIMES. DO NOT POWEROFF <br/> - Fixed bootloader upgrade for 14.1 <br/> - Change isy userid to polyglot <br/> - Power button no longer performs upgrades<br/> - Using ud repo for FreeBSD packages<br/> - Initial IoX Matter Bridge scafolding<br/> <strong>Release notes for 3.6.5_2 - 11/19/2024</strong><br/> - Major upgrade to OS 14.1<br/> - Cleaner daemon operations<br/> - Support for eisyui (Unified/Universal eisy UI) <br/> <strong>Release notes for 3.5.8 - 07/23/2024</strong><br/> - Fixed upgrade failure bug<br/> - Fixed tpm and sleep issues<br/> - Fixed warning for upgrade to 14.x <br/> ************ IoX ************ isy-5.9.1_18 Name : isy Version : 5.9.1_18 Installed on : Thu Apr 10 11:51:46 2025 EDT Origin : misc/isy Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : UNKNOWN Comment : ISY Port to X (IoX) Shared Libs required: libxml2.so.2 libwebsockets.so.19 libsqlite3.so.0 libmosquitto.so.1 libiconv.so.2 libgobject-2.0.so.0 libgmodule-2.0.so.0 libglib-2.0.so.0 libgio-2.0.so.0 libcurl.so.4 libarchive.so.13 Annotations : FreeBSD_version: 1401000 repo_type : binary repository : udi Flat size : 39.4MiB Description : ISY Service for Universal Devices Running on X (IoX)<br/> <strong>Release notes for: 5.9.1_17 - 03/14/2025</strong><br/> Fixes:<br/> - Fixes for isy permissions <br/> <strong>Release notes for: 5.9.1_15 - 03/14/2025</strong><br/> Fixes:<br/> - Support PIN codes for Zigbee locks <br/> <strong>Release notes for: 5.9.1_12 - 03/07/2025</strong><br/> <strong>Release notes for: 5.9.1_11 - 03/07/2025</strong><br/> Fixes:<br/> - In some cases a corrupted file was causing IoX to crash <br/> - Fix file permissions for scripts when installing IoX - Don't process battery devices when doing network heal (queue them instead) - Don't attempt to interview battery devices during migration <br/> <strong>Release notes for: 5.9.1_9 - 02/20/2025</strong><br/> Fixes:<br/> - Dynamic Profiles: Allow and ignore blank or numeric 'init' on command parameter<br/> - Dynamic Profiles: Make sure profile entry in common db is updated after any profile move<br/> <br/> <strong>Release notes for: 5.9.1_8 - 02/10/2025</strong><br/> Fixes:<br/> - Dynamic Profiles: Show parsing errors in log when moving profile files to database<br/> <br/> <strong>Release notes for: 5.9.1_7 - 02/09/2025</strong><br/> Fixes:<br/> - Programs: Fixed problem where node status changes caused control conditions to run (only affected node server nodes)<br/> - ZWave: Fixed problem where Z-Wave migration would fail to migrate any Z-Wave devices<br/> - Zigbee: Fixed problem of nodes not being created for devices with multiple buttons<br/> - Insteon: Fixed problem where some commands were missing from inlineLinc devices<br/> - Insteon: Fixe problem where Insteon would stop responding (usually caused by using I3 Dial)<br/> <br/> Features:<br/> - Matter: Hello World! Light bulb support<br/> - Zigbee: Support Relative Humidity and Temperature Measurement Clusters<br/> - Zigbee: Support thermostats<br/> - Insteon: LED Control for I3 Dial and I3 Paddle<br/> - Programs: Added 'Unix Date/Time (seconds)' to the set of system values you can assign to a variable<br/> - Admin Console: Log Viewer and Capture for Matter, Zigbee, Z-Wave, and other logs<br/> <strong>Release notes for: 5.9.0_x - 11/11/2024</strong><br/> - New lightweight daemon<br/> - Support for Matter<br/> - Support for eisyui<br/> <strong>Release notes for: 5.8.4_3 - 07/11/2024</strong><br/> Fixes:<br/> - Infrequent crash at iox boot up due to timing<br/> - Node status changes caused control conditions to run on plugin nodes. <br/> - SMTP mail removing new lines<br/> <strong>Release notes for: 5.8.4 - 06/27/2024</strong><br/> Fixes:<br/> - Insteon I3 Paddle and I3 Keypad buttons default links<br/> - Show Unix Time status values as Timestamps<br/> - Faster IoX Backup<br/> - Some characters not displayed correctly in Admin Console<br/> For Developers:<br/> - Plugin timestamp support<br/> - Allow node servers to define their own status names in nodedefs<br/> - Fill in device type field for Zigbee (so Philips hue can be recognized)<br/> - Query Zigbee devices after they are added<br/> - added <rpnode> to Zigbee nodes<br/> - Initial support for posting events to MQTT<br/> - Fix ISO8601 Timestamps for node property history and events<br/> <strong>Release notes for: 5.8.3_2 - 05/23/2024</strong><br/> Fixes:<br/> - Added <> to message ID in SMTP mailer - Added uuid to SMTP mailer - SMTP large body was not sent Enhancements:<br/> - Events are now published through mqtt as well - Removed dependency on Status names - SNI automatically enabled for OpenADR <strong>Release notes for: 5.8.3_0 - 04/22/2024</strong><br/> Fixes:<br/> - Remove default time events from event viewer<br/> Features:<br/> - Better support for enhanced hue (for Phillips Hue)<br/> - Support Zigbee Color XY / Temperature<br/> - Allow user to manually specify Zigbee radio channel (for Securifi devices)<br/> <strong>Release notes for: 5.8.0_1 - 01/03/2024</strong><br/> - Fixed reboot on polisy when using ZMatter in original mode<br/> <strong>Release notes for: 5.8.0 - 01/01/2024</strong><br/> - Fixed system crash (for Insteon users)<br/> - Fixed subscription causing crash when bombarded <br/> - Misc bug fixes<br/> - Integration of sqlite database for recording events/property changes<br/> - Node property history database - disabled by default<br/> <strong>Release notes for: 5.7.1_07 - 12/01/2023</strong><br/> - Fix for subscription hang - Fix for 4.9 migration crash <strong>Release notes for: 5.7.1_05 - 11/29/2023</strong><br/> - Crash while initializing PLM (older versions)<br/> <strong>Release notes for: 5.7.1_03 - 11/27/2023</strong><br/> - Zooz dongle issue<br/> - Initial db<br/> <strong>Release notes for: 5.7.1_02 - 11/15/2023</strong><br/> <strong>Fixes</strong><br/> - Crash during restart<br/> - Crash during usubscribe<br/> - Z-Wave change from bridge to static <br/> <strong>Release notes for: 5.7.1_01 - 11/09/2023</strong><br/> <strong>Fixes</strong><br/> - Thermostat min/max validation incorrect for some Z-Wave thermostats<br/> - S2 Verification popup appears when using SmartStart<br/> - Graceful hadling of HomeAssistant bombardment through websockets<br/> - Subscriptions filling up due to HomeAssistant not closing sockets</br> - Right mouse click support for FreeBSD <br/> <strong>Enhancements</strong><br/> - Support ISY994 version 4.9 migration<br/> - Add auto/on/off configuration setting for enabling Z-Wave and Zigbee<br/> - New installations default to using ZMatter Z-Wave<br/> <strong>APIs</strong><br/> - Add event indicating all nodes for a device have been added<br/> - Add 'hint' field to all nodes<br/> <strong>Release notes for: 5.7.0_4 - 10/09/2023</strong><br/> <strong>Fixes</strong><br/> - Possible fix for all programs being disabled after upgrade<br/> - I3 Paddle/Keypad not showing up correctly in ISY Scenes<br/> - Programs disabled after upgrading<br/> - Z-Wave region default setting may be incorrect<br/> - Max subscription error debugging support<br/> <strong>Release notes for: 5.7.0 - 09/08/2023</strong><br/> <strong>Fixes</strong><br/> - Crit not being initialized causing zero size files and other anomalies<br/> - Fix: Zigbee color commands not available for some customers using Sengled color bulbs<br/> - Fix: Zigbee devices unexpectedly removed from network<br/> <br/> <strong>Enhancements</strong><br/> Zigbee:<br/> - Support for Zigbee On/Off switch<br/> - Support for Zigbee occupancy cluster<br/> - Basic support for Zigbee door locks (lock/unlock/query)<br/> <br/> Z-Wave:<br/> - Support .gbl OTA Firmware upgrade files<br/> - Support abandon OTA Firmware upgrade<br/> INSTEON:<br/> - Support dimmer/relay mode for I3 Paddle and I3 Keypad<br/> - Support various flags for I3 Paddle and I3 Keypad<br/> <br/> General:<br/> - Support dynamic text status values for node servers<br/> - Add parameter initial values for light on/off commands<br/> <hr/> <strong>Release notes for: 5.6.5_1 - 08/31/2023</strong><br/> <strong>Fixes</strong> OpenADR Dashboard cannot find icons <br/> Crit not being initialized<br/> <strong>Enhancements</strong> Support for upgrading the OS to 13.2<br/> <hr/> <strong>Release notes for: 5.6.4_7 - 08/23/2023</strong><br/> Fixed socket/file description exhaustion issue<br/> <hr/> <strong>Release notes for: 5.6.4 - 08/11/2023</strong><br/> <br/> <strong>Fixes</strong> Z-Wave devices no longer responding when IoX restarts<br/> Faster port detection for Z-Wave<br/> Z-Wave backups no longer progressively get larger<br/> Native linking of Insteon I3 Outlet nodes<br/> Bootup crash when too much network traffic <br/> Log showing IPV6 addresses only<br/> File system status showing garbage<br/> <strong>Enhancements</strong><br/> Insteon I3 KPL support<br/> Z-Wave OTA Firmware updates (limited to intel hex format)<br/> Zigbee sensor support<br/> Increased max nodes from 1024 to 2048<br/> Simplified pg3 authorization.<br/> Webserver enhancements.<br/> OpenADR Dashboard is now incorporated into the Admin Console.<br/> - ************ libwebsockets ************ libwebsockets-4.3.3 Name : libwebsockets Version : 4.3.3 Installed on : Thu Apr 10 11:51:42 2025 EDT Origin : net/libwebsockets Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : net devel Licenses : MIT Maintainer : ports@FreeBSD.org WWW : https://libwebsockets.org/ Comment : C library for lightweight websocket clients and servers Options : GLIB : off HTTP2 : on HTTP_PROXY : off LIBEV : off LIBEVENT : off LIBUV : on MBEDTLS : off MQTT : on OPENSSL : on PEERLIMITS : off PLUGINS : off SECURE_STREAMS : off SOCKS : off SQLITE : off WEBSERVER : off Shared Libs required: libuv.so.1 Shared Libs provided: libwebsockets.so.19 libwebsockets-evlib_uv.so Annotations : FreeBSD_version: 1401000 repo_type : binary repository : udi Flat size : 1.95MiB Description : Libwebsockets is a lightweight pure C library built to use minimal CPU and memory resources, and provide fast throughput in both directions as client or server. ************ tpm2-tools ************ tpm2-tools-5.6_1 Name : tpm2-tools Version : 5.6_1 Installed on : Thu Apr 10 11:51:49 2025 EDT Origin : security/tpm2-tools Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : security Licenses : BSD2CLAUSE Maintainer : tstruk@gmail.com WWW : https://github.com/tpm2-software/tpm2-tools Comment : TPM2 tools Shared Libs required: libtss2-tctildr.so.0 libtss2-sys.so.1 libtss2-rc.so.0 libtss2-mu.so.0 libtss2-fapi.so.1 libtss2-esys.so.0 libcurl.so.4 Annotations : FreeBSD_version: 1401000 build_timestamp: 2025-01-09T19:39:08+0000 built_by : poudriere-git-3.4.2 port_checkout_unclean: no port_git_hash : a40e262549 ports_top_checkout_unclean: no ports_top_git_hash: 2414cbd02b repo_type : binary repository : FreeBSD-udx Flat size : 1.36MiB Description : This port contains the code for the TPM (Trusted Platform Module) 2.0 tools based on tpm2-tss. ************ mosquitto ************ mosquitto-2.0.18 Name : mosquitto Version : 2.0.18 Installed on : Thu Apr 10 11:51:42 2025 EDT Origin : net/mosquitto Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : net Licenses : EPL Maintainer : joe@thrallingpenguin.com WWW : https://mosquitto.org/ Comment : Open source MQTT broker Options : CARES : on WEBSOCKETS : on Shared Libs required: libwebsockets.so.19 libcjson.so.1 libcares.so.2 Shared Libs provided: libmosquittopp.so.1 libmosquitto.so.1 Annotations : FreeBSD_version: 1401000 cpe : cpe:2.3:a:eclipse:mosquitto:2.0.18:::::freebsd14:x64 repo_type : binary repository : udi Flat size : 1003KiB Description : Mosquitto is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for "machine to machine" messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers like the Arduino. ************ pg3x ************ pg3x-3.3.20 Name : pg3x Version : 3.3.20 Installed on : Mon Jul 7 19:58:02 2025 EDT Origin : misc/pg3x Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc Licenses : MIT Maintainer : benoit@universal-devices.com WWW : https://github.com/UniversalDevicesInc/pg3 Comment : Polyglot PG3x for UDI eisy Shared Libs required: libthr.so.3 libssl.so.30 libm.so.5 libgcc_s.so.1 libcxxrt.so.1 libcrypto.so.30 libc.so.7 libc++.so.1 Annotations : FreeBSD_version: 1401000 repo_type : binary repository : udi Flat size : 67.2MiB Description : PG3x Plugins manager for Universal Devices eisy/Polisy Release notes for 3.3.20 - 06/20/2025 - Added support for eisy-ui local login Release notes for 3.3.19 - 06/04/2025 - Auto-Logout timeout increased - After uploading profiles, trigger a profile reindex on IoX - Developer page: Add new buttons at the top Release notes for 3.3.18 - 01/27/2025 - Added enhanced webhook support (Required for Tesla plugin) Release notes for 3.3.17 - 12/10/2024 - Fix migration process (restore backup from another unit) Release notes for 3.3.16 - 11/26/2024 - Fix to Developer plugin edit Release notes for 3.3.15 - 11/20/2024 - Add support for upcoming eisy-ui - Fix plugin updates when using git Release notes for 3.3.13 - 10/16/2024 - PG3 is now available using /plugins/ route - Fixed /auth when serving from port 443 - Fixed portalAuth when account is using special characters - Minor bug fixes - New service files for PG3 and plugins - Security: remove token fron getNsInfo messages to plugins - Security: Submitting new plugins require a developer token - Node names are sanitized: /<> are replaced - Display the plugin edition in the details page - Log API requests to PG3 - Release for FreeBSD 14 --------------------------------------------- FreeBSD 13: PG3x last release is 3.2.27 FreeBSD 14: PG3x 3.3.0+ --------------------------------------------- *** Networking Information *** re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:21:b9:02:71:1e inet 192.168.0.151 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::2a30:5515:6cdf:a3c5%re0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=3<PERFORMNUD,ACCEPT_RTADV> lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> *** USB Devices *** ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: <AX201 Bluetooth Intel Corp.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) *** Upgrade Status **** UDX_UPGRADE_STATUS="inactive" Does anyone know how to telnet into the eisy?

I tried that. I found the IP address in my routers DNS table. The IoX launcher couldn't find the eisy. This is all very frustrating. I just want to get the thing working.

NEW PROBLEM: I downloaded the latest version of IoX finder (after clearing the Java cache first-all 3, actually). when running the IoX finder, it found the old ISY994, but NOT the eisy (the eisy appeared in the DNS cache of the router). When I removed the ISY994 from the network (and powered it down), and re-ran the IoX Finder, it still showed the ISY994 and not the eisy. What is going on? I cleaned the Java cache and reran the IoX finder, same thing-eisy was not found.