timlacey
Members-
Posts
36 -
Joined
-
Last visited
timlacey's Achievements
New (2/6)
0
Reputation
-
Also when I go to the UD Mobile app and try to view node servers or go to Polyglot home, it tells me bad username or password? I tried admin/admin and also the one I'm using successfully to log in to the ISY. . . neither works? And I tried using the "magic button" 3 times to reset passwords, yet my previous password is still in force. everything about the EISY just seems to be wrong.
-
OK, tried this. The six button trick to shut down, and then the eisy web interface shows the exact same thing as above. My IoX finder is now working for the first time, though. I generally keep clearing the cache, but that's working now anyway. I tried to go to the ISY settings->config and do upgrade packages again. 30 minutes later I tried again to update the firmware through the UD mobile app. I haven't tried the "magic button" single press to prompt an update yet. . . it says to wait until support says to try that. I don't know where the "current versions area" is, but the UDmobile app offers an update from 5.6.2 to 5.7.0. As per the migration instructions from ISY994, I tried to upgrade before importing my ISY backup. . . but apparently the upgrade hadn't worked so perhaps now it can't upgrade because my ISY backup is causing issues? Maybe I should factory reset the EISY and try again - except I've already transferred all the licenses to the new one running on EISY. Nothing is working quite right . . everything seems off. . . my log files are filled with can't connect to IoX even though its localhost. . . Tim
-
When I go to the polyglot dashbaord, I see no node servers. I am running ISY but it's not behaving properly. I'm unable to upgrade firmware. Upgrade packages (from the ISY admin console) does nothing. The upgrade firmware button on the UD Mobile app does nothing. I just want to get to a point where everything is working and stable but I don't know how to push it to that point. Also, my device doesn't show up in IoX finder and I always have to manually use the IP path. When the screen below first came up, it showed iOX as disconnected. I had to say "autolocate" in the menu for it to turn green. This just doesn't seem right? Node Servers PG3x Version 3.1.33 Status: ConnectedPG3x Restart Required Frontend Version: 3.1.35 IoX Version: 5.6.2 Connected Uptime: 9 Hour(s) 12 Minute(s) 20 Second(s) (c) 2023 UDI Getting Started
-
I had a similar problem and simply needed to remove and reseat the microSD card.
-
The YouTube video showing how to link the ISY Portal and Alexa says that the spoken words will sync both directions with the ISY. If this is not the case any longer, why is there still a SYNC button? Anyway, it doesn't work for me, so I assume the post above is correct that it does not work. Shouldn't it? Why would the portal list of spoken commands not sync with the ISY?
-
Will try that soon. I'm surprised there isn't any better troubleshooting capability with the PLM. I got the list of PLM links and I wish I had a way to compare against the list expected by the ISY. I saved a copy of the links from the PLM and I searched on the ID of both keypadlincs. The one keypadlinc found a few entries, but the newer one added under 3.1.10 and again under 3.1.12 showed nothing. Tim so far did the backup restore and got an error uploading file. . file size error. . . ugh. did the backup restore with a wired connection and all ok. . . restarted. removed out of date devices (lamp and old keypadlinc) rebooted ISY added 2 new devices - a dualband lamplinc and a dualband keypadlinc (2487s) set one button on the 2487S as a controller to test with ISY and PLM checked and upstairs 2487s is still not showing up on ISY rebooting ISY again (it can't hurt, after all) restoring modem now. .. after restore modem (takes a good long time but I let it finish uninterrupted),ISY is acting dead to the world. . . no status shows up for any device, and it doesn't even see a standard dimmer switch near me. i cannot query devices. I check PLM links and when I hit start, nothing happens. I unplug the PLM and plug it back in. . . nothing different. i rebooted the ISY (i could perhaps have just closed My Lighting and started a new session. . . ) and now it can query. now it can see the dimmer next to me. now the PLM loads in just fine. Now I seem to see all my devices once again. . . . I linked the new keypadlinc to all my scenes. . . all good. Everything seems to be working. Thanks, Tim
-
Tried that. First I confirmed that the PLM links did not contain links for the keypadlinc. So I deleted the device. Then after a while, I restarted the ISY admin and saw buttons A, G, and H still there. So I deleted the device again, and it went away. Then I reset the console (closed and logged back in) and added the keypadlinc again. Still nothing. it seems that the PLM is not getting programmed for it. I do see in the log, writing PLM group commands, so I assume it's happening. So the KeypadLinc is back in the ISY, but still doesn't see any commands from the keypad. And the keypad works great as a controller for other switches. . . So what's up? And how can I fix this? Is restoring the PLM still the preferred solution? If so, I can do it tomorrow during the day. . . Thanks, TIm
-
Yes, they match up and they are identical. What I believe is that the PLM links are wrong or missing. But counting the PLM links takes so long and seems unreliable. Tim
-
I had upgraded from 2.8.16 so that's the only pre 3.0.10 backup I've got. You think that will should work better. Another thing - the second keypadlinc was a new one I added in 3.0.10, so it wouldn't have been an import problem. It is the new dual-band one. I added it after the upgrade rather than doing it before. Is there any link table I can compare to check on this? Doesn't a device restore restore the PLM links as well? What you're proposing seems like a lot of work, especially if I know that one keypadlinc is not failing as a result of the database upgrade process? Would deleting and re-adding the device to the database solve the problem? Tim
-
Hi, I recently replaced a faulty PLM and restored the PLM and devices with ISY. Everything works fine, except two of my keypadlincs (one of them a new dualband 2876S) do not show up in the event viewer. I would assume this means that eh PLM is lacking links for the keypadlincs, so I've restored device a couple of times on both. They still don't work. They control all the scenes with the other keypadlincs fine, they respond to all scenes just fine. The ISY just doesn't see any key presses from them. How should I troubleshoot/fix this? I'm running 3.0.12 now and had been running 3.0.10 when I did the PLM restore. Tim
-
FYI. . I noticed that when I rename my keypadlinc buttons, I have to restart the WebUI to reflect the new names. I had tried sorting to refresh the list, but that didn't help. I had to close and restart the Admin Console. I don't recall ever having this problem before, so I thought I'd mention it. It happened whether I renamed a single button or did the "all associated devices" naming interface. ADDENDUM: Now it is working. So perhaps it is not an issue.
-
So that I understand completely, let me tell you my story. I have two buttons E and F on every keypad that i want to stay in synch. they are mutually exclusive on each keypad. They are used for two different exclusive lighting modes. I used to set the grouping on each keypad for the two to be mutually exclusive, and then run a program (just like as shown in the example in this thread). For example, turning on button E would instantly turn off F locally but then the program would run to turn on the scene with all of button E and turn off the scene with all of button F. In the end, all the KPLs would match. With you phasing out groupings and asking us to do it all via scenes, I reworked it: For the scene that turns on all the E buttons, I added the F buttons with a value of 0, thinking that pressing any E would turn on all E buttons and turn off all F buttons. I then noticed that I can't set the global attributes for the scene and that I can set it for each controller but only the local OFF works. But then what's the point? If this DOES NOT WORK, then the groupings are required as before. Can you confirm that I need to use groupings and go back to the way I had it before? And if groupings don't work, the program that runs will replace the grouping features, albeit more slowly and with more ISY traffic/activity. Thanks, Tim i'm using 2.7.0.12
-
Is Last Run a new feature? I can't find it as an option under SCHEDULE?? I'm running 2.7.2. Thanks, Tim
-
My 5012 errors and the following 10011 errors appear to come from the Homeseer plug-in. I will send a note to Bob about that one. The file open errors for /CONF/F and /CONF/9 seem to be a problem - should I backup the system and upgrade to 2.7.3 and see if those errors stop? Is a -2 error for no device anything unusual?
-
I apologize. A new search revealed a link to this: http://www.universal-devices.com/mwiki/ ... r_Messages So my answer is already there. . . now to figure out what these errors are. . .