SteveBL

Hi guys, I'm still have no local control with the eisy from the AC in setting the "Armed Status" and no errors in the NS log. Yet I can control it from UD Mobile and see it in the log. I also installed a recent copy of my Elk Lighting file to ElkRP and I'm getting no control of any devices through the M1. No devices have been changed from the switch to eisy. I have done restarts of the AC and PG3 and even re-installed the Elk NS with no success. Another anomaly is with hardwired motion sensors; all parameters are set the same for both sensors, one living room and one Office. I have a pgm that turns on my Office lights if motion is detected, and another pgm for the Living room that turns on path lighting from sunset to sunrise. The Office works perfectly and shows in the NS Log, yet the Living room doesn't work at all and no errors in the NS Log. Both sensors are working and can be triggered when tripped or if there is an alarm condition. Everything worked for years with 994i

Thanks Jim, Yes I thought I'd seen that topic explained somewhere but it's so difficult to search for a thread on here sometimes.

Is there any way to create an export data file for import into ElkRP2 like we used be able to do on the 994 in Elk config?

Yes I am hitting the "Set Armed Status" button. All of the options are listed "Armed Away, Armed Instant Mode" etc but they do nothing and there is no activity in the Elk NS logs. Yet I can arm/disarm etc from UD Mobile and of course the keypad, with activity showing up in the log file.

Hi Jim, I've sent both the "info" and "debug" files. Again, I can arm/disarm etc from UD Mobile and I see instant response in the logs but nothing happens when I trigger from the AC; no errors or info... nada.

User code is fine. I can arm and disarm the M1 with UD Mobile, although it is slow to respond, however, I cannot arm or disarm from within the admin console.

eisy/Iox: 5.5.4 Pg3: 3.1.20, Elk NS: 3.5.8 I'm having a few issues with the Elk NS that I can't figure out. After a successful install of the NS everything populated fine but the "Armed Status" is not working, I can't arm/disarm from the eisy. I also see no errors in the log. On the "Main House" screen "arming status" shows the current state, "Arm Up State" is accurate, as is Last User Keypad" and "Last Triggered Zone". Also the "Last Violated Zone" is not accurate. As I walk around and trigger zones manually they all report accurately as do the various arming/disarming settings.

PG3x Version 3.1.18 Status: Connected Frontend Version: 3.1.18 IoX Version: 5.5.2 Connected Uptime: 41 Minute(s) 15 Second(s) (c) 2023 UDI

Yes I'm running 18

I'm wondering if I should delete the M1 node server from the eisy and re-install it. I've set the host to 192.168.1.251:2101 since I read that it uses the non-secure port.

Not having had any experience with PG3x, or node servers for that matter, I'm have some setup issues connecting my Elk M1 to the eisy. It sure was "eisy-er" on my tried and true 994i with the Elk plug-in! I've installed the ELK node server and it shows as "connected" and the "M1EXP status" is "connected" in the eisy but it's not pulling any data from the M1. the import from my 994 brought over all of my lighting but not my "area 1" nodes. I've set the port to 2101, the non-secure port. I've set the "user_code to my M1 password.

Problem solved. The cable is working but it will not show up as connected until you Restore the PLM from the Admin console. Now it shows an address and it is indeed connected!

Hi @jhoulihanI was wondering if you'd received your UDI cable kit yet and, if so, is it working for you? I have the the cable kit but it's not working with my 2413S to the eisy.

I am using the USB to RJ45 cable kit that @Michel Kohanimput together and it's not working. The 2413S is fine and working with my 994. The gremlins are having a field day...

I just received my "Official" UDI PLM "cable kit" for my eisy to 2413S and it will not connect. The "pretty" blue light is lit on the USB to DB9 connector and the eisy OS is showing "uplcom0: Prolific Technology Inc. USB-Serial Controller, class 0/0, rev 2.00/6.05, adr 4 on usbus0" yet PLM diagnostics shows "/ Not Connected." I would not think that there would be any cable or pin corrections needed with the UDI cable set... right? Before getting the UDI cable set I tried to connect my PLM with the eisy using my own cables and DB9 to RJ45 adapter/USB to DB9 cable and an assortment of ethernet cables and nothing worked, hence my purchase of the UDI Cable set. The 2413S works perfectly on my 994i. Any help would be appreciated! Also any news as to the birth of the "new and improved" PLM's? Insteon say's it should be sometime in Q1.

Geddy, that did it! Yes I had tried a manual add several times without success. Thanks to your suggestion I tried it again after doing a network reset on the eisy then a manual add and it's now up and running! Thanks again Geddy Happy New Year! Steve

Problem: New eisy now not showing up in Iox Finder and I can't access the Admin Console. It has a local IP address and I can Ping it. I have cleared Java and also downloaded the most recent Iox Finder again. It WAS showing up yesterday and all was fine. I've done a network reset on the eisy and also another complete Factory reset but can't see it locally anymore but I can Ping it. I also have a 994 connected to the same network and it's working perfectly and shows an IP in the Portal Information and shows up in Iox Finder.. The eisy is online, shows in the Portal, I can access it with UD Mobile, but doesn't show an internal IP assigned under "information" in the Portal and can be accessed via "ISY Web access" just not locally so no Admin Portal. It's got me stumped

Reset Networking Click the button 4 times Reboot Click the button 5 times Shutdown Click the button 6 times Factory Reset Click the button 10 times

Home automation company Insteon reportedly goes out of business by Duncan Riley Insteon, a home automation company owned by Smartlabs Inc., has reportedly gone out of business after users reported that their connected devices stopped working last week. There has been no official word from the company that it has ceased operating and as of the time of writing its website is up and its status page claims that all services are online. Stacey on IoT reported Saturday that customers who have been trying to contact the company since Friday have not heard back from it. Insteon/Smartlabs executives have either scrubbed references on LinkedIn to working at the company or say that their positions have now ended. Insteon was founded in 2005 and offered a range of home automation hardware and software. The company’s devices included intelligent light switches, lights, thermostats, motion sensors and other electrical devices. Insteon’s smart devices connected through power lines or radio frequency. The company’s devices were pitched as easy to install without any expertise or automation background. The devices worked with smartphones, tablets and computers, as well as offering support for Amazon Alexa and Google Assistant. Insteon was also one of two smart-home hub manufacturers to support Apple Inc.’s HomeKit when it launched in 2015. The parent company Smartlabs Inc. had the same executives as Insteon and, along with offering Insteon equipment, also held a license with Nokia to use the name “Nokia Smart Lighting.” Smartlabs was acquired by Richmond Capital Partners in 2017, although it’s not entirely clear whether the firm owns Smartlabs today: Crunchbase lists Smartlabs as both an acquisition and an exit for the firm. The company never reached great heights of popularity despite being in business for 12 years, but it did have a sizable user base. How big is not clear but at least thousands of customers are left with smart home equipment that does not work as designed. The case highlights consumers’ risk when relying on a company to provide services to support smart home or connected devices. Since the devices rely on an outside connection, when the company is no longer in business or drops support, the devices often become unusable. For Insteon users, however, there is an alternative. According to Ars Technica, Insteon’s protocol has been reverse-engineered, so it’s possible to control the devices locally without the app. It’s also possible to pipe local control to another platform’s hub controller.

Well I do have the Elk Module and using EkeyPad Pro, it shows up just fine but I don't see it at all using UD Mobile yet I see all of my other devices. I currently don't have a Polisy but it looks like that will change pretty quick here.

I've been trying to integrate my Elk MI into the UD Mobile app but can't seem to do it? Is it added as a NODE, and if so how is that done? Thanks!