Jump to content

TKopke

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TKopke's Achievements

Newbie

Newbie (1/6)

3

Reputation

  1. You can remove Guard completely but only from the desktop Alexa account access. Go to Smart Home, Devices. Guard is the device called something like RedRock. Remove it and Guard is gone.
  2. I'll go back and revert the .json file to the original.
  3. Nodelink.cmd returned errors until I moved them to the system32 directory. It could have been something else in how I was trying to execute the cmd but, I didn't have the patience to go back and figure it out after I got it running. Forgot to mention that I edited the .json file to reflect the version of net core installed. Don't know if that matters but did just in case. Updated my previous post to reflect this.
  4. Got it running! It took several attempts of trial and error not being familiar with the world of Windows. However, I've provided the below to help others like me (Windows 10, 64bit)... * Installed Net Core on Windows complete with SDK * Moved the .dll and .json files to the Windows/System32 directory * Ran Nodelink.cmd (required Administrative privileges) * Looked for the ip address from the output including the port number and entered it into a browser. * Bingo! The Nodelink console appears!
  5. Ahhhhhh! Nope, I'll do it now. I guess I need to RTFM a little more closely next time.
  6. Downloaded the zip file, extracted the contents. I then tried running the cmd file and got a system warning, allowed the file to run. Nothing happened after that. What am I doing wrong and what's supposed to happen next?
  7. Hmmm, right-click delete works... if using a real mouse. I was using the Microsoft onscreen keyboard whereas there is a key that is "supposed" to act as a right-click (Operating my PC from my phone via Remote Desktop.) For whatever reason, it didn't in this case. When was able to physically be at my PC, I used the physical mouse, it worked as expected.
  8. Uploading files to the ISY web server is easy. How does one delete files? Delete key and right mouse button doesn't do anything.
  9. Thanks, a few minor edits and the page worked. Edits to where support files (css, images, etc.) were located were all that were needed. Now, I can tune the page to meet my needs. Thanks!
  10. Sorry for not being clear. I opted to revert to the 6-button mode and all is working now as expected. I can't believe how difficult I made this out to be! I originally went to 8-button because of an erroneous understanding of how the KPL worked with regards to the LEDs. It was the non-toggle-OFF that caused what I had not to work - the OFF button LEDs would never illuminate. With a button in non-toggle-OFF mode, I wondered if the button LED could be configured to illuminate suggesting the button was "on." I now know it can't or, at least, not easily. I had it working in 6-b mode when I had the Insteon Hub but when my second one began to fail, I got an ISY primarily because of the ability to make backups. I did some things on the hub not really understanding how they worked. I'm barely a month with the ISY along with integration with the Echo and already understand more than I ever did using the hub. The hard stuff is easy. It's the simple stuff that gets me everytime. Again, thanks for your help.
  11. My understanding is that a custom interface can be written and used instead of using udajax.htm. My question is where to upload since it appears that the only directories available are xxx.xx.xx.xx/user/web/... Is this were the files go (assuming all my page links go the correct directories?) Is there something I'm missing?
  12. Thanks for everyone's help! I suspected the "non-toggle" part. So, my understanding now is that one can manipulate the LEDs for a non-toggle-ON (as done in the Garagelinc wiki instructions) but one cannot manipulate the LEDs for non-toggle-OFF. For the OFF, it's akin to trying to operate a plug-in when it has been unplugged. I went to 8-buttons because of a thread I read elsewhere here. If I understand the 6-button KPL correctly, it's listed as 5 buttons in ISY with first node being to control off/on of my plugin and, internally to the KPL, operation is split between the two buttons. I'm assuming that the LEDs will work as expected. Hopefully, I'm understanding all of this. I feel much better using ISY than the HUB only being in it for less than a month. The HUB could be confusing and overly restrictive at times. The learning curve for the ISY wasn't as steep as it initially appeared and it really makes it easy to see relationships. I just getting impatient since I want to explore so many of the other capabilities!
  13. I have a 6-button Keypadlinc in a tabletop enclosure. It is not connected to a load. In order to be able to use it as a 6-botton controller for a non-load device, I converted it to an 8-button controller but with the 6-button overlay. I am able to turn off/on the responder (a plug-in module) as expected. What I need help with is lighting the "On" (A and B buttons when only on and the "Off" (G and H) when only off. What am I doing wrong? Switch ON, non-toggle ON Switch OFF, non-toggle OFF
  14. According to the documentation, to have Switchlincs to act as a multi-way switch, one only needs to create a scene with the the required Switchlincs all configured as controllers. Sure, it works but, I don't understand why without needing responders. Can someone explain how this works so that I can better integrate various devices.
  15. Yep, that's the answer. A bit of a pain to initially set up but, it does exactly what I want. Thanks for your help!
×
×
  • Create New...