GPG

Had to submit ticket to resolve. Issue fixed.

@DennisC My above response was to @Techman. I have powered down polisy, PLM, Router, and PC previously. I used http://MY IP:8080/desc to add my polisy to the launcher. That's when I noticed that my uuid had changed. I have never see that happen before. I also get the same uuid returned if I use https://MY IP:8443/desc. I'll take a fresh look at this in the morning.

I had already done that, but I just did it again and I still have the same problem.

After upgrading to 5.6.0 my polisy was no longer listed in the ioX launcher. Using my IP address I was able to get to the Admin Console, but I am unable to make changes or control any devices. In addition my uuid changed. I also lost portal operation. I added the new uuid to the portal and received a message to go to the AC and approve the access request. I logged into the AC Configuration/Portal and I see 5 requested services listed (my name is on the top one). When I click on the +Approve button, I receive the message "Bad Request". Has anyone else had this issue and solved it, or is it time to submit a ticket?

Hi @kewashiThis is great news. Thank you very much.

Is there any information on whether a PG3 node server will be available for Hubitat.

I am having this same problem. I first noticed it yesterday. This morning I was able to use a voice command to turn on some lights, but now it is not working again. All my devices are showing up in the Alexa app. I have rebooted all devices: cable modem, router, echos etc. I am now getting the verbal error message from Alexa that the "device is not responding", but after a few minutes it device turns on. This happened earlier today also, but the delay was more like 20 minutes. I am thinking this may be a problem with the Alexa server.

Finally it is working. I'm not sure why the logs were not showing up. I went back to the initial NodeLink setup and started from scratch. The log then showed up, which helped a lot. I'm sure part of the problem was me being new to the raspberry pi. Thanks much for your help. Looking forward to setting up my sprinkler programs now.

Are the log files supposed to appear in the node folder?

Options are: Emergency, Alert, Critical, Error, Warning, Notice, Information and Debug

Which nodelink log level should I set? Is a restart from within nodelink sufficient?

There is no plus in front of RainMachine. I did reboot the ISY. No change.

@Whitehambone No I am not. @io_guy RainMachine Irrigation Controller now shows as an installed device and RainMachine now shows up in the ISY. However, there are no zones showing up. Something I missed?

Thanks for checking into this. Definitely something with how the download portion of the script ran. I repeated it several times, all with the same result. I ended up downloading NodeLink.exe directly from automationshack.com an put it in the raspi node folder. I was then able to setup the isylink node server in the isy. I am now at the point of adding the isylink nodes for the RainMachine. Is there any documentation for adding the the 3 RainMachine nodes.

I ran the install again and took this from the terminal. pi@raspberrypi:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash ### Installing dirmngr and updating to offical mono repo dirmngr is already the newest version (2.1.18-8~deb9u4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Executing: /tmp/apt-key-gpghome.hwRmb9J9Lc/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF gpg: key A6A19B38D3D831EF: 2 signatures not checked due to missing keys gpg: key A6A19B38D3D831EF: "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 deb http://download.mono-project.com/repo/debian raspbianstretch main ### Updating System - this may take several minutes All packages are up to date. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Installing mono and relevant dependencies - this may take several minutes libmono-system-net-http-formatting4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http-webrequest4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). mono-vbnc is already the newest version (4.7-0xamarin1+raspbian9b1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Creating directory ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink ### Install complete. Login to NodeLink at http://192.168.1.252:8090 pi@raspberrypi:~ $ Cannot open assembly '/home/pi/node/NodeLink.exe': File does not contain a valid CIL image.

That's what I am trying to do - install it on a Raspberry pi.

Debian 9 on raspberry Pi 3 B+

I am having a problem installing NodeLink. OS is ver 9. Used the following command via putty. sudo curl -sSL http://automationshack.com/Files/install.sh | bash At the end of the installation the console shows the following 3 lines: ### Starting NodeLink ### Install complete. Login to NodeLink at http://192.168.1.252:8090 Cannot open assembly 'home/pi/node/NodeLink.exe' File does not contain a valid CIL image. Does anyone have any suggestions as to how I can start to track down this problem?

I upgraded from 4.6.2 to 5.0.13A. I currently have about 40 Insteon devices (Wall Switches, Plug-ins, Motion Sensors, Tstats and KPL’s). All came over without a problem. The Z-Wave dongle also installed without a problem. So far I have installed the following Z-Wave Plus units: Aerotec Smart Switch 6, Aerotec MultiSensor 6, GE Plug-In Dimmer and a HomeSeer WD-200 Wall Dimmer. I am entirely new to Z-Wave so I am going through a bit of a learning curve. For example, I finally figured out I had to add both the dimmer switch and the dimming control to the scenes in order to get different dimming levels on the WD-200 switch. The results thus far are very positive. Reception is better than I expected.

Hi Michel, Like ronbo, I am also missing scenes. I use two major folders and then sub-folders for my scenes, with the exception of one scene which is not in any folder. I have quickly looked at my rest/nodes output and I see a pattern where if group flag = 4 they are missing, and those with a group flag = 132 show up.

Michel, My Echo is on back order and I can't wait for it to arrive. I just wanted to say how gratifying it is to see the enthusiasm and dedication you and the UDI staff have demonstrated over the years to make the ISY product line so great. Thanks for outstanding support, George

Hi Michel, My rain reporting has also often been missing. I am glad to hear some improvement may be forthcoming. Is there any estimate for when the transition will be completed? Edit: Sorry I posted before I saw your reply. Thanks, George

Ok, Now I am showing UI as v4.0.5 Everything seems to be working fine. Many thanks, for your help.

Insteon_UD994 v.3.3.3 (2012-10-03-15:23.54)

LeeG, I am also having the same problem with a newly purchased 2334-222. My ISY is a 994/IR Pro at v.4.0.5 After my first attempt to link the KPL, following your suggestions I : Deleted the unit Made a Backup Factory Reset the KPL Unplugged the ISY and PLM After 30 sec, plugged the ISY and PLM back in Tried to link the KPL again, with auto detect The KPL shows up with all 8 nodes, but the type is "Unsupported Device 1.65" If I attempt to add a button to a scene, it will only add as a responder (no choice is provided).