
jkraus
Members-
Posts
839 -
Joined
-
Last visited
Everything posted by jkraus
-
OK, is there a fix, otherwise it appears that I would not be able to use it? Thanks
-
yes, when it is off line it now shows an error in the program that was using it (since it is no longer available)
-
is this what you need? BTW my Temp sensor shows up so I know the NS is working YoLink_6-11-2022_23302_PM.zip
-
well "on-line" for a MS? it showed up on the config portion of your NS, but yesterday it showed up on the AC but not now. attached is log file UDReport.txt
-
OK now 4.1 so that worked, but my Motion sensor is gone, but may be an issue on my side not sure, but was working before
-
Odd, I install ver 4.0 and looks OK for a few seconds then reverts back to ver 3.6. I have uninstalled and reinstalled several times, same issue
-
When I use the insteon motion detection if I use control then it activates my program when it switches on as opposed to a status when it’s on. I’m not an expert in this but The old programs that had it as a control work very well
-
also, where in "configuration" is the temp unit setting, do I need to uninstall and reinstall first?
-
one other issue I am having with the YoLink motion sensor in programs it only shows up for "status" and not "control" so tougher to write programs that use it.
-
BTW both my temp sensor and motion sensor work great!! way toooo cool!!
-
It worked! Thanks...is there a way to change from Celsius to Fahrenheit on the temp sensor? Not a big deal, but happy to have it working, playing with it now!
-
Trying to use the YoLink NS. I installed it (I know its "non-production") but under the github instructions it says Credentials needs to be added to configuration. Goto Settings->Account->Advanced Settings -> User Access Credentials Enter both UAID and SecretKey under configuration - then restart - some times it seems to require 2 restarts to fully get all devices synchronized (I have looked but cannot find pattern" I don't understand where they are referring too, any ideas?
-
yea, in my attempt at debugging I deleted the ISY and re-added it, that may have contributed to the problem, so since tryin a lot of things, I may have obfuscated the real problem I was having
-
yea, that seemed the same for me. I just went back to original and called it a day...but not sure why it would not take the new password.
-
your probably correct, just saying this is what I did. However, it was necessary, and Michel confirmed, that the NS needed to be deleted and reinstalled
-
OK, thought I was clear. I had changed my passwords on the AC login. it seems the PG was "out of sync". I deleted my ISY and reinstalled it with correct password and deleted and reinstalled the NS
-
solved! Michel helped me out (as usual), I had changed my AC password. there were no visible signs it was not connected i,e, the NS showed connected etc., but that seems to be the issue. I also had to un-install the NS and reinstall, so now fixed.
-
yea, restarted and rebooted, nothing. It shows connected on the on the IOP dashboard, looks fine
-
I had been using the KASA NS, worked fine. I added a new device and it would not show up, so I uninstalled and reinstalled a purchased version. It shows up fine in my IOP dashboard, even shows all of the nodes (devices) just fine, but it will not show up as a NS in the Admin Console. I don't think this is specific to the KASA NS seems like I am missing something in general to get a NS to show up in the AC
-
I have been using the KASA NS and works great. Since I installed it I have added a couple new devices by going to the NS and hitting "discover" and it adds them to the AC no problem. Today I added a new dimmable bulb, and it shows up in the PG3 nodes under KASA but not in the AC list of devices. Any thoughts of how to fix this? Much appreciated Joe
-
OK so the pro adds wifi and bluetooth, correct? The wifi, I assume is that so you do not need to be connected via ethernet port, right? what is the use case for the bluetooth?
-
Thanks!