stillwater

I am reluctant to use the staging repository because 1) there is the warning not to do so unless UDI has instructed you to. 2) It is not clear to me that it is possible to downgrade to earlier versions. (I was unable to downgrade from Beta to the Production instances and even restoring from an old backup did not restore the production versions).

I have a node server that I developed and that is only useful to me. It seems to have survived migration from ISY-994i to eisy (current production repo version). Will this continue to work going forward? Do i have to put my plugin in a local store? The node server (now plugin, I guess) is not complicated -- though I wrote it when node servers were brand new and didn't document it. -- It connects IoX with my climate control computer and a separate auxiliary processor to control a sauna. It defines a node with a few custom states, with the states updated via REST and a scene (involving insteon KPL buttons), and programs that activate network resources to communicate to the climate control computer. There is also a (probably redundant) communication channel between IoX and the auxiliary processor (a raspberry PI programmed in Dyalog APL) that uses the SOAP WSDK (not Java). Update -- I believe that in 6.1.1 when I right clicked on the node it gave me configuration info. But that might be wrong. I might be remembering access via the admin console. I just switched to the beta repo. In eisy-ui when I right click on configuration it sends me to a plugins Dashboard where it gives no information on my plugin other than its name and that it is unmanaged. By contrast the admin console gives access to an X-ray menu that includes "all profiles (JSON)" that appears to provide the definition for the node. I have no idea how to load or edit such info via the admin console or eisy-ui. I have no current need to do so if the node server keeps working. But it does seem that there is something missing in eisy-ui compared to the admin console. Certainly eisy-ui should continue to give full node definition info. I vaguely remember that I uploaded the node definition profile files to ISY using REST. This was probably before the portal or maybe even polyglot existed, certainly before PG2 and PG3. Further Update -- I see the Admin Console has a plugins menu item at the top that lists my node server and also has a configure menu for the various plugin slots. I don't see this anywhere on eisy. Third Update -- It appears that when certain things happen on eisy (package upgrade? plugin refresh? restore from backup), I need to reenter the password for my node server communication through the admin console -- top ribbon menu plugins/configure/choose slot/ Password. This box ends up blank rather than having dots in it. I don't see equivalent functionality in the eisy-ui (beta repository). I don't remember how I originally entered this information (which is for access to a web service on an auxiliary computer)-- there may have been a node server menu item in the admin console or it might have been created in the node server profile files -- but in the eisy it needs to be entered while I never had to do that with changes to the ISY-994i.

It would be nice to have a comprehensive user manual for eisy-ui, and for those of us who are used to the old admin console, a cross-walk document that tells users how to accomplish via eisy-ui all the things that could be done under the admin console. My current question is about how to view level 3 (device communication) events live, as was possible in the AC under tools/diagnostics/Event Viewer. No shame if this isn't available yet -- but I hope it's on the dev list if so.

This is a belated response to some discussions in the forums before Javi's September 8 post. I am not diminishing the concerns of those who want to keep their ISY-994i boxes working forever. At this point, because of issues with Java including on the Mac, it is imperative that there be a full alternative to the admin console. Now that UDI is fully committed and has a timetable, I am confident that the eisy-ui wil have every bit of functionality that the admin console had, and probably some additional useful features as well.

You can use IoX to test for connectivity and only reboot the router when connectivity to the portal been lost. I have done this in the past. It will reboot extra when the portal goes down but this is not common.

I don't know, maybe do a factory reset on the PLM and then try restore PLM again. Before that you could do a count of the links in the PLM (from the tools/show PLM links table box) and see how that compares to the complexity of your insteon system. Something seems to be going wrong in the refresh of the PLM. If your IoX/ISY backup is current you could restore from backup again before doing the PLM restore, just to be sure that the scenes are accurately reflected in the IoX links table that would be transferred to the new PLM by the PLM restore. But this is clearly clutching at straws on my part.

I was just saying that the fact that the scenes run from keypads means nothing about the status of the PLM links table. Not suggesting you actually unplug the PLM. You haven't said whether you can turn the scenes on and off from the Admin Console but I assume based on the diagnostic that the answer is no. This means either that the EISY is not communicating with the PLM (the fact that the diagnostic says specific links not found probably means that this is NOT the case. Also the fact that recreating the scene worked suggests that the connection between EISY and PLM is working. ) OR more likely that the PLM does not have the proper links in it to activate the scenes. I would try rerunning the restore PLM procedure following the instructions exactly. Maybe restore the EISY from backup again first. But again others know more than I about all this.

Again my understanding is that scenes will run from keypads with no PLM plugged in. (Unless they need programs on IoX to run properly.). Of course EISY wouldn't know whether they have run or not or have any idea about changes in device status.

I thought your problem was that Alexa wasn't causing scenes to tun -- so now I don't understand what is working and what isn't. The device table compare shows what links are in the devices but not what is in the PLM's link table. It sounds like that is where the problem lies. Under Tools in the Admin Console there is a show PLM links table but I wouldn't know how to analyze what's there. (There's no "compare" button.) Clarification-- there are 3 types of link tables. The IoX keeps a record of the links that are supposed to be in each device and also the links that are supposed to be in the PLM links table. So you did a compare of the IoX "should be" device table with the actual device table, for particular devices. The restore device re-writes the device link table to reflect what's in IoX. I don't think restore device affects what's in the PLM device table (but it might be intended to--I am not an expert).

The scenes still run from the keypads because the keypads have the scene links in them as a controller. So they work without the PLM being in the loop. Presumably ALexa is interacting with the IoX on Eisy, probably via REST, and then the IoX on EISY goes through the PLM to all the devices in the scene to activate the scene. So either the EISY isn't seeing the PLM or the PLM doesn't have the links for the scene responders defined properly. Maybe try following the instructions for restoring the PLM again. When I click on a scene (not right click) the main part of the page has buttons along the bottom including On OFF FastOff and FastOn. That's what I meant by running the scene from the admin console. Scene test does turn the scene on and then off and reports.

Do the scenes run from the admin console or the Eisy-UI? I am not familiar with running scenes from Alexa. There are people usually on the forums who are much more expert than I; perhaps one of these will know what to suggest.

Did you check all the devices that your error log says can't be contacted?

Yes. There is also the "restore devices" command from the File menu that restores all devices but somehow this didn't work entirely for me. You can check afterward by doing the link table compare again. If the links are still not identical the next step is to do a factory reset on the device and do restore device again. On a KPL keypad the factory reset is to push the airgap button at the bottom and hold until it stops beeping.

I'd look at the device tables for the devices in the scenes -- right click and then choose device table under diagnostics. Then use compare button to compare to the iox links table. Use restore device to eliminate discrepancies. Hopefully that will restore communication between devices and PLM and fix the issue. (This assumes you used Restore Modem (PLM) to accomplish the replacement of the PLM--otherwise first follow instructions for that. )

Success!! Exporting and Restoring the Network Resources made them all work. I hadn't noticed these options previously.

Copying each network resource to a new one seems to create a working network resource -- test button works and result is as expected. I only have 25 so if i have to copy them and then reset the names in programs that use them it's not horrible but obviously the wiki was not correct in my case that the network resources would transfer seamlessly and only need opening and saving to make them work.

Also the test button for network resources doesn't seem to do anything.

This was an upgrade from ISY 994i 5.3.4. Communications event viewer shows failure to connect. I did open and re-save all the network resources as advised in the wiki somewhere. I wrote the network resources a long time ago and they were working with tcp. Is there something in the EISY that needs to be switched on to allow the network resources to work?

I never had an all-on event but I did have random individual devices turning on when they shouldn't during the "factory query." I had few/no insteon comms issues and dealt with this problem by disabling the nightly query all. It didn't seem to be doing any good for me.

Thanks to each of you for the very helpful information. I was able to make REST work as before. The time zone was wrong in the custom location. I was able to fix it by reentering the location (editing didn't work). I am still having problems with programs not working but am hopeful I will be able to figure that out.

Thanks! I've run out of time to try today and am reverting to ISY994i. I'll try next week. I still don't understand how to get a username as short as "admin" into the list on IoX on EISY since it told me userid was too short. It seemed to accept adminadmin but I could find no evidence that it stuck. I did not have a port in my old spec so maybe 8080 will do the trick. I'll try without authentication.

I did reboot from the menu (several times). Behavior hasn't changed. The physical unit is in the basement near PLM but I can power it off if you think that could change its behavior (seems unlikely)

http://<ipaddress>:8443/desc gives no response https: gives an XML list but no opportunity to log on

I am concerned that an email address won't work given that the formal for providing username and password in REST has an ampersand before the host.

No, connecting to port 8443 does not give any sort of connection. The eisy doesn't allow "admin" as a userid -- too short. I tried putting in adminadmin as User1 via the file menu in the admin console, trying to put in the URL in the finder (ip adress/desc:8443) as you suggested inists that the userid be an email address. Using the adminadmin as userid in REST did not work