hart2hart

I don’t know if anything was cleared. I followed instructions to migrate items from old ISY and Polisy to the new eISY. Most of what I can see is good. What do you mean by does it show at top after pressing? Pressing what? Selecting which system and synchronizing it where? I’m really lost. Sorry.

It says it can’t get UUID. It’s visible at top of that same form. Also, the search icon next to the remote URL button finds it but it does not help. Does it need to be on the network?

Thanks. I got interrupted during migration from pg3 to PG3x including the portal migration. Im 99.99% I did something wrong or out of order. I had to reinstall all nodeservers in their same slot and enter various parameters. They all worked except for this one. It was odd how you config it and I can’t recall even the basics. I’m fine to recreate the 5 virtual switches but I don’t remember how it works and can’t find an example. I usually put this stuff in a document for future reference. But not for this or I can’t find it. Looking at its config screen again, there appears to be a missing section at the bottom. There is a header and then save button but no add another parameter button for that section.

I reinstalled Virtual nodeserver and the nodeserver did not retain the config including nodes and config. The 5 virtual switch devices I created still exist in the admin console, but they are not listed in the nodeserver custom configuration parameters or as nodes. I'm thinking I need to add them back on the nodeserver side. Is that correct and is there a way to keep what is in admin console and nodeserver synchronized?

@Javi I’ve been using UD Mobile and it is fantastic program with excellent support. I just migrated from ISY994 to eISY and would like to move favorites if possible in UD Mobile. Is it possible or should I just recreate them. Good either way!

Nevermind. Found where to renew in Purchases -- image that. LOL

The steps are very simple, but I have one clarifying question. Does the zwave back referenced in the 5.3.4 release notes need to be Normal or Full or does it make any differnce? Also, I am upgrading from 5.0.16C and not a 4.x.x version but do not think that is an issue. Z-Wave migration from 4.x.x branch All Z-Wave nodes will be recreated when migrating from 4.x.x. Some nodes will have different addresses, and some devices will have a different set of nodes. In some cases, it is easier to rebuild your network rather than migrate. 1. Before moving to 5.3.0, in 4.x.x, Backup your Z-Wave Dongle and then Backup your ISY. 2. Replace the 300 Series Z-Wave board in your ISY with a 500 Series Board 3. Install 5.3.4 EDIT: I did Full backup and upgraded to 5.3.4. Zwave appears good so far. This is just stair on way to EISY tomorrow or Friday! Even a couple of Schlage ZW 300 series of deadbolts are still working without any intervention and programs were fine. I've got to do something with two zwave nodes that were added to my lighting. I'll do search and then a separate post if I can't locate what to do with them.

Thanks.

I located the excellent wiki and read those steps. The item that was not clear was how would the ISY service on Eisy know the new IP address of the PG3x nodeservers. UD always does excellent planning and execution but I want to understand process so I can recover or take right steps if any issues occur.

I’m planning to move from isy994 to eisy later this week and feel good about all instructions to get it done. @bpwwer I plan to move from PG3 on a Polisy to PG3x on the same eisy above. How do you make this migration including pointing to nodeservers at their new location?

Thanks. I have a 500 series board. While researching other forum posts and install instructions for ISY FW yesterday, my draft plan is to upgrade to 500 as a step in the process of moving to 5.3.4.

I'm taking steps to migrate from my trusty ISY (5.0.16C) and POLISY (PG3 current version) to eisy. As first step, I want to get blank eisy set up properly. I had UD Mobile installed when I plugged it in (ethernet cable first and then power) but UD mobile did not take me through the setup. IoX already installed so I connected to eisy via it and set time zone then did upgrade packages -- now at 5.6.0. Kind of glimpsing that UD Mobile may only guide one through setup if eisy is connected via Wi-Fi -- correct? Between update TPM and upgrade bios, do I need to perform either. I recall setting up TPM when I installed the POLISY. Do I need to do that for eisy? Do not remember reading anything on an updated bios but want to confirm. I'll be upgrading from ISY with 5.0.16C and 300 series z-wave board (two Schlage 300 deadbolts are only significant z-wave devices -- rest are just to get enough of a mesh to support them and mesh is nearly 100% effective). Moving from PG3 on POLISY (9 nodeservers) to PG3x on eisy. I'm also running isylink. Therefore, I've been looking at some of the step-by-step guides. Please let me know if you've used one of them and how it went or how you would update it. Thanks and looking forward to the holy grail of eisy in coming week or two! Paul

Does it run PG3 and PG3X?

As stated by others, we need more but… Program A can have an If for the time and be disabled. B could run the If of A.

I feel like I’m missing something subtle but.. Have program B execute program A

Very welcome and thank you for incredible support.

I just upgraded to 1.0.11 and as usual checked log after upgrade. The following was in the in log and as you see said report this: 2023-04-11 12:09:06 error: NS: uncaughtException REPORT THIS!: ReferenceError: use_mosquittio is not defined at MqttClient.<anonymous> (/var/polyglot/pg3/ns/0021b900f1fd_8/node_modules/polyinterface-v3/lib/Interface.js:261:7) at MqttClient.emit (node:events:525:35) at TLSSocket.f (/var/polyglot/pg3/ns/0021b900f1fd_8/node_modules/once/once.js:25:25) at TLSSocket.onerror (/var/polyglot/pg3/ns/0021b900f1fd_8/node_modules/end-of-stream/index.js:44:12) at TLSSocket.emit (node:events:525:35) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Me too!

Hi Bob. The letter to button map follows: A - Open B - Favorite C - Close D - Up E - Down Thanks for your help. I've got everything working well!

As always, you're correct. When I selected Control the 5 devices were available with switched On as the option. Shade Remote-A appeared to have been to close them. I could see it triggered in the program summary and the True time was registered in the program summary. Like you thought it did not know which or all shades were controlled. Just that Close had been pressed last. I don't anticipate using this feature, but time will tell -- glad it is an option. I talked with Lutron Tech Support about the App representation of the Shaded Remote and it is in the cloud. I changed which shades were controlled by the 1,2,3,4 buttons and it changed both in the app and when the physical remote button was pressed. He said he thought this would have been more "hard-wired" if I hadn't added the remote to the App. In fact, my physical programming of the remote to shade connection had been "lost" at some point since the Saturday install and all physical remote buttons were controlling all shades, so I fixed it without pulling ladder out to do button presses on the shades in second story windows!

Thanks Bob, understood. I selected the remote in the Luron app and the virtual Open and Close buttons on the screen raised and lowered the shades. It appears that the app does emulate the button presses on the physical remote. I pressed the close button on the physical remote and following was in Caseta NS log when set at debug level. Created a program to trigger on any of the NS Remote -A to -F nodes but they were not available as a trigger item. 2023-04-03 12:25:30,527 Thread-2 udi_interface DEBUG remote:btn_on_callback: Button on was Press 2023-04-03 12:25:30,528 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'command': [{'address': 'device2_3', 'cmd': 'DON'}]} 2023-04-03 12:25:30,547 Thread-2 udi_interface DEBUG remote:btn_on_callback: Button on was Release 2023-04-03 12:25:30,691 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-04-03 12:25:30,693 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-04-03 12:25:30,701 Thread-2 udi_interface.node DEBUG node:setDriver: device4:Great Room:Left Shade Reporting set ST to 100 to Polyglot 2023-04-03 12:25:30,703 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 100 2023-04-03 12:25:30,703 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device4', 'driver': 'ST', 'value': '100', 'uom': 79}]} 2023-04-03 12:25:30,705 Thread-2 udi_interface.node DEBUG node:setDriver: device4:Great Room:Left Shade Reporting set OL to 0 to Polyglot 2023-04-03 12:25:30,706 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-04-03 12:25:30,707 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device4', 'driver': 'OL', 'value': '0', 'uom': 51}]} 2023-04-03 12:25:30,728 Thread-2 udi_interface.node DEBUG node:setDriver: device5:Great Room:Right Shade Reporting set ST to 100 to Polyglot 2023-04-03 12:25:30,730 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 100 2023-04-03 12:25:30,730 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device5', 'driver': 'ST', 'value': '100', 'uom': 79}]} 2023-04-03 12:25:30,732 Thread-2 udi_interface.node DEBUG node:setDriver: device5:Great Room:Right Shade Reporting set OL to 0 to Polyglot 2023-04-03 12:25:30,733 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-04-03 12:25:30,734 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device5', 'driver': 'OL', 'value': '0', 'uom': 51}]} 2023-04-03 12:25:30,753 Thread-2 udi_interface.node DEBUG node:setDriver: device6:Great Room:Middle Shade Reporting set ST to 100 to Polyglot 2023-04-03 12:25:30,755 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 100 2023-04-03 12:25:30,755 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device6', 'driver': 'ST', 'value': '100', 'uom': 79}]} 2023-04-03 12:25:30,757 Thread-2 udi_interface.node DEBUG node:setDriver: device6:Great Room:Middle Shade Reporting set OL to 0 to Polyglot 2023-04-03 12:25:30,758 Thread-2 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-04-03 12:25:30,759 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'device6', 'driver': 'OL', 'value': '0', 'uom': 51}]} 2023-04-03 12:25:30,942 MQTT udi_interface.interface INFO interface:_message: Successfully set device4 :: ST to 100 UOM 79 2023-04-03 12:25:31,262 MQTT udi_interface.interface INFO interface:_message: Successfully set device5 :: ST to 100 UOM 79 2023-04-03 12:25:31,301 MQTT udi_interface.interface INFO interface:_message: Successfully set device4 :: OL to 0 UOM 51 2023-04-03 12:25:31,400 MQTT udi_interface.interface INFO interface:_message: Successfully set device5 :: OL to 0 UOM 51 2023-04-03 12:25:31,651 MQTT udi_interface.interface INFO interface:_message: Successfully set device6 :: OL to 0 UOM 51 2023-04-03 12:25:31,694 MQTT udi_interface.interface INFO interface:_message: Successfully set device6 :: ST to 100 UOM 79 2023-04-03 12:25:39,574 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-04-03 12:25:39,576 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

Thanks. Remote is https://assets.lutron.com/a/documents/085314.pdf Where would I look in logs to find information on remote you referenced? I just looked at remote again and I’d guess the 5 nodes might be groups 1,2,3,4, & All but without the additional action control buttons.

Not sure why I asked as I just bought it... I knew I wanted it and that you would guide me through whatever I couldn't figure out. On to that LOL... I've got a 4 shade remote (has 10 buttons) and it shows up from nodeserver with 5 nodes named "Shade Remote - A" through "Shade Remote - F". Do you know how this might logically map to the physical remote. I was kind of expecting each of the 10 buttons on the remote show as a node for a total of 10 nodes. For example, my working plan was to press the "All Button" and then press the "Close or Open Button" via activating the represented node to open all or close all shades which I like because it mapped to the same logic as my old shades. I could go into more detail on why that's my desire but just know it would take advantage of logic already in place to open and close from my IR remote. Next step... As expected, my 3 shades each show as a node. Using the command mode in a scene supports open and close for each shade and can do the same from a program. As a workaround to above... To Open and Close all 3 shades at the same time, I'm guessing that an All Shades Open scene and an All Shades Closed scene (with all 3 shades included with right command state set) are equivalent to a program(s) that runs the open or close method on each shade in sequential order. Is that correct? What are good values for short and long poll?

@bpwwer I installed 3 honeycomb shades today and as you described I have great control using Lutron’s 4 shade remote and the Lutron app with the Caseta Bridge. If I install the trial nodeserver, is it simple process moving to purchased app when I confirm desire to add ISY/Eisy control?

@Goose66I realized that PLM was not registering the insteon device update so I did a restore PLM and all is working now -- sorry to have bothered you with it. Of course the PLM may need a replacement soon. I'll watch it. I prophylactically replaced the capacitators a couple years ago.