theedudenator Posted January 6, 2015 Posted January 6, 2015 I have the M1XEP with latest firmware. The unsecure port is disabled. ISY integration module will not connect. Now what should I do?
Michel Kohanim Posted January 6, 2015 Posted January 6, 2015 Hi theedudenator, Please make sure you have 4.2.18 or above and then check https client settings in you ISY. For strength choose All. http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security Michel
theedudenator Posted January 8, 2015 Author Posted January 8, 2015 I don't have that version of firmware on the ISY I have a ISY 99i device. The ISY and ELK worked fine prior to the ELK update.
MWareman Posted January 8, 2015 Posted January 8, 2015 Don't know for sure, but its likely that Elk removed SSL3 due to the vulnerability, and the 99i (non-pro) only does SSL3. You'll likely have to use the non-secure port or upgrade to a 994 where the base crypto is now TLS1.0.
shannong Posted January 12, 2015 Posted January 12, 2015 That would be my expectations, too. However, the release notes do not reference removing SSL. It's likely though because they updated the M1 cloud service in this firmware update and it seems doubtful they'd update an internet based service without removing SSL due to the POODLE vulnerability. Sadly, the release notes also say you cannot rollback to previous versions after this update. You're stuck in the middle.
shannong Posted January 12, 2015 Posted January 12, 2015 I just now noticed the title says "DOES NOT ALLOW UNSECURE" port. But the first post says "The unsecure port is disabled." I just updated my M1XEP and can't connect with the UNSECURE port. Now my integration isn't working. ARRGHH! The ISY attempts to connect and it fails all within a second. Obviously there's a problem negotiating since it fails so quickly vs a timeout. I've already rebooted both devices. My ISY is on 4.2.22. I can connect to the M1 over the network using ElkRP.
shannong Posted January 12, 2015 Posted January 12, 2015 Cancel the sirens and emergency crews. I disabled the non-secure port on the M1XEP and enabled it again. The ISY can connect again.
DennisC Posted January 14, 2015 Posted January 14, 2015 Cancel the sirens and emergency crews. I disabled the non-secure port on the M1XEP and enabled it again. The ISY can connect again. Shannong, After upgrading your M1XEP are you still able to arm/disarm your Elk from the ISY's default Web interface UDAjax? Also, can you still arm/disarm from the Admin Console? Thanks, Dennis
shannong Posted January 18, 2015 Posted January 18, 2015 I can from the Admin Console, but I haven't tried the web interface. I'll test tomorrow and let you know.
shannong Posted January 20, 2015 Posted January 20, 2015 Yes. I can arm/disarm from Admin Console, a program, and the Web GUI. I'm no longer using the non-secure port. I finally got TLS working.
DennisC Posted January 20, 2015 Posted January 20, 2015 That's great. I thought I read in the release notes that the upgrade wouldn't work with Java and I was wondering if that meant we would loose some functionality with ISY. Thanks for taking the time to confirm everything still works. Dennis
WetCoastWillie Posted January 24, 2015 Posted January 24, 2015 I'm having the same problem it seems... I just updated all the firmware on all of the Elk M1 components, now the ISY will not connect, I have tried both non secure (2101) and secure (2601) ports but the ISY will not connect! I can log into the elk with ELKRP with no problem... I'm on day two of trying to figure this out but I'm not having any luck. is there something I'm missing?
shannong Posted January 25, 2015 Posted January 25, 2015 How did you connect from the ISY before that? Port 2101 or 2601? For me it was a problem with my Elk M1EXP . I had to to disable non-secure port (2101) and then enable it again. Problem resolved. However, shortly after that I got TLS (secure/SSL) working so I'm now using the secure port. (2601)
WetCoastWillie Posted January 25, 2015 Posted January 25, 2015 I was using 2101... after the firmware update on the EXP i lost all comunication between the two. from what i read the upgrade does not allow the unsecure port 2101? what was involved in getting port 2601 to work, I was reading the link that Michel posted about a security certificate....?
MWareman Posted January 25, 2015 Posted January 25, 2015 When the M1EXP reboots, it can take an extraordinary amount of time before ISY can connect. Made me think there was a problem once when there wasn't. Just want to make sure you've considered this. Also, if ElkRP is connected, everything else gets locked out, including ISY. That once is well known though, just wanted to make sure you were aware. No cert issue is going to affect a connection to the non-secure port - it has to be something else.
shannong Posted January 26, 2015 Posted January 26, 2015 Nowhere in the release notes or documentation does it say that the firmmare upgrade does not support the non-secure port. As mentioned, I got it working again on mine. Did you disable and enable again the non-secure port as recommended using ElkRP? Can you connect to the M1 using ElkRP with the non-secure port? For the secure port, I had set my ISY HTTPS Client settings to "1.2". The M1 only supports 1.0 so once I set it that I was able to connect with HTTPS.
kstock Posted January 29, 2015 Posted January 29, 2015 Extraordinary frustration here. M1EXP updated to latest firmware as above. Have been able to get ISY994i to connect to Elk thru non-secure port. ISY receives updates from elk, but I cannot control any aspect of elk thru ISY. The elk console will no longer load; gives an error message. Everything worked fined before M1EXP firmware upgrade. Tried the disable then re-enable of the non-secure port in ElkRP as noted above without effect. At a loss.
kstock Posted January 29, 2015 Posted January 29, 2015 Just thinking, is there a router port forwarding requirement here, of the secure and/or non-secure ports? If so, this is new.
kstock Posted January 29, 2015 Posted January 29, 2015 My latest is that I am now able to control Elk thru ISY (had to tweak the user access code parameters in ElkRP). However, the Elk console still won't load in ISY (as it always did before). I get a IE browser error message "the device or resource xx.xx.xx.xx is not set up to accept connections on the port HTTP, where xx.xx.xx.xx is the ip address of my M1XEP. Can't figure out what's blocking the communication. Any thoughts?
theedudenator Posted February 28, 2015 Author Posted February 28, 2015 I now have the latest ISY 994i I have the Elk module. At the main screen when I select ELK I cannot see anything related to my system I cannot arm/disarm
theedudenator Posted March 2, 2015 Author Posted March 2, 2015 My current error message. Elk Rest command failed, checking elk status: Connection: Disconnected Module: Enabled
Michel Kohanim Posted March 2, 2015 Posted March 2, 2015 Hi theedudenator, Please submit a Ticket. With kind regards, Michel
theedudenator Posted March 4, 2015 Author Posted March 4, 2015 Got it to connect now. It can see the Elk system. But I cannot make changes. Arm/Disarm or elk motion is not triggering insteon events.
GSpitale01 Posted April 14, 2015 Posted April 14, 2015 I have a similar problem - ISY and Elk worked using either port 2101 or port 2601. Then I upgraded the M1EXP firmware and all ISY to Elk communication stopped. After reading through this thread and fiddling with secure/non secure ports and TLS settings, I disabled and then renabled the non secure port on the M1EXP and now ISY is getting status from ELK but I cannot arm/disarm ELK through the UDAjax admin console. Anything else I should try?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.