bikerbobhain

OK ... I found the problem. The EISY changed the address but you have to update the portal. The portal is where the device address gets connected to the Alexa spoken. lt should have been obvious ... I'm just a bit slow

I recently replaced a burned out Insteon led bulb. I can no longer control this from Alexa. The problem is that Alexa has the old device address. What I have done.... 1) The new bulb has the correct address and works fine from the hub. 2) I removed the device from the Alexa app and reran device discovery. 3) The device was discovered but has the address of the old bulb NOT the new addresss in the EISY. 4) I disabled the skill and re-enabled it. The same result it finds the old device address. 5) Rebooted everything (EISY, Device with the Alexa app, and the Router. After re-discovery it still has the old device address. Has anyone else had this experience? How did you fix it? Thanks in advance

Michel came through ... This is the answer to this issue ... Linux does not support Java reflection. What you need to do instead is to go to: https://eisy.local:8443/admin.jnlp That enabled me to talk to the EISY. We are moving forward again!!!! Thanks to all who responded and a special thanks to Michel who didn't give up on a tough problem.

I'm on OpenSuSe Tumbleweed. I have Java. My old ISY worked so I must have a working Java install. Of course the license got transfered so I can't use the old ISY. I am aware of the install page and have read it several times. I believe I have followed these instructions. ---------------------------------------------- I pushed the multi function button ... Waiting 30 minutes ... OK time is up ... pushing mf button 5 times Waiting ... OK time is up Cleared Java cache. Downloaded new start.jnlp file and ran it ... see attached finder.jpg Clicking on the finder gives me the menu. Selecting "Admin Console (lan) A brief spin icon followed by nothing. Further clicking yields nothing (no menu) and no icon. I see that in the title bar it read Not Found. If this applied to the EISY I can say that it is there. I can ping it ... PING eisy.local (10.0.0.35) 56(84) bytes of data. 64 bytes from EISY (10.0.0.35): icmp_seq=1 ttl=64 time=0.287 ms 64 bytes from EISY (10.0.0.35): icmp_seq=2 ttl=64 time=0.186 ms 64 bytes from EISY (10.0.0.35): icmp_seq=3 ttl=64 time=0.256 ms I can telnet to it ... noname% telnet eisy.local 8443 Trying 10.0.0.35... Connected to eisy.local. Escape character is '^]'. ^[ Connection closed by foreign host. If I point a browser at https://eisy.local:8443/desc I get ... (see second attachment) The UD app shows connected. (My original ISY is not online.) (see third attachment) Well this is were I'm stuck and that is all I know browser-return

I did start a ticket. They suggested I ask the forum as it may be faster..

I am trying to replace my ISY with the new EISY home. I tried to follow directions but must have done something wrong. What I can see: 1) My new EISY shows up (My Home) on the portal login. The connection button is green. 2) The information tab shows ... UUID: 00:***removed*** Alias: My Home Product: 5226 eisy External IP: ::***removed*** Internal IP: 10.0.0.35 Encryption used: TLS_AES_256_GCM_SHA384 Admin Console URL: https://my.isy.io/isy/.... (Suggested I remove these) URL to ISY : https://my.isy.io/isy/.... (Suggested I remove these) Features installed OpenADR Networking Module Portal Integration - UDI Z-Wave Module A10/X10 Module 3) Portal License shows ... UUID: 00:***removed*** Alias: My Home License Active: Yes License Expiry Date: 2024-10-12 Purchase History: Date purchased Start date Expiry 2017-10-12 2017-10-12 2019-10-12 2019-10-04 2019-10-12 2021-10-12 2021-09-26 2021-10-12 2023-10-12 2023-10-12 2023-10-12 2024-10-12 4) Trouble shooting tips shows ... Everything appears to be configured correctly! 5) Neither of the URLs (See item 2 above) will connect. 6) Under Maintenance the reboot tab says it will reboot but the EISY does not seem to reboot. A ping set to my internal address of 10.0.0.35 does not stop, so I don't think it is rebooting. 7) After clearing cache and using the ISY Web Access tab. I get a page... "https://my.isy.io/udajax/udajax.htm?mode=corp " after selecting "Settings" then "Clear Cache" (responds cache cleared} then "Install Admin Console (Internet)" I get a page "https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop" I then select Clear Java cache which I clear but removing /home/bob/cache/icedtea-web (I'm on OpenSuSE Tumbleweed). I then select ISY Launcher which downloads start.jnlp I then run start.jnlp the IoX Fjinder appears and after a few seconds it fill in my device. The first click yields a menu that shows a menu with System Console .... plus other stuff. Any selection results in the menu going away and nothing happening; After the initial start its is just a window that seems to accept nothing. You can seem to get any response. The buttons at the buttons on the bottom work but selecting "Add" and entering the local IP results in "Not Found" ------------------------------------------------ The UD app shows the EISY as My Home and Connected but there is not much I can do with the app. Under that it says ... System home ERROR: Requested ISY not online. 503 system not online or not communicating with Universal Devices Portal Veryfy your System is connected to network. Try reboot Rebooting changes nothing!

My bad for not reading carefully. Thanks much

I have a 994i with a z-wave dongle and serial modem. I ordered a esiy and z-matter to replace my older unit. I could not resist the Cyber Monday Coupon. I also have a new USB plm to replace the serial interface. I have looked at migration information but they don't seem to address the change of modem during upgrade. Does anyone know what other steps I must make to do the complete (w/ USB modem) upgrade? Any special steps? What order? Gotchas? Any help will be appreciated ... THANKS in advance!

Looks like I have the same issue. It 8:28cdt here.

The program is working well. It is very quick to respond. Good work BUT.... I have an observation/request ... Please note that many home automation users have a lot of devices and often employ Alexa (Amazon) to control parts of the installation. Button controllers are out of the question and tablet based systems are cumbersome and slow. If you setup a program in the Alexa environment "Alexa ON" runs the THEN part of a program and "Alexa OFF" runs the ELSE part. The icon you use for a program looks much like the icon for a switch. It would be nice if there were a way to mimic the Alexa ON/OFF protocol. Turing a program icon on would run the THEN part of an associated program and turning the icon off would run the else part. This provides a program entry point that integrates the ISY/Alexa environments. Thanks bob

I did not. I did not know how it worked. That did fix the problem. Is there any documentation (manual) for this program. I know it is early and everything may still be developing so I understand If it has not happened yet.

I have used the following format for many of my lights. 1) A default on level for a device (most common desired brightness / used as "Alexa turn on the light `) 2) A dim value implemented as a scene (attached to "fast off" if there is a switch / also used as "Alexa turn on light dim" 3) A bright value implemented as a scene (attached to "fast on" if there is a switch / also used as "Alexa turn on light dim" When registering these as favorites the scenes work as they did on the Devices and Scenes page BUT the device DOSE NOT". The favorites device icon lacks the little dot and can not be used to turn on/off the device by simply clicking on the icon. Scene favorites work the same as on the Devices and Scenes page (icons have dots). I don't know if this was intended (a feature or a bug) but it would be handier for my use if it worked the same on the Favorites page as it does on the Devices and Scenes page. Thanks

Good job ... careful inspection revealed a directory without a name. Things now synchronize and I have Variables too. Please accept my apologies. I did not understand what the error message was pointing me to. I did support work for a while and I try to resolve things on my own if possible. Thanks and Apologies

I'm not sure what happened but I ran z-wave synchronize nodes and repair links. After that it looks like I now have Devices and Scenes and My Programs. Variables both Integer and State are still missing. So I don't really know what is going on here but it look like progress. I'm still working on the variables.

I tried to setup the UD mobile app but when I try to sync and save I get the following error message. Error: java.lang.illegalArgumentException. Devices - Node Name - MUST BE A STRING Any insight ... what can I try?