Recently, perhaps with a recent update, elk module no longer reports any of my keypads, except maybe a parameter shows up and then goes away, and a handful of zones show no status. I see no pattern to the zones not showing. If I open elk rp2 all status is there. If I query, it might temporarily report voltage. I restarted the node which didn't help. I really don't want to delete and re add the node because of all the reorganizing I did with folders and names for the various things that would all need to be redone.

Same. This started a while back, then fixed itself and is now back.

I get status of 1's and 0's in UDM and in Pushover notifications.

So I have isolated the problem to logging in via the portal user/password. Anything that uses the portal (UD Mobile and admin console not using port 8080). For example.

This screenshot is from logging in using port 8080 admin/password

@bmercier

And simultaneously on another computer using the portal login.

I can confirm same on ud mobile. I switched to local settings and now it populates everything.

I am also having similar problems with UDM and the AC.

Working with Javi to solve.

Here is a summary of what I am seeing:

-Nodes are NOT populating in:

1. UDM via my.iso.io,

2. AC thru my.iso.io,

3. New UI 

-Nodes ARE populating in:

1. AC thru direct connection,

2. Portal/ Select Tool / Isy Web Access

I could not get UDM to connect directly to test. Kept getting a SSL error. 

Nodes not populating include Zwave, Insteon and certain plugins. 

ELK plugin is also reporting numbers vs status. 

1 hour ago, dbwarner5 said:

I am also having similar problems with UDM and the AC.

Working with Javi to solve.

Here is a summary of what I am seeing:

-Nodes are NOT populating in:

1. UDM via my.iso.io,

2. AC thru my.iso.io,

3. New UI 

-Nodes ARE populating in:

1. AC thru direct connection,

2. Portal/ Select Tool / Isy Web Access

I could not get UDM to connect directly to test. Kept getting a SSL error. 

Nodes not populating include Zwave, Insteon and certain plugins. 

ELK plugin is also reporting numbers vs status. 

Exactly. @Javi

This has been going on for at least a couple weeks. It is consistently the same nodes that don't work while other nodes that seemingly should be identical work fine. The first place I noticed it is a perfect example. I have shortcuts setup for my garage door and my wife's garage door. Both are Elk zones (zone 22 and 34). On different expansion boards, but I don't think that is a reason. When the doors are closed or open I have to change the color of the icon from red to green. So I quickly noticed that the icon was neither, but rather the default blue. Every now and then, it would populate, say "closed or open" and set the color, but typically, just blue. My wife's door, always populates.

It will populate on occasion. It seems like the way to have that happen is to have the admin console open or have UD mobile open, and then change the status of the node. It will populate, but it doesn't stay populated for long. Certainly won't stay populated if you close your session and open again.

Here it is:

And then there is also the 0 and 1 for Elk status instead of armed/disarmed/etc which, as far as I an tell, is a different issue with the newer firmwares.

Edited November 2Nov 2 by apostolakisl

To further this, it is not just Elk. It is seemingly random nodes across the entire system. Insteon nodes, PG3x nodes, Nodes from IoGuy Nodelink. I see no pattern to it. @Javi

Example:

Admin console on local connection:

Admin console as viewed via portal login at the exact same time from different PC:

Makes sense.  There are 2 issues, Property Value Formatting and Missing Property Values.

We are still looking into the cause of both issues.

Missing Property Values has been replicated on Portal Connections when going through EisyUi***, EisyUi local, and Admin Console Local on port 8443. 

***Firmware 6.x and greater use EisyUi for portal connection and the Admin Console when Local on port 8443.

Local connections on UD Mobile uses port 8080 so does not use Eisy UI, same with Admin console when using port 8080.

If using UD Mobile on Portal clicking into the Device Dashboard will perform a new Property Value Query. While not ideal it is the current work around until fixed.

@Javi

Where do we stand on this? I can't log in using anything but port 8080 unless I am OK having about 20% of my stuff not populate.

I, too, would like to know if there is anything in process to fix the Elk problems related to the upgrade. I am holding off on the upgrade to 6/7 until this is more stable. I am unclear if this is a node server issue or something else. Clarification on that would be helpful.

I was having trouble with my Elk alarm, but with a restart of the PG3 node, it now works. sorry to cry wolf.

Edited Sunday at 01:14 PM2 days by someguy

Initially I thought this was an elk node issue because that is where it was immediately obvious in my daily usage. But it is lots of nodes. Stuff randomly won't populate when accessing through the portal. Accessing locally via port 8080 works correctly. ISY is functionally populating based on the fact that programs run correctly, it is just that the portal isn't feeding the data to UD Mobile or to the admin console when using the portal as the means of accessing ISY

I reached out to javi a few days ago on a different thread.

response was that a new firmware version should be out soon that will fix these issues.

@everyone firmware should be released this week.