Techman
-
Posts
5174 -
Joined
-
Last visited
Everything posted by Techman
-
@richardw Try removing power from the eisy for a minute. After it boots up try adding the swtch again.
-
IOX Launcher not finding eisy - after clearing java cache and reloading
Techman replied to twired's topic in IoX Support
From the UDI Wiki: ISY Launcher cannot find ISY Make certain that you are using ISY Launcher. This is a MUST If you have VPN software running, Admin Console cannot search for ISY on your computer. Please disable the VPN, find ISY's IP address and then click the Add button and enter it manually Make certain that, after reboot, the pattern of lights is as described here If you have recently changed your modem/router, please follow these instructions If you have any firewall software, make sure it's configured properly If all the above have been checked, it's almost a guarantee that that your ISY is not on the same network as your computer. Perhaps at some point you might have configured ISY with a static IP address. Or, that your WiFi network is not connected to the wired network. -
@smorgasbord Try using Multimedia Messaging Service, which AT&T still supports. (your phonr number) @MMS.ATT.NET
-
I just logged onto the UD Ticket website and wasn't presented with a Captcha. https://www.universal-devices.com/my-tickets
-
Take a look at these issues with a MAC Universal Devices, Inc. Wiki
-
@smorgasbord Being that your email was working on your ISY It's probably best to submit a support ticket. You should get a quick response. https://www.universal-devices.com/my-tickets After you get it resolved, post the action taken.
-
Just looked at your error log. Your SMTP settings are either incorrect or you don't have an good internet connection. Check your eithernet cable. Are your firmware and UI the same version? It's also possible that your migration got corrupted. There's no option to write messages to the admin console, not sure about UD Mobile. There are 4 eisy files in your windows temporary folder starting with UDI_TREE.STATE. You can delete them, which may or may not help.
-
@smorgasbord Can you post a copy of your error log. You might also try rebooting the eisy. Being that your regular email account works, why not use those settings for the eisy rather than the default SMTP server
-
My error, I see that you're using txt.att.net. Do you have the TLS box checked. You should also increase your timeout to 9,000 The above may resolve you issue. let me know
-
AT&T blocks most email to SMS messages. They use a very agressive spam filter. You should be able to use TEXT from the eisy however the message may not format properly. Have you tried using your own email server rather than the default server? Which ISP are you using?
-
Glad to know we're not alone
-
I don't believe there's an option for retries on the 2477. You could add a plug-in module that would act as a repeater and most likely improve you insteon communications. You should also verify that both sides of your powerline are bridged via dual band modules. Take a look at these links INSTEON Signal / Noise Troubleshooting - Universal Devices, Inc. Wiki INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki
-
If you're using only Insteon devices you won't lose any functionality other than the ISY may not support some of the newer Insteon devices. Not sure if a new portal license can be added to the ISY, you can submit a suport ticket to UDI for an answer.
- 1 reply
-
- 1
-
-
It didn't happen to me during the previous time change. Guess it's a little glitch in the current firmware.
-
After the end of Daylight savings tme none of my sunset or timed programs ran Sunday night. The time was correctly displayed in my eisy. I did a cold boot and will see what happens tonight.
-
Try removing power from the controller for a few minutes. If that doesn't resolve your issue then post a copy of your error log
-
Delete the sensor from your eisy, factory reset your sensor then brng it close to the PLM, put it in the linking mode and then add it to the eisy. If it adds to the eisy but doesn't work properly when it's relocated then it may be due to poor communications between the eisy and the sensor. You may have to add a dual band plug in device between the two which will act as a repeater. Restoring the PLM and replacing the PLM was most likely not necessary, especially if your other devices are all working properly.
-
@PB11 A lot of the carriers are either not supporting, or fully supporting, email to text or SMS coming from a device other than a smartphone. This is most likely due to the extreme spam filters they're using. Thus far I haven't found a workaround to correct the formatting issue..
-
@mikek Be sure to update the firmware on your eisy. After you restore your backup to the eisy check all your programs and scenes as some may need a little tweak.
-
@mikek If you're using your previous serial PLM, did you purchase the required serial to USB conversion cable?
-
The ISY backup is located on the harddrive of your computer. It's named IoX-Backup.v(your firmware version #)_(date of backup) Your existing ISY firmware is OK for the migration. If you're using the same PLM you had on the ISY, then power down both systems, Remove the PLM from the ISY and connect it to the eisy, then power up the eisy. On the eisy, under FILE, select restore IoX. Select the ISY Backup file you just created
-
The green 1011 means that there are pending writes to that device. Put the new motion sensor into the linking mode, then right click on the device and click on write updates. Right click on the old device then click on delete. You may have to reboot your ISY first. You should only have one battery operated dvice in the linking mode at a time otherwise there's a chance their link tables get crossed..
-
One last thing you can try, delete and then recreate your two programs. I've seen rare cases where a program can get corrupted.
-
Can you turn it on and off from the admin console? It's possible that one of the led bulbs has a bad/noisy driver. Try removing two of the bulbs then run the THEN clause. What's your controller firmware and UI version?
