PCRover Posted November 27, 2014 Share Posted November 27, 2014 I am new to the ISY system and have run in to an odd situation when trying to work with scenes. When I create a new scene, then click on the name in the tree, The "ISY Finder" pops up and I get an authorization failed message. The Factory installed scene does not do this when I click on it. Then after hitting "Ok" on the error message if I do a "test scene", I get the same "ISY Finder" popping up and the "Authorization Failed" message but the test appears to process. Anyone know what is going on here? Link to comment
PCRover Posted November 27, 2014 Author Share Posted November 27, 2014 It doesn't matter what method I add a scene with, same result. "Authorization Failed" after it is added. My ISY is a factory installed Z-wave version and had a scene already added, but had no devices in it. I do not get the "Authorization Failed" with that scene. My new scene "Test Scene" has a Z-Wave wall outlet module in it for testing, but there is no difference in the results with various devices added to the scene. Link to comment
Michel Kohanim Posted November 28, 2014 Share Posted November 28, 2014 Hi PCRover, Authorization Failed means that the Admin Console has a stale userid/password for ISY. Please restart the Admin Console and retry. With kind regards, Michel Link to comment
PCRover Posted December 1, 2014 Author Share Posted December 1, 2014 That is not it. New fresh session, same results. Also I cannot delete the new scene unless there is a device in the scene. When empty I get a popup that says "TCP Client DNS Error" "dispatcher.mobilincconnect.com Link to comment
Michel Kohanim Posted December 2, 2014 Share Posted December 2, 2014 Hi PCRover, Can you please go to Tools | Diagnostics | Show PLM Info/Status and let me know what you see? Also, please do not hesitate to contact our tech support team (links below) who'd be able to help figure out the root cause. With kind regards, Michel Link to comment
PCRover Posted December 5, 2014 Author Share Posted December 5, 2014 It was a bad connection to the PLM. I would never have thought the PLM could cause that kind of error. Thanks! Link to comment
stusviews Posted December 5, 2014 Share Posted December 5, 2014 The PLM didn't. The bad connection did Link to comment
GGITech Posted March 18, 2015 Share Posted March 18, 2015 I am getting this error, but I DO NOT HAVE a PLM connected. Any idea? Link to comment
Michel Kohanim Posted March 19, 2015 Share Posted March 19, 2015 Hi GGITech, In 4.2.x branch, scenes are INSTEON specific and, since you don't have the PLM installed, you are going to get that error. Do you plan on ever having a PLM? With kind regards, Michel Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.