I transitioned to EISY and loaded ELK Module (after some difficulty getting into Polyglot).

The nodes all appear to have enter into the EISY, and I have fixed most of my programs. Unfortunately I did not copy the programs, I just did a backup as I thought everything would carry over.  Even tried loading back into ISY, but says it is in safe mode and doesn't copy the programs.

I have 2 problems with ELK Module now:

1. After I click Elk module in UD Mobile I get 2 errors saying "Could not get custom. Client is null. 500" then it says "Could not get node servers. Client is null. 500"

2. The ELK log says "Invalid Credential. Please check username and Password. 401".  I entered a new user in ELK named it EISY and gave it a separate passcode.  Used that passcode in ELK Server user_code.

How do I fix?

 

13 hours ago, JSchumann said:

I transitioned to EISY and loaded ELK Module (after some difficulty getting into Polyglot).

The nodes all appear to have enter into the EISY, and I have fixed most of my programs. Unfortunately I did not copy the programs, I just did a backup as I thought everything would carry over.  Even tried loading back into ISY, but says it is in safe mode and doesn't copy the programs.

I have 2 problems with ELK Module now:

1. After I click Elk module in UD Mobile I get 2 errors saying "Could not get custom. Client is null. 500" then it says "Could not get node servers. Client is null. 500"

2. The ELK log says "Invalid Credential. Please check username and Password. 401".  I entered a new user in ELK named it EISY and gave it a separate passcode.  Used that passcode in ELK Server user_code.

How do I fix?

 

1. Will need @Javi to help with that issue.

2. This is not a user_code issue.  Did use the non-secure port of the ELK when entire host?

7 hours ago, JSchumann said:

but says it is in safe mode a

Why are you in safe mode? Are you using Insteon and is your PLM working?

Since the address of each device changes with the node server, programs need to be fixed manually. A back up wouldn't help.

Are you using any other node servers and are they working?

As a test to see if the node server is connected to Elk, violate a zone and see if it shows violated in admin console.

9 hours ago, Jimbo.Automates said:

1. Will need @javi to help with that issue.

2. This is not a user_code issue.  Did use the non-secure port of the ELK when entire host?

Yes I am using 2101

3 hours ago, DennisC said:

Why are you in safe mode? Are you using Insteon and is your PLM working?

Since the address of each device changes with the node server, programs need to be fixed manually. A back up wouldn't help.

Are you using any other node servers and are they working?

As a test to see if the node server is connected to Elk, violate a zone and see if it shows violated in admin console.

ISY defaulted to safe mode after Migration

Understand changes, but I deleted some of the lines, and need to re-create them

No other node servers

Will violate a zone and check

2 minutes ago, JSchumann said:

ISY defaulted to safe mode after Migration

I would suggest you should start troubleshooting with the first thing that is wrong, namely ISY is in safe mode. That is not normal. Take a look at this from the wiki: https://wiki.universal-devices.com/index.php?title=INSTEON_Safe_Mode_Dialog

I'm wondering is your migration was not complete, because of the safe mode start up. Have you tried rebooting since?

Yes I am using 2101

Please download log package from the PG3 UI ELK node server page and PM it to me.

Sent from my Pixel 6 Pro using Tapatalk

 

On 10/14/2023 at 7:57 PM, JSchumann said:

2. The ELK log says "Invalid Credential. Please check username and Password. 401".  I entered a new user in ELK named it EISY and gave it a separate passcode.  Used that passcode in ELK Server user_code.

I reviewed the log package you sent and see no issues.  When you said "ELK Log" I assumed you meant the ELK node server log.  I'm not sure why the ELK would give an Invalid Credential because the node server doesn't send username/password, it connects to the non-secure port where that is not required.

Again, the node server log looks fine, please let me know what issue you have with the node server.

 

So I tried to arm my elk from UD Mobile and I get:

<?xml version="1.0" encoding ="UTF-8"?><RestResponse succeded="false""><status>404</status><reason code="1" /></RestResponse> . 404

So I tried to arm my elk from UD Mobile and I get:
404 . 404

Where did you get that response? Please try from the Admin Console.

Sent from my Pixel 6 Pro using Tapatalk

1 hour ago, JSchumann said:

So I tried to arm my elk from UD Mobile and I get

 

1 hour ago, Jimbo.Automates said:

Please try from the Admin Console.

Once you have it working from the admin console, try syncing UD Mobile and try again.

3 hours ago, Jimbo.Automates said:

Where did you get that response? Please try from the Admin Console.

Sent from my Pixel 6 Pro using Tapatalk
 

I got the response in UD Mobile

From admin console, main, network, home, set armed status, it shows disarmed.  If I select armed away and click set armed status, it changes back to disarmed.

If I click query, I get TCP client request failed [NS-2-ELK:401]

43 minutes ago, JSchumann said:

I got the response in UD Mobile

From admin console, main, network, home, set armed status, it shows disarmed.  If I select armed away and click set armed status, it changes back to disarmed.

If I click query, I get TCP client request failed [NS-2-ELK:401]

In the admin console, Elk Controller, does it say connected?

4 hours ago, JSchumann said:

If I click query, I get TCP client request failed [NS-2-ELK:401]

@bmercier or @bpwwer This means IoX is not communicating with PG3x, right?

@JSchumann did you happen to open the Admin Console -> Node Servers for this node server and edit the username/password?

 

34 minutes ago, Jimbo.Automates said:

@bmercier or @bpwwer This means IoX is not communicating with PG3x, right?

@JSchumann did you happen to open the Admin Console -> Node Servers for this node server and edit the username/password?

 

User ID is mac address of EISY and password is blank

4 hours ago, DennisC said:

In the admin console, Elk Controller, does it say connected?

Yes, it says connected in nodeserver online and M1XEP status

User ID is mac address of EISY and password is blank

Password is entered when the node server is installed, if you edited that form and saved then it might have cleared the password. @bpwwer or @bmercier is that right? And is there a fix for the 401 error?

Sent from my Pixel 6 Pro using Tapatalk

On 10/14/2023 at 8:57 PM, JSchumann said:

1. After I click Elk module in UD Mobile I get 2 errors saying "Could not get custom. Client is null. 500" then it says "Could not get node servers. Client is null. 500"

 

Is this Android or iOS? Does this issue persist?   If I recall correctly sometimes Android will display "Client is null" error in the Plugins (PG3) section after an unexpected disconnect, but will then start working shortly after. 

53 minutes ago, Javi said:

Is this Android or iOS? Does this issue persist?   If I recall correctly sometimes Android will display "Client is null" error in the Plugins (PG3) section after an unexpected disconnect, but will then start working shortly after. 

Android, yes, it persists

Edited October 18, 20231 yr by JSchumann

55 minutes ago, JSchumann said:

Android, yes, it persists

Thanks.  Does the app appear to work as normal after you dismiss the error messages?

Please do a Query on your Area node again, then download log package and PM it to me.

 

1 hour ago, Javi said:

Thanks.  Does the app appear to work as normal after you dismiss the error messages?

The programs in EISY seem to work ok but I cannot control the ELK from US Mobile or from the Admin console.

1 hour ago, JSchumann said:

The programs in EISY seem to work ok but I cannot control the ELK from US Mobile or from the Admin console.

 

Please follow @Jimbo.Automates instructions below first.

OK.  Let us work one issue at a time, solving this first issue may solve the ELK issue, so don't worry about controlling ELK in the following test.  I only want to see if UD Mobile can communicate with the plugin software.

From UD Mobile got to Admin Tab > Plugins.  Do you get an error here?   If you do dismiss the error alerts, does the app show your installed node server(s) or is there a blank screen?

If there is a blank screen then UDM cannot communicate with the Plugin Software.  So please first verify the eisy firmware is up to date. In UDM > Admin Tab > Firmware select update (or upgrade) if available, if not select "Force Upgrade" then wait for the upgrade to complete.  After firmware upgrade is complete you may get a notification asking to reboot, if you don't get a reboot notification please reboot anyway after about 5 minutes of firmware update completion.  Reboot from UDM > Admin Tab > Reboot.  After reboot please try Admin Tab > Plugins again. If you get an error please post a screenshot.

In the logs you just sent I see many:

10/18/2023, 09:10:32 [pg3] error: IoX Inbound Status: UnauthorizedError: Unauthorized

 

This means that username/password was messed up.  Please close the Admin Console, do a Re-install all node servers from the PG3x UI then open Admin Console when it completes and re-test Arming an area once they all finish.  

1 hour ago, Jimbo.Automates said:

In the logs you just sent I see many:

10/18/2023, 09:10:32 [pg3] error: IoX Inbound Status: UnauthorizedError: Unauthorized

 

This means that username/password was messed up.  Please close the Admin Console, do a Re-install all node servers from the PG3x UI then open Admin Console when it completes and re-test Arming an area once they all finish.  

OK, done. In admin console I go to my area then on the bottom there are drop downs.  I change disarmed to arm away and hit set armed status and it changes back to disarmed.  Still get error messages.  Am I doing it right?

Edited October 18, 20231 yr by JSchumann