TheA2Z

Thanks @Techman Its fixed. Im on PC. I did the java, and new IoX Launcher again but what i think fixed it was I went through all my backround tasks. I ended the vpn even though it was not on as well as other background tasks. Started working. 😀

Upgraded, rebooted, ensured Im on latest Java version, cleared app in Java, downloaded new Start file. I also can also ssh admin@<IP> at the command line. I can connect with phone via UD Mobile and from web app in Portal. When I open the Admin GUI, it wont list the EISY url that I can click on to connect to. Any recommendations before I open ticket? Sysconfig File below *** 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 Jun 19 16:07:42 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 Jun 19 16:07:33 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 : Fri Feb 14 17:17:04 2025 EST 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 : Fri Feb 14 17:16:11 2025 EST 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 : Fri Feb 14 17:17:06 2025 EST 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.19 Name : pg3x Version : 3.3.19 Installed on : Thu Jun 19 16:08:10 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 nodes 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:5f:80 inet <IP> netmask HGidden broadcast IP inet6 fe80::3802:f222:9f4e:2522%re0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX <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: <CP2105 Dual UART Bridge Silicon Labs> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.3: <PL2303 Serial Port / Mobile Phone Data Cable Prolific Technology, Inc.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: <AX201 Bluetooth Intel Corp.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) *** Upgrade Status **** UDX_UPGRADE_STATUS="inactive"

Upgrade went fine including pg3 My ip address did change though.

Thanks to @Michel Kohanim for getting me back up and running. I opened ticket and he responded with: Please reboot using the following method: 1. Press/hold power button -> red 2. Click again -> blue Everything working again.

@Pmool No, I turned off Zigbee support. Rebooted and reloaded admin Gui. Doing same as above.

@Techman Ok thanks

Completed Upgrade. Downloaded new GUI. Cleared apps in Java. Reinstalled Gui. Shutdown EISY. Disconnected power for 30s and then plugged back in. Noticed the following: Once Gui comes up, top green buttons for Automatically write changes and Include battery devices cannot be turned off when clicking them. After about 5m, a box pops up stating to Authenticate ISY. When I put login and password in and click ok, a box pops up and says the system has been restarted Please start a new session. When I go to config tab and portal tab there is no connection to Portal Any help or suggestions would be appreciated.

No. They are wired EISY with zMatter. Thanks

My zwave devices are functioning but when I try to do an "Update Neighbors" on some devices the update neighbors fails. Screen shot below. Note that it appears that the devices further away from hub are doing it, but not all of them. I can do a successful "Update with Interview" on the devices and I can do a successful "rewrite all device links". Anyone else having this problem? Anyone have a fix?

Anyone?

Any plans for EISY to support Zwave 800 devices? I know they are backwards compatible but looking for EISY to be Zwave 800.

Not to be a "Debbie Downer" but what does this give me to upgrade? My Yolink hub is plugged into same Battery Backup APC as my eISY so nothing there. It has a Cellular hub. I have a dual WAN setup with Tmobile Home internet (5G Cellular) and Xfinity cable modem. Ubiquity router switches to Tmobile 5G modem if Xfinity is down. Its still not a true local hub as it uses cloud over cell. If you dont currently have a battery backup or dual wan, I can see a reason to get. I dont know how much that sim card and service will be but Tmobile 5G home internet is $50 a month with no minimums. However speed varies and is not available everywhere.

This is why I use a Zwave motion, Temp and Humidity sensor in shower area of bathroom. Using motion, fan comes on for 5 minutes if someone uses the bathroom and stays on for 5 min. The motion gives the humidity sensor time to stabilize in that 5 minutes if using the shower and stays on until humidity drops to the desired level. However, I dont find the zwave connection to eisy stable on these battery motions. Sometimes I have to remove battery and reinstall to get it to reconnect. That is why I would love yolink to create a motion with temp and humidity so I can mimic how I do it now. Yes I could put a yolink motion and temp/humidity sensor but would prefer not to have so much hardware on ceiling and it makes it costlier.

Good plan. Would love to hear how the motion analysis turns out. Not a big fan of the insteon and zwave motions I have now. I wish they offered a motion with humidity sensor too. I have these zWave in bathrooms now. So far yolink has been rock solid on the temp sensors in fridge and freezer and water leak detection. Integration with eISY has been perfect too. I will really look at going Yolink before zwave devices going forward. Only drawback is Yolink does not have a local hub yet. Everything goes to cloud. Has not been a problem yet but connection with Eisy would stop working if internet was down. Not an issue with me as I run a dual wan at the house since I need always on internet as I work from home. Their new hub is supposed to offer it but still not released.

Nice. I still have a zwave outlet strip from Zooz for a few years that works really good. May look at yolink if it goes poof. Be interested in how the motions do. They make an outside version that I will need to try. Right now I have motion floodlights on zwave switches. I find motion floodlights to have alot of false alarms no matter how much I adjust the sensitivity. I wonder if Yolink will be more concise. It would also enable me to point the motion more strategically vs just where the floodlight is. Also want to try inside motions too as my zwave battery motions are just ok.

I would think that it would change the resistance of the cable skewing results. Does it offer a temp offset in the sensor where you can calibrate it so it would be accurate with the longer cable? I had to offset the temp of a Yolink temp sensor in my fridge as it was off a little. Was able to do it in Yolink app.

So far so good. just wanted to give the forum my perspective. Isy user since 2016 with over 70 insteon, zwave and matter (Smartthings) devices controlling/ detecting leaks, hot water recirc, lights, motion, Temp, humidity, fans, humidifiers, mailbox, shades, LEDs, alarms and AV. You can say I am hooked... Now adding Yolink. Bought the speaker hub, 3 leak detectors, two temp Humidity sensors for the fridge and freezer, two outdoor contact switches(1 for Luba robot mower to ensure still in dock at night and 1 for my hot tub cover to ensure its closed when Im not home. Got them all on Amazon for less than Yolink site and 1 day delivery. Bought the PG3 Yolink node. Install was very cut and dry on Eisy with PG3. Works great. Have been running insteon leak detectors for years but get bad intermittent reception on a couple of them. Full strength signal with Yolink. Nice that they have a siren on the actual device as it makes it easy to determine where the link is quickly. I still have quite a few Insteon leaks but will only replace if they go bad. Nice to have full strength signal in the fridge and freezer too. Alerts setup in case fridge breaks or other outage. Will continue to monitor but I have high hopes for Yolink due to increased signal strength and distance. Not to mention uses regular AA batteries with some devices getting 2 to 3 year battery intervals. I will definitely look to see Yolink options going forward vs zwave for any new devices.

I've been using this for over 4 years. Heavy duty. Had a Dome but it wasnt strong enough to turn valve over time and stopped working. Recommend a mount on type over a built into the valve model. Much easier to replace if there is an issue. Bulldog Valve Robot (econetshop.com)

@Geddy Perfect. Ill delete the old port forwards. I use UD mobile and have Portal sub.

@Michel Kohanim Actually I am. Are they not required anymore? Had this setup from a few years ago. Do I just delete the port forwards now on the router? Do I need any port forwards for eisy to work? I use UD mobile.

Thanks @Michel Kohanim ANy idea on the second item I listed? In between those times, I got random Authorization errors. How do I tell what device is throwing the Auth errors to fix this?

@Michel Kohanim Ticket number is 21458. I did a test. I cleared error log at 121PM. Top part is while I am still logged into Admin. I only have level: 1. Status/Operational events in event log selected. I then log out of admin console at 137PM I get the IoX service errors while logged into admin at 121PM and then when I log back in at 252PM. I didnt get them when I was not logged into Admin. What can cause this? In between those times, I got random Authorization errors. How do I tell what device is throwing the Auth errors to fix this? Time User Code Message Mon 1900/01/01 12:00:00 AM System -170001 <s:Envelope><s:Body><u:GetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetDebugLevel></s:Body></s:Envelope> Tue 2023/11/21 01:21:41 PM 0 -170001 <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetErrorLog></s:Body></s:Envelope> Tue 2023/11/21 01:22:20 PM 0 -170001 <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"><option>0</option></u:SetDebugLevel></s:Body></s:Envelope> Tue 2023/11/21 01:22:20 PM 0 -170001 <s:Envelope><s:Body><u:Unsubscribe xmlns:u="urn:udi-com:service:X_IoX_Service:1"><SID>uuid:26</SID></u:Unsubscribe></s:Body></s:Envelope> Tue 2023/11/21 01:37:13 PM 0 -170001 --308e3d4e328700b91b02df3a1ddaa85e Content-Disposition: form-data; name="x_Setting"; filename="x_Setting" 0 --308e3d4e328700b91b02df3a1ddaa85e-- Tue 2023/11/21 01:38:50 PM 0 -170001 --308e3d4e328700b91b02df3a1ddaa85e Content-Disposition: form-data; name="x_Setting"; filename="x_Setting" 0 --308e3d4e328700b91b02df3a1ddaa85e-- Tue 2023/11/21 02:14:14 PM 0 -170001 --308e3d4e328700b91b02df3a1ddaa85e Content-Disposition: form-data; name="x_Setting"; filename="x_Setting" 0 --308e3d4e328700b91b02df3a1ddaa85e-- Tue 2023/11/21 02:14:14 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:18961->64288 Tue 2023/11/21 02:15:50 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:4705->36895, Tue 2023/11/21 02:51:11 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:3691->64288, Tue 2023/11/21 02:51:20 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:17932->64288 Tue 2023/11/21 02:51:20 PM 0 -10108 Check log Tue 2023/11/21 02:51:21 PM 0 -170001 --308e3d4e328700b91b02df3a1ddaa85e Content-Disposition: form-data; name="x_Setting"; filename="x_Setting" 0 --308e3d4e328700b91b02df3a1ddaa85e-- Tue 2023/11/21 02:51:21 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:24097->64288 Tue 2023/11/21 02:51:21 PM 0 -10108 Check log Tue 2023/11/21 02:52:51 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:59622->36895 Tue 2023/11/21 02:52:51 PM 0 -10108 Check log Tue 2023/11/21 02:52:57 PM 0 -170001 --308e3d4e328700b91b02df3a1ddaa85e Content-Disposition: form-data; name="x_Setting"; filename="x_Setting" 0 --308e3d4e328700b91b02df3a1ddaa85e-- Tue 2023/11/21 02:52:57 PM 0 -170001 [Auth:-10104] ::ffff:80.94.95.226:47707->36895 Tue 2023/11/21 02:52:57 PM 0 -10108 Check log Tue 2023/11/21 03:19:58 PM 0 -170001 <s:Envelope><s:Body><u:GetISYConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetISYConfig></s:Body></s:Envelope> Tue 2023/11/21 03:20:17 PM 0 -170001 Authenticate Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetStartupTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetStartupTime></s:Body></s:Envelope> Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/INTEGER.VAR</name></u:GetSysConf></s:Body></s:Envelope> Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/STATE.VAR</name></u:GetSysConf></s:Body></s:Envelope> Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>1</type></u:GetVariables></s:Body></s:Envelope> Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>2</type></u:GetVariables></s:Body></s:Envelope> Tue 2023/11/21 03:20:18 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope> Tue 2023/11/21 03:20:19 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope> Tue 2023/11/21 03:20:20 PM 0 -170001 <s:Envelope><s:Body><u:GetNodesConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetNodesConfig></s:Body></s:Envelope> Tue 2023/11/21 03:20:22 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemTime></s:Body></s:Envelope> Tue 2023/11/21 03:20:23 PM 0 -170001 <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"><option>1</option></u:SetDebugLevel></s:Body></s:Envelope> Tue 2023/11/21 03:20:23 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope> Tue 2023/11/21 03:20:23 PM 0 -170001 <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_IoX_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration><send>F</send></u:Subscribe></s:Body></s:Envelope> Tue 2023/11/21 03:20:23 PM 0 -170001 <s:Envelope><s:Body><u:IsSubscribed xmlns:u="urn:udi-com:service:X_IoX_Service:1"><SID>uuid:27</SID></u:IsSubscribed></s:Body></s:Envelope> Tue 2023/11/21 03:20:24 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Tue 2023/11/21 03:20:24 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Tue 2023/11/21 03:20:24 PM 0 -170001 <s:Envelope><s:Body><u:RefreshDeviceStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"><sid>uuid:27</sid></u:RefreshDeviceStatus></s:Body></s:Envelope> Tue 2023/11/21 03:20:25 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Tue 2023/11/21 03:20:25 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Tue 2023/11/21 03:20:29 PM 0 -170001 <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope> Tue 2023/11/21 03:21:14 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Tue 2023/11/21 03:21:22 PM 0 -170001 <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetErrorLog></s:Body></s:Envelope>

Ah yes. "That was easy". I must of overwrote it in the past. Thanks @Michel Kohanim

Actually duh, I opened a ticket on this 6 months ago. Just asked for status. Previously @Michel Kohanim said it was on the list.

Thanks @Geddy Ill open a ticket as they happen very frequently. Have a Happy Georgia Thanksgiving.