
DennisC
Members-
Posts
2787 -
Joined
-
Last visited
Everything posted by DennisC
-
I also used Mobilinc Pro and when my repeated request to support node servers was ignored, switched to UD Mobile. I am very glad I did. UD Mobile has proven to be reliable and very fast either locally or remotely. It is actively and continuously being developed and improved. Support is fabulous and available when needed. Since it doesn't cost anything to try, check it out for yourself.
-
Out of curiosity, are you accessing eisy remotely with your portal address? I have been successful accessing both an eisy and Insteon using my Portal address.
-
If it helps any, UD Mobile can handle most of the day to day needs with eisy. It can also let you do most of the programing and more functionality is added regularly.
-
I wonder if the ZWave board is starting to fail. At this point, I would normally say open a support ticket with UD and they will get to the bottom of it. However, free support for the ISY994 has ended. All that is available now is paid support and that is for a limited time period. If a new ZWave board is necessary, new parts are not available, you would be forced to source a used one. It might be time to start thinking about upgrading to eisy.
-
Are you renewing according to these directions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Renewal_Instructions
-
Support thread for: PG3x v3.1.29 (June 12, 2023)
DennisC replied to bpwwer's topic in Polyglot v3 (PG3x)
That is what should happen. Once you see that message, go to the admin console and upgrade packages. Might take awhile, wait about 30 minutes. You will then need to reboot. After going back in to Polyglot, you will probably see a message to restart Poliglot. After that you should be finished. -
Support thread for: PG3x v3.1.29 (June 12, 2023)
DennisC replied to bpwwer's topic in Polyglot v3 (PG3x)
You posted in a help section for PG3x, is that what you are running or are you on PG3? Can you tell us what your hardware is, all version #'s, Mac or Windows, etc. Also, what have you done and specifically what does "stuck" mean? -
Are you replying by email? That doesn't work, you need to go to their website, support, log in and reply on the service ticket. They will then get a notification.
-
I wouldn't discourage you from getting an eisy, but you could try responding to your ticket and requesting a remote session.
-
The log is saying a reboot is necessary. You have indicated you are not sure if the system is rebooting. Running sudo shutdown -r now will force a reboot.
-
That helps, now run: sudo shutdown -r now
-
What command did he have you run? If the command he had you run was to force an update, remember, you need to reboot when it is finished. Is this from the log? If so, it looks like it might be ready for a reboot.
-
Let's backup a minute and verify a few things. The Insteon 2413S PLM is a serial PLM and for it to work with Polisy, it requires: DB9 to RJ45 converter (Amazon Part) RS232 to USB converter (Amazon Part – Pinout ) 3ft Ethernet cable One or more of the components may have been damaged and may no longer be working. The Insteon 2413U PLM is an USB PLM and can plug directly in to Polisy. Do you have a different cable to try for this PLM? A few things to note: 1. Do not plug the PLM in to any type of surge suppressor, including a power strip that might have surge protection, or a UPS. 2. Try moving the PLM to a different outlet. Choose one with no power supplies or transformers on the circuit. 3. Try a different power supply for your Polisy. Any 12vdc, 2 amp power supply will work. Weak power supplies have been known to cause strange behavior. Be sure to plug the PLM in first and wait at least 30 seconds before plugging in Polisy. If none of this works and you can ssh in Polisy, ssh in and open the log by entering: sudo tail -f /var/udx/logs/log With the log open, upgrade packages Polisy via the admin console. After the log stops updating and Polisy is finished updating, post the output of the log. If you see the same output continually repeating, you may be stuck in a loop, but let's see what happens first. Polisy has a speaker and should beep 4-5 times after it has rebooted. That is not like them, you should update your ticket if we can not get you going.
-
Follow my instructions to use the multi function button. First try reboot, wait about 20 minutes and then clear Java cache and download start.jnlp. If that doesn't work, use the multi function button to upgrade packages. Wait about 30 minutes and follow the same procedure to clear Java and download start.jnlp. You may need to reboot again when you get into admin console.
-
To add to what @oberkcsaid above, the description for the Polisy lights is: All three lights on the front light up when powered on If BIOS does not need to be updated, after a few seconds, only the left most stays lit for up to a minute and then, all lights turn off, you'll hear a couple of beeps If BIOS needs to be updated, the 2nd and 3rd light keep blinking while the BIOS is updated and the unit reboots and follows the normal process Everything is operational once only the left most light is lit either initially or after BIOS update If the 2nd or 3rd light keep blinking for more than 3 minutes, then there is an underlying issue. Please review the Troubleshooting section. Is the green light on the PLM?
-
If it has been over 4 hours and you still can not access the admin console, then I would suggest using the multi function button. You could try upgrade packages or reboot. Upgrading packages will bring you to the latest version available, which would be v5.6.2. Update and Upgrade All the Packages Click the button once. Please consult support before updating this route. See link below for suggested update/upgrade process. Please see this important update (July 2022) Safely Reboot Click the button twice. Safely Shutdown Click the button three times. Be aware, after upgrading you will need to completely clear your Java cache and download a new start.jnlp, which when you run will place the IoX Launcher on your desktop. https://isy.universal-devices.com/start.jnlp
-
Verify Insteon support is checked on the Configuration tab.
-
If you are using a serial PLM with Polisy, you need the cabling shown below: https://www.universal-devices.com/product/serial-plm-kit/ If you have a USB PLM, it can plug right in to Polisy. Be aware, if you change PLM's, you need to do a restore PLM for it to work. I would suggest you power down, wait a bit, then power back up before changing parts.
-
Support thread for: PG3x v3.1.29 (June 12, 2023)
DennisC replied to bpwwer's topic in Polyglot v3 (PG3x)
And, if you happen to be running any node servers on PG2, you will loose them. -
What platform are you running on, Windows or Mac? Just as a guess, try clearing your state files: Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns: ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state There are some other causes for this, read about them here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Finder_does_not_find_ISY
-
Once upon a time, you could run node servers on a Raspberry pi, with the current version of Polyglot, that is no longer the case. Also, remember free support for your ISY994 has ended and there will be no further updates or development for this hardware. To utilize node servers today, eisy is the currently available hardware. It is much faster than the ISY994, and new features are being actively added.
-
The SmartBridge firmware is listed as 1.5.1. I am on Android & there doesn't appear to be a way to upgrade firmware in the Android app yet. Upgraded the node server and all is well know. Thanks!
-
No worries, but there looks like there is still an issue. While the shades no work, it is throwing an error. 2023-06-19 13:14:22,003 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 50 UOM 51 2023-06-19 13:14:22,003 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 50 UOM 51 2023-06-19 13:14:25,542 Thread-57 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:25,542 Thread-57 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:30,552 Thread-59 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:30,552 Thread-59 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:35,580 Thread-61 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:35,580 Thread-61 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,227 Command udi_interface INFO ryse:speed: set shade speed {'address': 'c702e129edd7', 'cmd': 'SET_SPEED', 'value': '85', 'uom': '51', 'query': {}} 2023-06-19 13:14:40,227 Command udi_interface INFO ryse:speed: set shade speed {'address': 'c702e129edd7', 'cmd': 'SET_SPEED', 'value': '85', 'uom': '51', 'query': {}} 2023-06-19 13:14:40,327 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,327 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,330 Command udi_interface INFO ryse:position: set shade position {'address': 'c702e129edd7', 'cmd': 'SET_POSITION', 'value': '0', 'uom': '51', 'query': {}}% 2023-06-19 13:14:40,330 Command udi_interface INFO ryse:position: set shade position {'address': 'c702e129edd7', 'cmd': 'SET_POSITION', 'value': '0', 'uom': '51', 'query': {}}% 2023-06-19 13:14:40,433 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,433 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,440 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 0 UOM 51 2023-06-19 13:14:40,440 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 0 UOM 51 2023-06-19 13:14:40,582 Thread-63 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,582 Thread-63 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:45,584 Thread-65 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:45,584 Thread-65 udi_interface ERROR ryse:query: query failed: 'speed'
-
To find your IP address look in your Eero app under DHCP & NAT section of Advanced settings. I posted the full DHCP instructions below. I am wondering if the subnet changed between your old router and the new. Do the IP addresses start with the same numbers? The eero mesh network offers a range of advanced features accessible through the eero app. These features include: Static IP Address Custom DNS DHCP and NAT Configuration IP reservations and Port Forwarding Band (Client) Steering. DNS: Your DNS translates an address like www.eero.com to an IP address that your phone or computer can understand. Your ISP typically provides an automatic DNS server that resolves web addresses. However, if you’d like to set Custom DNS, you can do so from the eero App. Tap the Settings tab, then select Advanced. Select DNS, then tap the Custom DNS bubble to enter your desired DNS server. DHCP & NAT: Under the DHCP & NAT section of Advanced settings, you can configure the way your eero network assigns IP addresses to the connected devices in your home. If you choose Automatic, we will automatically choose the best settings for your network. If you have a particularly complex home network, you can set custom IP address settings for your eero network. You’ll need to tap Manual, then choose your IP address prefix and specify the lease range manually. Finally, you can choose to put your eero mesh network in Bridge mode. If you choose to put your eero network in bridge mode, it will still provide WiFi access but you’ll need another router to provide network services. Reservations & Port Forwarding: Under this Advanced setting, you can assign IP reservations and port forwarding rules for devices on your eero network. Port forwarding allows you to manually open an Internet port for a single client, to let traffic pass directly through to that machine. For example, if you wanted to run a FTP server on your laptop with IP address of X.X.X.X, you might create a port-forward on port 21 that directs TCP traffic to that IP address through your eero. Check out our detailed directions here on how to set up port forwarding. UPnP: Universal Plug and Play (UPnP) allows devices like game consoles and media centers to open direct connections to other devices on the Internet. We enable this feature by default. If you’d like to turn it off, toggle the slider so it’s no longer green. Band Steering: Many devices are dual-band capable, meaning they support both 2.4 GHz and 5 GHz. 5 GHz is typically less crowded and offers higher performance. Band steering tracks whether a device has previously been seen on both 2.4 GHz and 5 GHz, and if so attempts to “steer” it to 5 GHz to improve long-term device performance. Band steering does not guarantee that a device will choose the 5 GHz band, but helps to favor that preference. eero DDNS: eero DDNS, available to eero Plus customers, gives you the ability to remotely access your network easily regardless of if your dynamic IP changes. With the new DDNS feature in eero Plus, users receive a unique hostname for their network that is simple to recognize and recall.
-
Is your ISY connected via WIFI or ethernet?