kzboray

I wasn't clear, that was my fault. You can only use ONE IP address at a time to access the Elk, however you can run multiple sessions via it's non-secure PORT. Ports and IP address are very different in terms of how they can be accessed. If you want more information on this do a search for "OSI model." TCP/IP communications is handled at layer 3, while ports are handled by layer's 4 & 5. Each layer relays on the layers before it. So you can have only one IP address at layer 3, but on top of that you can stack all kinds of ports that access via that one IP address. There are 1024 "Well Known Ports" i.e. port 25 (POP), port 80 (HTTP) etc. These are off limits for devices for obvious reasons, but ports above 1024 are available. Some of these have been defined by manufactures for their equipment as in the case of Elk with their use of ports 2101 and 2601. Don't confuse ports with IP's, they are very different things. In every day terms, every device on your network has to have it's own unique IP address. If you accidentally assign the same IP to multiple devices, bad things will happen so for that reason and NAT addressing, DHCP is used in most networks to handle IP address assignments.

@Jimbo.Automates Here's a link to the Elk shutoff valves. https://www.elkproducts.com/product/water-shutoff-valve-wsv2/ Just when you thought you were done with the Elk NS 😀

@rick.curl I'm not sure if you are trying to move away from Insteon, but you can still purchase new 2475F's from Insteon. https://www.insteon.com/ceiling-fan-controller Otherwise any z-wave relay would work. Here's some from Amazon. https://www.amazon.com/s?k=z-wave+relay&crid=FZCBXAEY40CP&sprefix=z-wave+relay%2Caps%2C181&ref=nb_sb_noss_1

@keepersg You may be running into simple IP communications problems. The Elk can only connect to one device at a time. So if it's connected to something other than the eisy that may be the problem. Same thing applies to RP2. When you are connected via RP2, the Elk NS won't be communicating with the panel.

Update on Polisy running 5.6.4. Opened AC <Config><Upgrade Packages> Polisy beeped after about 5 seconds, then 10 seconds later beeped again with a different tone. Approximately 1 minute later I heard 5 beeps and then a single beep signalling the reboot. Cleared Java et all downloaded the new start.jnlp and started AC. AC started but complained that the version of AC and the version of IoX did not match and asked to reboot the Polisy again. I clicked reboot and about 30seconds later the Polisy was up and running 5.7.0 and I was able to access it via SSH and AC. No disabled programs The OS did NOT update from 13.1 to 13.2 at that time. Clicking on <Upgrade Packages> from 5.7.0 A dialog box came up indicating that an OS update was available and it would take approximately 30 minutes to complete. That update is running now. STATUS UPDATE: The update of the OS did not complete. Tried three times. Opened a ticket with UD. I will update as more information is available.

@GTench please DM Chris as the instructions say to do. You can also open a support ticket.

@GTench

I had an unusual issue following 5.6.4_6/7 snafu. We know that one or more versions of 5.6.4 caused a weirdness with sockets that resulted in system files being corrupted. If you had a backup all you had to do was update to 5.6.4_8 dated 8/11/2023 and then restore your system which I did, but a couple of programs would not work post restore. I tried for hours to figure out why the devices in the associated scenes / programs could not be controlled by AC, but worked fine from UD Mobile. Finally I just deleted the programs that didn't work and starting from scratch rewrote them exactly as they had been. This fixed the problem. So if you have any weirdness post 5.6.4 with your programs, I'd try that as a solution.

@pinlawr Based upon @Rick Kacel post above, you might open AC go to <Config><System> and click <Install Dev Packages>. This can take quite some time as I recall. Up to 20 minutes so wait patiently for your Polisy to beep five times and then reboot followed by a single beep. If that fails I'd go ahead and open a support ticket with UD support. They will need to take a look at whats going on.

@Rick Kacel sounds like you're half way there! Go ahead and open a support ticket with UD at https://www.universal-devices.com/my-tickets/ Changing permissions is something I'd prefer UD walk you through. And if you would be so kind as to post the fix, we can use it to help others in the future.

@CoolToys, it's important to understand that not only did you change hardware but you also changed from a dedicated ISY Elk Module to the new ELk Polyglot Node Server (NS) which replaces the older ISY Elk Module. On eisy there is no longer any module support so that is why you need to purchase and install the new Elk NS before you can do anything. I believe from the last line of your post that you have done this. If not, then open your web browser and type in https://your_eisy_IP:3000. This will start the Polyglot server interface. You will be promoted to sign in if you haven't already. The default user is <admin> and the default password is also <admin> if you have changed the password in AC then you should use that password instead. Now that you are logged in you will need to click on <Node Server Store> Top menu. Then scroll down to Elk and click on the name Elk on the far left. Now find the button labeled <More Info> and click on that. Now you need to read all of this thoroughly. You should also check out the Elk NS Configuration Help section. Use this link as the one on the above page is broken ATM. Now that you have some idea of what the Elk NS can do, it's time to change every single program that used the older Elk Module on your ISY manually. There is no migration available for this complex Elk update, you have to manually update each program for the new Elk NS commands that replace the older ISY Elk module. If you don't have copies of your old ISY programs this is going to be difficult. Hopefully you have that information available. If not you will need to rebuild from scratch all your programs that used to talk to the ISY Elk Module. A quick way to see which programs are broken is to start AC and then go to <Programs><Details> and click the small + button on the top ribbon. Every program that is broken will be shown with a yellow icon. These are the ones you need to look at and rebuild. As far as the MSII's they are not part of the Elk setup nor were they ever. Recently there was a post about the MSII's no longer being found by IoX on eisy. I don't have any verification of this as I don't use MSII's and no longer have any to test with. The recommendation I saw posted was to migrate to a supported z-wave device like the Aeotec MultiSensor 6. https://aeotec.com/products/aeotec-multi-sensor-6/ The newer MultiSensor 7 was not recommended by the posters. Your call. If you find the MSII is indeed not being discovered by IoX on eisy then you can also open a support ticket at... https://www.universal-devices.com/my-tickets/

For the eisy you need to use: You will need to use putty or something similar to access the eisy via SSH. You can log in with the user name <admin> and the password <admin>, then just copy and past the lines below one at a time and hit <enter> after each one. On the first command you will be promoted for password; use <admin> again. sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b90260e8_2/.local bitstring pip3 install --prefix /var/polyglot/pg3/ns/0021b90260e8_2/.local bitstring==3.1.9 Note that the directory /0021b90260e8_2/ may need to be changed for your installation of the LifX NS. Look at your Polyglot dashboard and find the LifX NS slot number; in your case slot 2, then open putty and <cd> to /var/polyglot/pg3/ns. Then type <ls> you will see a list of NS by slot number, cut and past the correct NS name into the above command lines replacing /0021b90260e8_2/ in both lines with your specific NS name. I have updated the above command for the NS listed in the output you supplied, but if something has changed you will need to verify it first.Be sure to use the correct one. When you type <ls> you should see an output similar to the below with more or less directories depending on your particular setup. Just find the NS with a name ending with the proper slot number. [admin@polisy /var/polyglot/pg3/ns]$ ls 000db9560fac_1 000db9560fac_11 000db9560fac_3 000db9560fac_5 000db9560fac_7 000db9560fac_9 000db9560fac_10 000db9560fac_2 000db9560fac_4 000db9560fac_6 000db9560fac_8 You will need to restart Polyglot after you install Bitstrng 3.1.9. You should then see device discovery working. If not open a ticket with UD as the problem is not Bitstring.

@Rick Kacel Sorry mate, but we need a lot more information before any help can be offered. What platform are you on? ISY w/RPi. Polisy, or eisy, and what versions of firmware are you running? A log of the NS output would be especially nice. Please change it from INFO to DEBUG and then do a restart so we can see what is happening in more detail.

@pinlawr You may be running into the btistring problem from awhile back. Check and see if the module that's not loading is bitstring. The version of bitstring that the LifX NS relies on is old and since no one is maintaining the NS you'll need to down rev the module being called. Here are the commands to do that. sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/.local bitstring pip3 install --prefix /var/polyglot/.local bitstring==3.1.9 Restart the LifX NS from the web interface and you should be good to go. I don't recall having to reboot the Polisy, but if you have problems after this I'd give that a shot before you get back to us.

@sjpbailey A small issue with updates not affecting functionality. In this case the NS is being flagged as out of date, but is actually running a more current version than what is being recommended. Not sure if this is a dev option or in the core so I thought I would post it for review.

I had not known that remote access for PG3 had been enabled, This is amazing! Thank you. I went ahead and tried to remotely connect to one of the Polisy's I manage and I must of missed a step. This is what came up, but no browser window opened, nor was I able to access the Polisy in an active PG3 browser session. It shows as connected, but I'm not sure how I actually interact with the PG3 web interface for the remotely connected Polisy. Can you point out where I went wrong? Thank you.

I've used these Aeotec 6, with decent reliability, but I install them with a wired USB power supply. I was never a fan of the battery operation. The delays on activation and the window until it would shut off was too long as I recall. The fix was to supply them with a USB power source. This is a z-wave device. There is now a version 7 Aeotec 7 available as well and also a Zigbee motion only sensor Aeotec Zigbee Motion from the same company. One of these might meet your needs. Keep in mind Zigbee support is limited at the moment and would not support the motion only sensor out of the box.

@PapaBear When I get back home next week I think I have a MSII in my box of spares. I'll pull it out and test it with a PoliSy. I don't have an eisy to test with, but the OS is the same so let's find out what happens. I hated the MSII and all its failings due to UDI being unable to get any engineering docs from Insteon at the time. UDI had to revers engineer the features that are supported. The MSII just never worked reliably enough to meet real world wife standards, but I'll see if I can get one to link as a test.

@zorax2 I'd try defaulting the 6-button keypad and do a restore device again. It's important to actually default the 6-button. Pull the air gap, and then wait a minute, finally press in the air gap and hold it until the switch beeps, about 5 seconds. If that doesn't clear it up, I'd default all the linked devices and redo the scene from scratch. I suspect you have a bit not set or incorrectly set and a clear should fix it.

@shbatm Is this something you can shed some light on? Thank you!

@Ross, check out this NS from @sjpbailey. https://github.com/sjpbailey/Documentation/blob/main/Tuya Relay/README.md

AC update took less than minute. Rebooted via AC, about 2 minutes to accessibility. System/Reinstall all Node Servers via PG3x web interface took about 5 minutes for the 11 NS's I have installed. Manually restarted each of them and everything is once again operational. I also DL'ed the PG3x log and did a quick search for 3.0.60 which was not found so I'm unsure if the UDI interface was updated. Is there a way to check via SSH?

@cosyn , @sjpbailey just released a bunch of NS's one of them is exactly what you want. Here's the link to the documentation on the NS and HW. https://github.com/sjpbailey/Documentation/tree/main/Tuya Relay

So I opened a ticket on Saturday and as usual got an almost instant reply from Michel. That man never sleeps! We went back and forth a couple of times on more detail, but Michel came up with the answer. The Smartenit devices are not dual band and have to be on the same electrical leg to communicate with the PLM effectively. They are also very susceptible to line noise. I had moved my PLM a couple of weeks ago and this is what started my problem. As soon as I moved the Smartenit's to be on the same electrical leg as the PLM they were again able to be discovered by an Insteon device search via AC. FYI they are called; I had forgotten, not Smartenit but by their original name COMPACTA 2X4

@n_sievers great information, thank you! I'll follow up with Smartenit, but I want to wait and verify that the 2X4 is still supported due to it being removed from the supported devices list in IoX. If you Start Linking and try to manually add a Smartenit 2X4 it used to be in the list. It's not there anymore. If it is still a supported engine type and I missed it in the list. Then I would agree it's the 2X4 itself that has failed...bummer. I'll keep you posted on Smartenit support in IoX when I get a response to my ticket.