RKinOhio

Interestingly, the system is now working as it should with the only noted change being that the log now shows the correct time. It is no longer in DST. Thank you. Randy

Starting on Sunday, my eisy programs stopped controlling my KASA devices. Working through the admin console, the devices are not accurately showing their current status on all devices and none of them are responding to commands from the console although the KASA controller shows that it is connected and which devices are connected. I have seen a condition in which the KASA controller becomes disconnected (not certain as to why but we have lost power on occasion), but everything would be restore after going to Polyglot, shutting down the KASA plugin, and starting it again. I don't see any sign of errors or warnings in the log files. When I send a command to a KASA device near my desk from the console the 'DON' and 'DOF' followed by "node address ********3e34 does not exist." and I have noticed that the plugin clock is still running on DST while the admin console time is correct. After looking for other topics similar to this issue, I have tried unplugging and re-plugging the devices, restarting the plugin, and rebooting the eisy. All of the packages are up-to-date. I haven't made any changes in months to my programs, devices or network. Any ideas as to what may be going on? Thanks, Randy

No, I didn't, but when I just went in to edit the current IoX configurations, I noticed that the address is set for the 127.0.0.1 and the HTTP/S was set for HTTPS. I selected the HTTP and within a few seconds I was connected on both the admin console and the P3x. That worked. Thanks for the suggestion to look. I wouldn't have thought of it without your prompting to look. Thank you! I think that I am good now.

Everything had been running smoothly until I went to add a pair of KASA modules. I noticed the packages needed updating so I did the update and two reboots, re-installed the node server(s) on the Polyglot (System - Reinstall) and noticed that the IoX was shown as disconnected now on Polyglot 3. The nodeserver was not online on the admin console. Re-booted a couple of times, powered it down twice, repeated the initial steps and I still don't have a connection. Also, is it normal for the IoX Launcher to locate the ISY and still have the Finder say "Not Found"? Helpful insight would be appreciated. Thanks!

Just saw your note. I was getting ready to send you an update. I took a tip from Techman (Michael?) and powered the eisy off, then restarted. I am now running 5.6.2. Thanks to you both! RK

Thanks, Dennis. I tried the update and I am still at 5.6.0. Any other thoughts? Randy

That sounds like a good suggestion. Thank you.

For some reason, I have not been able to get the 'update packages' to update anything. I have tried repeatedly with both the reboot button and the power pulled. I am tempted to restore an earlier configuration and see if that will allow me to update. Do you have an other suggestions?

No. This is my first and only so far. Thanks.

As I started working with the Polyglot this afternoon, I noticed that my KASA node server was showing the IoX as disconnected. I have tried logging off and on, rebooting the eisy, rebooting the eisy with the power cord and numerous other groupings, but it is still not connected. Am I missing something else for my bag of tricks and tips? Thanks, RK

I pulled the power and verified that I am 5.6 on both the UI and the eisy. I can now get into the Polyglot! Thank you for your help. I will add that to my bag of tricks. RK

Yes, I have access to the devices and programs. The programs are running as expected. I rebooted the eisy and there was no change in the Polyglot login. Press the button and nothing happens. After reboot I confirmed that the devices are working normally, except for the KASA devices. I can turn bulbs on and off, but the information in the administrative console is empty. I truly appreciate the help and ideas. RK

I need some new ideas. My old ones haven't worked. I replaced my router with a eero mesh system. My eisy has an IP reservation and I have no problems launching into it. I can access the ISY portal without issues. When I try to go into the Polyglot v3 from either the launcher or from the Administrative Console, the logon screen comes up, I enter my credentials, press the login button and nothing happens. I have tried the Incognito mode on Chrome and tried using Microsoft Edge without luck. Given that when I was using my old router there were no problems, I am wondering what is different with the eero router. Maybe the router isn't the problem. I am open to anything. I am probably just overlooked something. Any suggestions? Thanks. RK

Same sensor, but a different question. I have a 2844-222 running through the ISY at v4.6.2. A program reacts to the motion 'on' signal to control a light between dusk and dawn; the program sets the on time. What I don't know is if the 2844-222 will send a 'low bat' signal that the ISY can read. If it does, I can send a text message indicating that it is time to change the battery. Has anyone worked with the 2844-222, ISY at 4.6.2 and the 'low bat' signal? What did you find? Thanks, RK

Thank you.

Thanks, Teken. The sensor worked fine with the micro USB. The replacement battery that I used was supposed to be a 3.7V replacement for the 123 battery, but the fully charged voltage of my new 16340 battery is 4.2V, not 3.7V. The recommendation I went with, from someone that used a this rechargeable 16340 in place of a 123 on another product, was not a good battery for this application. I just put in a new 123 and all is well again. Puzzle solved. I appreciate the help. Do you know of a suitable, rechargeable replacement for the 123? Thanks, RK

I reset the devices, deleted the sensor, completed the factory reset and reinstalled the sensor. It now signals the ISY when it sees motion, but it enters a loop in which it goes off after about 38 seconds and then comes back on 1 second later, and repeats. I have the sensor sitting inside a closed desk drawer and it is not seeing any motion. I left it there and checked back about 2 hours later and it was not cycling. I woke it up and we are back to cycling. Any ideas? Thanks, RK

Done. Restarted the ISY and reloaded the console. At first the sensor's status was blank. So was the sensor's dusk.dawn status, but the low bat status showed off. Motion did not change the status of the sensor. One press of the set button put the status to on. Another press took it to off. Thanks for the help, by the way. RK

Here's the puzzle... I bought and set up an Insteon 2844-222 on my ISY994i with Z-Wave. I used a manual install with the older 2842-222 configuration and it worked fine. I could not control any of the sensor's settings from the ISY, but using the sensor status as an input I wrote a program to control an outside light from dusk to dawn with the program controlling the time out which works fine for me. Didn't use an Insteon Hub. The set up wasn't much of an issue and the ISY would show motion from the sensor when motion was present on the console properly. The sensor is battery powered and as you would expect, the battery died. I replaced the battery and now it wouldn't signal the ISY when there is motion. If, however, I press the sensor's 'set' button once, the ISY console reports motion 'on' at the sensor; press again and it reports 'off' at the sensor. When 'on', it won't time out; it just stays 'on' and the same with 'off'. Obviously, the sensor is able to talk to the ISY now, but regardless of the state that I set the status using the set button, it is not communicating motion to the ISY. The sensor's green LED is indicating motion as it did before but the ISY isn't getting the message. This happens regardless of whether I have pressed the set button to turn the ISY sensor status 'on' or 'off' manually. I have uninstalled the sensor from the ISY and then re-installed it without any impact to its operation. I am thinking about doing a factory reset on the sensor, but since it worked before I am a little hesitant. Before I do that, does anyone have suggestions to try out? I have to be missing something here. Thanks in advance! RK

I just picked up a Google Home and I added a scene to the Google Home spoken device list on the Portal. I opened up the Google Home app, added the scene and everything worked. Then I tried adding a couple of more scenes, but the app just shows in Linked services, Universal Devices 1 device. There doesn't appear to be a way to add more. My work around was to unlink and this re-link. Has anyone found a better way to add them? I also wanted to agree with Steve9f. The UD folks are rocking and have made things simpler in my life. Thanks, RK