Errors

[7RDR7]

Hi, The following errors have begun to show up in my Homebridge UI logs after running flawlessly for months. They don't seem to be causing any issues, so more of an observation. BTW, thanks for the great plugin!

[7/31/2021, 10:42:47 AM] [Envisalink-Ademco] Command format invalid! command='%00,01,1C08,08,00,DISARMED Ready to Arm '

[7/30/2021, 8:02:55 PM] [Envisalink-Ademco] Command format invalid! command='%00,01,1C08,08,00,**'

[7/29/2021, 9:08:14 AM] [Envisalink-Ademco] Command format invalid! command='%00,01,0008,04,00,FAULT 04 MOTION

[7/28/2021, 9:54:38 PM] [Envisalink-Ademco] Command format invalid! command='%00,01,0008,04,00,FAULT 04 '

[7/28/2021, 12:59:17 PM] [Envisalink-Ademco] Command format invalid! command='%00,01,0008,02,00,FAULT 02 FRONT '

[haywirecoder]

Hi,

This is odd. According to the Envisalink documentation "All data is sent as hex ASCII codes. The format of packets from the Envisalink will be as follows %CC,DATA$ All packets are encapsulated within the %$ sentinels and it is guaranteed that these symbols will not appear within a packet. CC => 2 digit command code in HEX. DATA => Arbitrary data based on the individual command"

Base on your log, the $ sign is drop which is sign of data packet issue. My best advise is rebooting of Envisalink module...but depending if the information is re-sent it could be harmless. Let me know if this keep happening or cause some messages to be drop. I can add option for ignoring the sentinels, with the understanding that this could have unexpected result since it doesn't conform to the documentation of how this should operate. I will also keep an eye out on it in my logs.

[7RDR7]

Thanks for the analysis. It's still not causing any issues, so I'll reboot and and let you know if I make any progress on the cause.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[7RDR7]

Hey, it's still experiencing errors, but does not appear to be causing any issues, and we use it everyday. Therefore low priority.

[9/4/2021, 8:52:37 AM] [webostv] [Kitchen TV] TV setup finished, ready to control tv [9/4/2021, 9:23:22 AM] [webostv] [Kitchen TV] TV turned off! [9/4/2021, 9:23:38 AM] [webostv] [Kitchen TV] Disconnected from TV [9/4/2021, 9:23:43 AM] [webostv] [Kitchen TV] Starting TV alive polling [9/4/2021, 9:59:59 AM] [DysonPureCoolPlatform] NM7-US-HBA3712A - set Active to 0: {"fpwr":"OFF","fmod":"OFF","oson":"ON"} [9/4/2021, 10:09:59 AM] [Envisalink-Ademco] Command format invalid! command='%00,01,1C08,08,00,DISARMED Ready to Arm ' [9/4/2021, 10:28:09 AM] [Envisalink-Ademco] Command format invalid! command='%00,01,0008,04,00,FAULT 04 MOTION ' [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Connected to TV [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Got TV information [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] TV webOS version: 3.5 [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] TV turned on! [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] App launched, current appId: com.webos.app.hdmi2 [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Sound output changed. Current sound output: tv_speaker [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Subscribed to TV services [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Connected to remote pointer input socket [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] Setup finished [9/4/2021, 10:30:57 AM] [webostv] [Kitchen TV] TV setup finished, ready to control tv [9/4/2021, 11:30:29 AM] [Envisalink-Ademco] Command format invalid! command='%00,01,0008,04,00,FAULT 04 MOTION ' [9/4/2021, 1:19:57 PM] [Envisalink-Ademco] Command format invalid! command='%00,01,1C08,08,00,****DISAR' [9/4/2021, 5:35:08 PM] [webostv] [Kitchen TV] Pixel refresher started! [9/4/2021, 5:41:05 PM] [webostv] [Kitchen TV] TV turned off! [9/4/2021, 5:41:05 PM] [webostv] [Kitchen TV] Disconnected from TV

[haywirecoder]

Hi, Still very odd, it's clear from the log the data stream format is missing the required tokens, so the plug-in is correct to reject it as a valid data stream. If it is not having ill effect, the next data stream must have the correct format and updates. I will changes "Error" to a "Warning" in the next release. Closing this issue, feel free to re-open if you have more information or it begins causing issues.