Illusion

Thanks guys. I am not sure what the 'Refresh' button does, and pressing it did bad things in my case. I got to a point where it where it seemed like it would not stop propagating. I eventually pulled the power to the eisy. I am not on the latest beta. It has always been tough for me to get a clean link read because it is trying to get a quiet insteon environment long enough to read 850 links, but in the eisy-ui it was down right brutal. I am going to assume my PLM restore worked fine until I find something in the house not working right. I will revisit this after a few more eisy-ui updates.

I am doing some extensive work with restoring a PLM and I am a good bit confused by the eisy-ui PLM Links Table display. When I ask to see/count the PLM links, there is a button on the bottom that says 'Stop'. But clicking it does not seem to stop the process, but it does bring up a current link count (which continues to grow sometimes and other times it does seem to stop) and an 'Refresh' button. What does these 'Stop' and 'Refresh' buttons do? I clearly am doing something wrong because get get back either really low link counts like 170 or stupid high counts like 1764. I should be right around 850, so 170 is wrong and 1764 is more than possible in a PLM. I am thoroughly confused.

Okay, my solution is in place and seems to be working flawlessly. All I did in the end was buy an adapter cable, pictured below, and connect that to my APC DC UPS barrel connector. This USB C connector is then connected to the power input port on the eisy, not the full function port. I did buy a USB C meter with PD triggering and did lots of testing before connecting my new eisy R2 to the power. It seems to me that the warning about using any other power supply with the eisy R2 is a bit backward. It is the included power supply that should never be connected to anything else. It spits out 12V all the time and ignores all PD protocols. It will have a good chance to wreck anything else you plug it into. But this version of eisy does seem like it could take a PD compliant power supply through either USB C port, but I am not going to be the one to mess with that as my solution works for application very well. Thank you all for your advice and direction.

I personally would recommend against removing them from IoX. At least at first. Personally, I would stop all IoX programs. I have a program to do that, but if you do not unplugging the PLM would work quick as well. Then turn your switches on and off and stuff. If problem is gone, it is an IoX program. If problem is not gone, do not remove them from IoX. T (Too much unnecessary work and you loose lots of fun troubleshooting options). Next I would compare device links. Alt click on one of the switches in Admin Console>Diagnostics>Show Device Links Table. Window pops up and IoX queries the link table stored in switch. When done, click on compare. If everything is not identical, that is probably your issue. Restore devices in the alt click menu of the device. If all that does not work, then I would factory reset the devices and see if the problem still persist. If it happens after factory reset you have bigger issues. And yes, you can absolutely program Insteon switches locally. I had an entire Insteon system that was completely locally programmed at the devices pre-ISY. It was horrible.

Further research seems to support that the 12V input port is a hybrid port. While it does not support data xfer, it appears to support the PD protocol. My research says that PD negotiation with this port is optional. It can accept 12-18V without negotiation which is what the included adapter is. The full function port appears to require negotiation as it is expecting 0V before PD negotiation and may be damaged by connecting a dumb 12V supply that is always on. It seems that they did this specifically so that you could power this small computer from a battery or power bank that has no PD ability, as long as it was 12V. Also the range of 12-18V seems to be because lots (maybe even most) USB C power supplies do not support the 12V profile. The 12V profile that was part of PD 1.0 was not included as a mandatory voltage in USB PD 2.0 & 3.0, so now most power supplies jump from 9V directly to 15V skipping 12V altogether. But this learning I have done makes me wonder if the warning label UD put on the device is a leftover from eisy that just came over to eisy R2? It sure does seem like you could power this device from a USB C Power Delivery compliant supply that supports 15V which would be any that advertise as 27W or greater capacity.

This is actually really great info. Yeah the power supply could really mess up another USB C device, but looking at the exact computer on Amazon: https://a.co/d/h0XQsML It looks like the OTHER USB C port is fully PD compliant and can be used as a power input! So for sure I feel like I could use a PD compliant UPS like https://myliontech.com/en/product/mylion-muc66-mini-ups-type-c-pd-65w-in-out-lithium-battery-pack-backup-uninterruptible-power-supply-for-wifi-router/ and plug it into the second USB C port. This is really a great link too. Thanks Brian. Based on this I am first going to try an adapter cable going from barrel to USB C. I am also going to buy a USB C meter/tester and play with that before connecting to my eisy.

Well, ideally for me would be if I could continue to use my APC DC backup. It outputs a regulated 12V up to 3.5 amps on a standard DC barrel connector. This plugged directly into the Polisy. It should be able to power the eisy for like 12 hours or more. So do you think a simple adapter like: https://a.co/d/3PLKt9u Would work? I know 12v is 12v, but my big concern is polarity and the USB C pin out. I would assume this is very common and manufacturers (including Universal Devices) would use the same pins for power, but I also would not have assumed that UD would have a USB C port that does not negotiate using the PD USB standard or at least have a way of protecting the eisy from damage. USB C power supplies are so common I was surprised to see a damage warning on the device with the public having access to such a variety of power supplies that terminate to USB C. So I am just a little scared. Regarding device sync. Yeah, I have a delayed activation relay connected to an I/O linc. 2 minutes after power is restored and stable the I/O linc closes, the ISY sees this and notifies me and does a query all.

Just set up my new eisy R2. I am coming from Polisy so the power supply form factor is different. The eisy uses a USB C 12V port. But the top of my new eisy R2 had a sticker that said to only use the factory supplied power supply as it will be damaged by anything else. What is special/unique about the eisy USB C power input? I thought USB C was generally supposed to be kinda universal and sorta protected? What is special/unique about the UD supplied power supply? The reason I ask is because I have some extensive programing that relies on countdown timers. (long ones) I am coming from the ISY 26 to the 99i to the 994 to the Polisy. With each iteration I have had to implement a new UPS solution to keep my ISY live across blackouts. Each time I have looked at alternate ways of achieving my objectives that are met by my long timers and never been happy with them. I have built further systems and protocols that rely on my ISY always being on. Before I begin looking for how I am going to accomplish a UPS for the eisy R2 I wanted to make sure I would not damage my eisy. I know I could just get a normal UPS and plug the UD 12v power supply into it, but I have always preferred a direct DC UPS. The Polisy ran on a APC UPS Back-UPS Connect CP12142LI : The advantage to this is the device is further separated from the power line, there is no transfer time, and most importantly, without inverting DC battery energy to 120V 60hz AC only to convert it back to DC I realize vastly longer run times for the same size back up battery. Actually, the DC UPSs usually end up being less than half the size of a normal standby UPS. I feel pretty confident that I can find a suitable USB C 12V device that will function as a UPS, but the sticker makes me worried about damaging my eisy.

I have a Denon AVR-X2200W. I installed AVRemote and added the Denon in the "Custom Typed Configuration Parameters" section. I put the static ip address of the AVR in as the host name. In the Admin Console it shows "Denon AVR Online" as 'True'. The volume, power, and mute statuses seem to be right and updating. But the input always sits at 'tv_sat' and the unit does not respond to input changes in the Admin Console. I have tried changing 'Connect on demand' from the default 'false' to 'true' with no noticeable change. What does this parameter do? If the volume, power and mute status is correct, I am at a loss as to how to get the input to show the correct status and unfortunately that is the main data point I wanted to use. Any suggestions would be appreciated.

Polisy. IoX version 6.0.0

1.4.3

If my UD Mobile app is using a remote connection, the home screen at the top will say "Disconnected, will reattempt connection" It will show an attempt counter eventually just landing at the disconnected message. But it appears to be connected. If I go into controller settings is reports as 'Online' with Synchronize working fine. Devices show correct status once I focus on them, but do not auto update which is the behavior I have come to expect when on a remote connection vs the auto status updates I see when local. It does not matter what device I use, and it does not matter wether that remote connection is cellular or wifi. Running v1.4.3

It took me 4 tries to reinstall and get it working again. But then no configuration work or anything. Poof all working again! Thanks for this thread!!

Upgrade of OS to 14.1 and IoX to 5.9.1 has corrected the issue. I guess we never get to know what was going on. I am going on the theory that it was something in IoX 5.8.4 as my update to that firmware coincides pretty closely with the start of the issue. Why no one else had the issue, and why we could not figure out what mechanism was the cause will remain a mystery.

Upgrade to wired Polisy went well. Only notes are I did not get the 4 beeps at the end. Did get beeps throughout. Took about 20m PG3x and system no longer show up at https://polisy.local:8443/WEB/sysconfig.txt) and https://polisy.local:3000 I have to use the IP address.