Bug in Envisalink4 firmware 121 ?

[pos42]

Hi

I see strange behaviour after upgrade...

I have had ver 111 for a long time and only seen one odd behaviour. The one with the socket lock-up solved in version 121.

Now….
After Upgrading from 111 to 121 I see two strange things.


# 1
After a forced Envisalink reboot in the web gui of Envisalink…
when you try to connect, the Envisalink will not send a request for password. Looking into it, it seems Envisalink card send null (well, at least something invisible) back which makes the login fail. I track this but only see "Dec 19 20:15:30 DSCengine We received initial data from EnvisaLink after session setup, but it was not an auth request. We got: “. I.e I print what I got back, but it is not shown. This happens the second time I connect as well. The third time I try to connect I got a request for password and can login. I m*a*y have rebooted the envisalink card twice before trying to log in. Don’t know if that has anything to do with two failed connection attempts later after the reboots.

Why do this happen?


# 2
I have two active partitions on my DSC1616. Why did I get the following from the Envisalink after test disarming partition 1 and 2.
(I have a 5501 pad and Envisalink only)
Dec 19 20:21:14 DSCengine Partition is Busy - The partition is busy (another keypad is programming or an installer is programming) - Partition: 5
Dec 19 20:21:15 DSCengine Partition is Busy - The partition is busy (another keypad is programming or an installer is programming) - Partition: 6
Dec 19 20:21:17 DSCengine Partition is Busy - The partition is busy (another keypad is programming or an installer is programming) - Partition: 7
Dec 19 20:21:19 DSCengine Partition is Busy - The partition is busy (another keypad is programming or an installer is programming) - Partition: 8

Did never ever see this before.


Has something happened between version 111 and 121 that can explain this? Any clues?

PS
Hopefully the socket problem is gone though… And I do not at the moment see any actual problems caused by this. (y e t).


Tnx
Peo

[K-Man]

1.1.121 is the current release revision. There has to be more than 5,000 customers with that version and no issues at all reported.

[pos42]

First...
The socket close was annoying. (that was the main reason why I upgraded from 111 to 121)


Second…
And it seems every disconnect and connect is successful after the first failed onces (the onces who failed directly after the Envisalink reboot)
And the partition buzy on partitions I dont have... My DSC PC1616 only has TWO partitions. This is really fishy. But I have not seen any damage caused.



Really strange to say partitions are buzy that does not exist in the DSC alarm. That is a new message after the upgrade. But as said have just received the codes saying so through the API.

As said above, I have not seen any damage caused by my findings. Therefor I for now sees it more important to see if the socket problem is gone.

Thoughts....
Could it be so that envisalink send out something not seen during a hard reboot through the GUI? I have not clicked reboot in the gui for a very long time. Therefor that particular behaviour could have been there before. But after that I never see it again even though I stop my client service and connect again. or stop it so envisa reboot by itself later on. It seems to only be seen when I actively have rebooted it. But not an issue. Just wanted to mention it. It could eventually be a bug, that has no impact...

And when it comes to the info about partitions I do not have. Could it eventually be so that it happened before, but envisalink now send them out to me? Just asking... This is also only seen after the envisalink has been rebooted through the GUI. no impact from this either...

Peo

[shawontx]

How do you upgrade? I am still running 01.01.113A for EVL4.

[GrandWizard]

How do you upgrade? I am still running 01.01.113A for EVL4.

Email Eyezon tech support and ask for an upgrade.

[pos42]

1.1.121 is the current release revision. There has to be more than 5,000 customers with that version and no issues at all reported.

Hi @K-Man

I see what you say. But I still think a new bug could eventually have been introduced. How should I act to have the firmware writer to have a look at it. The release I used before 121 was perfect. except the disconnects. The disconnects from the Envisalink side is gone with 121 which is really good.

However. When I drop the connection to the envisalink and reboot my home automation this is the conversation to the envisalink during connection directly after the home automation has rebooted. These errors did not show up in the release I used before 121. Ok more than 5000 uses it. But it does not mean it cannot have new bugs. After these initial boot errors it works as it should. So it is self healing. But even so. This is NEW with 121 and I think it should not be there.

Code: Select all

Jan 29 22:41:23 DSCengine Session start
Jan 29 22:41:23 DSCengine Contacting server...
Jan 29 22:41:23 DSCengine Request for password, sent after socket setup # API CODE:5053CD#015
Jan 29 22:41:23 DSCengine Password sent
Jan 29 22:41:23 DSCengine Login interaction - Password Correct, session established # API CODE:5000052A#015#0125051CB#015
Jan 29 22:41:31 DSCengine Trouble LED: ON - Partition: 1
Jan 29 22:41:33 DSCengine Trouble LED: ON - Partition: 2
Jan 29 22:41:36 DSCengine Trouble LED: ON - Partition: 3
Jan 29 22:41:38 DSCengine Trouble LED: ON - Partition: 4
Jan 29 22:41:41 DSCengine Verbose Trouble Status - Loss of Time:0 Sensor/Zone Low Battery:0 Sensor/Zone Tamper:0 Sensor/Zone Fault:0 Failure to Communicate:0 Telephone Line Fault:0 AC Power Lost:0 Service is Required:1
Jan 29 22:41:41 DSCengine Partition Ready - Partition: 1
Jan 29 22:41:59 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Jan 29 22:42:04 DSCengine Trouble LED: OFF - Partition: 1
Jan 29 22:42:06 DSCengine Trouble LED: OFF - Partition: 2
Jan 29 22:42:07 DSCengine Trouble LED: OFF - Partition: 3
Jan 29 22:42:09 DSCengine Trouble LED: OFF - Partition: 4
Jan 29 22:42:30 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Jan 29 22:43:06 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...

Or do you think I have missed something here? If so, please let me know...

Tnx in advance
/Peo

[pos42]

Hi again.

I continue to get problems with version 121 of Envisalink firmware that was not there before version 121.

What person or entity should I contact to adress this? If I ask for a downgrade I get the random disconnects back that are gone now.. It is like choosing between plage or kolera.

This is what I get in random (once a week or so) now instead of disconnects...
(the system continues to work though...)

Code: Select all

Feb  6 21:23:55 DSCengine Zone: 003 ZPIRLivingR: breached
Feb  6 21:23:55 DSCengine Partition Not Ready - Partition: 1
Feb  6 21:23:58 DSCengine Zone: 003 ZPIRLivingR: restored
Feb  6 21:23:58 DSCengine Partition Ready - Partition: 1
Feb  6 21:24:01 DSCengine Zone: 002 ZPIRKitchen: breached
Feb  6 21:24:01 DSCengine Partition Not Ready - Partition: 1
Feb  6 21:24:01 DSCengine Trouble LED: ON - Partition: 1
Feb  6 21:24:03 DSCengine Trouble LED: ON - Partition: 2
Feb  6 21:24:04 DSCengine Trouble LED: ON - Partition: 3
Feb  6 21:24:07 DSCengine Trouble LED: ON - Partition: 4
Feb  6 21:24:09 DSCengine Zone: 003 ZPIRLivingR: breached
Feb  6 21:24:09 DSCengine Zone: 002 ZPIRKitchen: restored
Feb  6 21:24:09 DSCengine Zone: 003 ZPIRLivingR: restored
Feb  6 21:24:09 DSCengine Partition Ready - Partition: 1
Feb  6 21:24:09 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:24:09 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:24:39 DSCengine Trouble LED: OFF - Partition: 1
Feb  6 21:24:40 DSCengine Trouble LED: OFF - Partition: 2
Feb  6 21:24:42 DSCengine Trouble LED: OFF - Partition: 3
Feb  6 21:24:44 DSCengine Trouble LED: OFF - Partition: 4
Feb  6 21:24:46 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:24:54 DSCengine Trouble LED: ON - Partition: 1
Feb  6 21:24:56 DSCengine Trouble LED: ON - Partition: 2
Feb  6 21:24:58 DSCengine Trouble LED: ON - Partition: 3
Feb  6 21:25:01 DSCengine Trouble LED: ON - Partition: 4
Feb  6 21:25:18 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:25:18 DSCengine Verbose Trouble Status - Loss of Time:0 Sensor/Zone Low Battery:0 Sensor/Zone Tamper:0 Sensor/Zone Fault:0 Failure to Communicate:0 Telephone Line Fault:0 AC Power Lost:0 Service is Required:1
Feb  6 21:25:18 DSCengine Partition Ready - Partition: 1
Feb  6 21:25:35 DSCengine Trouble LED: OFF - Partition: 1
Feb  6 21:25:36 DSCengine Trouble LED: OFF - Partition: 2
Feb  6 21:25:38 DSCengine Trouble LED: OFF - Partition: 3
Feb  6 21:25:40 DSCengine Trouble LED: OFF - Partition: 4
Feb  6 21:25:46 DSCengine Zone: 002 ZPIRKitchen: breached
Feb  6 21:25:46 DSCengine Partition Not Ready - Partition: 1
Feb  6 21:25:48 DSCengine Zone: 002 ZPIRKitchen: restored
Feb  6 21:25:48 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:25:49 DSCengine Partition Ready - Partition: 1
Feb  6 21:26:25 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:27:01 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...
Feb  6 21:27:32 DSCengine Zone: 002 ZPIRKitchen: breached
Feb  6 21:27:32 DSCengine Poll response received - TCP session to EnvisaLink is active. Good...

Tnx
/Peo