It seems to be updating zones but my partition is not updating.

 

It worked fine until I updated.

 

I even deleted the alarm and added it again

 

See screenshot.

 

Seems like same type of behavior withe my ecobee.  I will add that as another bug but there the sensors show up but data is not being updated on the thermostats.

 

In the logs I see a lot of connection type errors.   Again this was working fine before the update.

 

2017-12-10 23:11:01 - Web Request: /general.css
2017-12-10 23:11:45 - TCP: Polling Alarm [hwalrm1]
2017-12-10 23:11:57 - Web Request: /isylink/nodes/n001_hwalrm1/query?requestId=3
2017-12-10 23:11:57 - Alarm: Status Request Sent [hwalrm1]
2017-12-10 23:11:57 - Alarm: Data Sent - ^02,$ [hwalrm1]
2017-12-10 23:12:45 - TCP: No poll response, attempting to reconnect to alarm [hwalrm1]
2017-12-10 23:12:45 - TCP: Reconnecting To Server [hwalrm1]
2017-12-10 23:13:15 - TCP: Reconnecting To Server [hwalrm1]

 

That log shows nothing useful besides a poor connection to the EVL.

what do you want me to send?  Thats what is happening.  It worked fine until the firmware update so something to do with it.

 

I am sure others will have the same issue.  Even Ecobee not working correctly under the new firmware.

Actually ecobee may have been a different issue since all of a sudden it started getting data.

 

As far as the Honeywell Total Connect 2.0.   Under 5.0.10 I have data under all screens.

 

Under 5.0.11a I have data for all the zones but under the main Honeywell entry in the ISY I show no data and also no data under Partition 1

 

See screenshot of missing data in the node server

 

here is the log after a clean reboot where the screenshot showed data

 

2017-12-11 00:44:28 - TCP: Data Received - 8 Bytes [hwalrm1]
2017-12-11 00:44:28 - TCP: Login:[C][L] [hwalrm1]
2017-12-11 00:44:28 - Alarm: EVL User Login - Password Sent [hwalrm1]
2017-12-11 00:44:28 - Alarm: Login:
 [hwalrm1]
2017-12-11 00:44:28 - TCP: Data Received - 4 Bytes [hwalrm1]
2017-12-11 00:44:28 - TCP: OK[C][L] [hwalrm1]
2017-12-11 00:44:28 - Alarm: EVL User Login Successful [hwalrm1]
2017-12-11 00:44:28 - Alarm: Status Request Sent [hwalrm1]
2017-12-11 00:44:28 - Alarm: Data Sent - ^02,$ [hwalrm1]
2017-12-11 00:44:28 - Alarm: OK
 [hwalrm1]
2017-12-11 00:44:28 - TCP: Data Received - 519 Bytes [hwalrm1]
2017-12-11 00:44:28 - TCP: %FF,00000000B8F154F174FF48FF66FF8ABC8CE70000F8D500000000FDF2ECE100000000000000000000F895000000008AE700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000$[C][L] [hwalrm1]
2017-12-11 00:44:28 - Alarm: Envisalink Zone Timer Dump [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 1 (Zone 01) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 2 (Zone 02) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 3 (Zone 03) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 4 (Zone 04) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 5 (Zone 05) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 6 (Zone 06) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 7 (Zone 07) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 8 (Zone 08) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 9 (Zone 09) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 10 (Zone 10) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 11 (Zone 11) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 12 (Zone 12) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 13 (Zone 13) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 14 (Zone 14) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 15 (Zone 15) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 16 (Zone 16) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 17 (Zone 17) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 18 (Zone 18) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 19 (Zone 19) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 20 (Zone 20) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 21 (Zone 21) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 22 (Zone 22) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 23 (Zone 23) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 24 (Zone 24) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 25 (Zone 25) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 26 (Zone 26) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 27 (Zone 27) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 28 (Zone 28) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 29 (Zone 29) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 30 (Zone 30) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 31 (Zone 31) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 32 (Zone 32) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 33 (Zone 33) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 34 (Zone 34) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 35 (Zone 35) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 36 (Zone 36) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 37 (Zone 37) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 38 (Zone 38) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 39 (Zone 39) Closed [hwalrm1]
2017-12-11 00:44:28 - Alarm/ISY: Zone 40 (Zone 40) Closed [hwalrm1]
 

I have 11 devices on NodeLink, no issues. No one else has reported this yet. 5.0.11 was broken 5.0.11A seems to work.

 

Without an error message in a log I can't help since NodeLink itself didn't change.

 

Maybe this is something that's been broken for a while? I haven't changed Ademco code in a long time.

It was working Saturday.  Yesterday I did not look but went to 5.0.11a.  Then it did not work.

 

BUT overnight it started working.

 

My internet was NOT down as I tested that and I was posting here.

 

But could the Envisilink guys had some sort of issue it corrected during the night?   Or maybe they sent a firmware last night.

 

Starting to agree with you that this was all coincidental but I like to know why

I have no idea. Don't own an Ademco. If it's not in a log I'm blind.