Elk status

[d00gster]

I saw the thread on how to setup ELK status. in my case, instead of armed, disarmed, etc. I get a numeric value for the status. any ideas why? 

 

I'm on 5.6.4 and latest UD mobile version. I am also fully synchronized 

[DennisC]

2 minutes ago, d00gster said:

I saw the thread on how to setup ELK status. in my case, instead of armed, disarmed, etc. I get a numeric value for the status. any ideas why? 

 

I'm on 5.6.4 and latest UD mobile version. I am also fully synchronized 

Most common reason is a reboot of ISY is required.

[d00gster]

I rebooted numerous times. no change

[Jimbo.Automates]

Just confirming, you did a resync of UDM after restarting IoX?

Also, do the correct status names show up in the AC?


Sent from my Pixel 6 Pro using Tapatalk

[d00gster]

The answer is yes and yes.

 

I rebooted and re-sync'd

 

the status shows as disarmed in AC

[Jimbo.Automates]

Not sure, will need help from @Javi

 

[DennisC]

18 minutes ago, Jimbo.Automates said:

Not sure, will need help from @Javi

 

@Jimbo.Automates

I had this happen to me awhile back with Weatherflow. It turned out there was an old nls file, EN_US.TXT,  left over that interfered with proper display of the values.

I was told to locate and delete the file, then to restart IoX.

Maybe?

[Jimbo.Automates]

@Jimbo.Automates
I had this happen to me awhile back with Weatherflow. It turned out there was an old nls file, EN_US.TXT,  left over that interfered with proper display of the values.
I was told to locate and delete the file, then to restart IoX.
Maybe?

Shouldn't be an issue. ELK creates a new nls on restart since it has to be customized for each person.

Sent from my Pixel 6 Pro using Tapatalk

[Javi]

16 hours ago, d00gster said:

The answer is yes and yes.

 

I rebooted and re-sync'd

 

the status shows as disarmed in AC

Hi @d00gster,

Please open a ticket. Include your UUID and I will provide instructions for remote diagnostic.

[Javi]

Hi @Jimbo.Automates,

I think I may have found the issue.  There are two US-English NLS files being created, one upper and one lower case.

<profile family="10" id="1">
<files dir="nodedef">
<file name="PORTNDEF.XML"/>
<file name="nodedefs.xml"/>
</files>
<files dir="editor">
<file name="custom.xml"/>
<file name="PORTEDIT.XML"/>
<file name="editors.xml"/>
</files>
<files dir="nls">
<file name="EN_US.TXT"/>
<file name="en_us.txt"/>
</files>
</profile>

I believe the EN_US.TXT is being created in error as it only contains a small number of definitions

ND-occupancy-NAME=Occupancy
ND-occupancy-ICON=MotionSensor
ST-ST-NAME=Occupied
ND-occ2_device-NAME=Occupancy v2.0 (Mobile Device)
ND-occ2_device-ICON=MotionSensor
ND-occ2_geofence-NAME=Occupancy v2.0 (Geofence)
ND-occ2_geofence-ICON=MotionSensor
ST-occ2d-ST-NAME=Occupied
ST-occ2g-ST-NAME=Occupied

Was this somehow created by ELK? Does not look related.

[Jimbo.Automates]

No idea where that came from. Was another node server in the same slot previously and it didn't get cleaned up?

Sent from my Pixel 6 Pro using Tapatalk

[Javi]

31 minutes ago, Jimbo.Automates said:

No idea where that came from. Was another node server in the same slot previously and it didn't get cleaned up?

Sent from my Pixel 6 Pro using Tapatalk
 

Thanks Jim, Looking into this.

[d00gster]

..

 

Edited September 20, 2023 by d00gster