ElkM1 Keypad Attribute

[ajkerley]

The problem

The "changed_by_keypad" attribute is always shown a "null" and does not define what keypad either by name or number was used.

What version of Home Assistant Core has the issue?

core-2023.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ElkM1

Link to integration documentation on our website

https://www.home-assistant.io/integrations/elkm1

Diagnostics information

home-assistant_elkm1_2023-05-16T22-47-30.520Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @gwww, @bdraco, mind taking a look at this issue as it has been labeled with an integration (elkm1) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `elkm1` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign elkm1` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

elkm1 documentation elkm1 source _{^{(message by IssueLinks)}}

[gwww]

No guarantees since you have something real funky going on with your ElkM1. There are many Invalid message errors in your log. Could be bad or outdated Ethernet on your Elk or could be bad serial. I'm reluctant to try and solve this one off issue when I see basic protocol error messages when communicating with your Elk.

What versions of the ElkM1 software are you running? What version of the Ethernet board are you running? Did you read the docs on the minimum ElkM1 version?

The log that would be more useful is the elkm1_lib log. See this post on the log levels that are useful. https://community.home-assistant.io/t/elk-m1-interface/4461/983

Side note: the log you included has more errors and warnings in it than any other log I've ever seen.

[ajkerley]

ElkRP is v2.0.40 Main Program Module is v2.0.40 M1G Control Module is v5.0.40 M1 Control Module is v5.0.40 EZ8 Control Module is v5.0.40 ElkComm Module is v2.0.2.2 ConvertDB Module is v1.4.12 ElkSafe Module is v1.1.10 ErrorDlg Module is v1.2.12

Using M1XEP via IP and Port 2601

I will see if I can get the additional logs

[gwww]

The version of the ElkM1 that you are running does not support everything, which is most likely the problem.

See https://www.home-assistant.io/integrations/elkm1#elkm1-version for versions supported.

[gwww]

I just noticed that the version of the panel in text does not match the picture. Please confirm.

If you are indeed running the version in the image, that is supported. In which case logs needed.

[ajkerley]

The text came from the ElkRP programing software "Help > About"

The only thing I am seeing in Log Viewer now is stuff like, I'll be able able to get more logs this evening after some one arms and leaves: 2023-06-07 14:43:19.495 DEBUG (MainThread) [elkm1_lib.discovery] discover: ('255.255.255.255', 2362) => b'XEPID' 2023-06-07 14:43:32.162 DEBUG (MainThread) [elkm1_lib.connection] got_data '16XK3043144070623110006F' 2023-06-07 14:54:36.758 DEBUG (MainThread) [elkm1_lib.connection] got_data '1BSD02041USER 041 00AB' 2023-06-07 14:54:36.758 DEBUG (MainThread) [elkm1_lib.connection] write_data '0Bsd02042005F' 2023-06-07 14:54:37.995 DEBUG (MainThread) [homeassistant.components.elkm1] Creating elk entities for <elkm1_lib.elk.Elk object at 0x7f4176056830>

My "alarm_control_panel.elkm1_area_1" attributes look like code_format: number changed_by: Mike K code_arm_required: true index: 1 is_exit: false timer1: 0 timer2: 0 armed_status: disarmed arm_up_state: not_ready_to_arm alarm_state: no_alarm_active changed_by_keypad: null changed_by_time: 2023-06-07T12:52:00+00:00 changed_by_id: 33 friendly_name: Office supported_features: 7

[ajkerley]

Updated debug log attached. alarm was armed at 1725hrs by user 38 from keypad 05

home-assistant_elkm1_2023-06-08T05-36-56.697Z.log

[ajkerley]

@gwww @bdraco just wanted to follow up on this

[gwww]

Haven’t forgotten but not a high priority.

[ajkerley]

No problem, just making sure that the files came through and the thread didn't get auto closed.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.