Concord232 binary_sensor.unnamed_device_x [SOLVED]

So I managed to (partially) program our GE Concord4 alarm. The first item "learned’ was the front door. Next the back door and then the garage door etc. Then windows . . .

Each device, in Home Assistant “States” shows as binary_sensor.unnamed_device for the first device and subsequent devices binary_sensor.unnamed_device_X where X is the next digit.

My problem is when I try to set up automations for, example, binary_sensor.unnamed_device_6 - it always comes out the Front Door.

My customize.yaml DOES differentiate between each one correctly because I appended the “_X” accordingly. This is the one for the Front Door:

binary_sensor.unnamed_device:
  friendly_name: Alarm - Front Door
  device_class: door

Any suggestions as to why everything is the Front Door (binary_sensor.unnamed_device)?

@ConcordGE

Clear down the panel and start again. It looks like your panel was partially configured already.

Does that mean clear all the programming on the concord4? (I’m not familiar with alarm terms - LOL) If you recall (in the other thread) my panel had zero zones and zero anything when I first started on this project.

Had the panel ever been configured before.

What does the Concord summary command return in the server.

What does the server report when you issue the command concord232_client summary

I haven’t edited the last two:

concord232_client summary
+------+------+--------+--------+-----------+
| Zone | Name | Bypass | Status |    Type   |
+------+------+--------+--------+-----------+
|  1   |      | Normal | Normal | Hardwired |
|  2   |      | Normal | Normal | Hardwired |
|  3   |      | Normal | Normal |  Unknown  |
|  4   |      | Normal | Normal |  Unknown  |
+------+------+--------+--------+-----------+
+-----------+-------+----------+-------+
| Partition | Zones |  Status  | Level |
+-----------+-------+----------+-------+
|     1     |   3   | Disarmed |  Off  |
+-----------+-------+----------+-------+
sudo concordctl
concordctl:1> zone
                      Zone Name | Id |Par|Typ| Grp|Trp|Byp|Tro|Alr|Flt|Last Changed
--------------------------------+----+---+---+----+---+---+---+---+---|------------
               ENTRY ENTRY DOOR |  1 | 1 | 0 | 10 |   |   |   |   |   |
                      REAR DOOR |  2 | 1 | 0 | 10 |   |   |   |   |   |
                    GARAGE DOOR |  4 | 1 | 0 | 10 |   |   |   |   |   |
              DOWNSTAIRS WINDOW |  5 | 1 | 0 | 13 |   |   |   |   |   |

Had to delete a zone. . . .

It looks like when you type

concord232_client summary

at the command line your client is not picking up your sensor names.

Ideas? Suggestions? Need any debugging from me?

You need to run the server as a system daemon. Do you know how to set up a service daemon for your server.

I followed the directions In the readme here

sudo systemctl status concord232_server.service
● concord232_server.service - Concord4 concord232_server
   Loaded: loaded (/lib/systemd/system/concord232_server.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-06-19 21:31:04 UTC; 1 day 23h ago
 Main PID: 1338 (concord232_serv)
    Tasks: 2 (limit: 1055)
   CGroup: /system.slice/concord232_server.service
           └─1338 /usr/bin/python3 /usr/local/bin/concord232_server --serial /dev/ttyUSB0

Jun 21 20:17:07 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:07] "GET /zones HTTP/1.1" 200
Jun 21 20:17:16 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:16] "GET /partitions HTTP/1.1"
Jun 21 20:17:18 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:18] "GET /zones HTTP/1.1" 200
Jun 21 20:17:27 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:27] "GET /partitions HTTP/1.1"
Jun 21 20:17:29 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:29] "GET /zones HTTP/1.1" 200
Jun 21 20:17:38 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:38] "GET /partitions HTTP/1.1"
Jun 21 20:17:40 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:40] "GET /zones HTTP/1.1" 200
Jun 21 20:17:49 starpower concord232_server[1338]: 10.xx.xx.xxx - - [21/Jun/2019 20:17:49] "GET /partitions HTTP/1.1"
Jun 21 20:20:03 starpower concord232_server[1338]: 127.0.0.1 - - [21/Jun/2019 20:20:03] "GET /zones HTTP/1.1" 200 -
Jun 21 20:20:03 starpower concord232_server[1338]: 127.0.0.1 - - [21/Jun/2019 20:20:03] "GET /partitions HTTP/1.1" 200

Your service daemon is running fine.

Ok. So what is the output when you type

concord232_client summary

at the command line

All you need to do is power down your Raspberry Pi and power down your Concord panel. As soon as you power up the panel and power up your Raspberry Pi the concord server should pick up all your sensor names as you have defined them from the panel,

Using this method you won’t need to individually name each sensor in the concord platform in the configuration.yaml as they will be auto discovered.

Funny how a reboot fixes everything. . . . (Reminds me of “The IT Crowd”)

The names are now as I would expect.

Thanks again!

And remember if you add any additional sensors to your panel in the future follow the same procedure. It saves messing with the HA and the concord platform.

It’s all so easy when you know how :bulb:

Remember that famous line where the guy fixed an engine by tapping the side of it with a spanner and charged the customer $500. Outraged the customer asked him to justify his costs. His answer was “50 cent for the tap on the engine and $499.50 for spending years of his life learning exactly where it needed to be tapped”.

Enjoy the setup :ok_hand:

wait…where did this come from??

the only commands I’ve got (that I know of ) are concord232_client and concord232_server. Both on the concord232 server box (an rpi3b) physically plugged into the serial port on the concord automation module.

there’s no concordxxx anything that comes up on the homeassistant box with the concord232 integration installed on it.

OK, found it.

Is this something that can be run in addition or as a supplemental toolset to the concord232? or are they mutually exclusive?

I haven’t looked at any depth yet, but does the concordd have to be run on the rpi3b that is physically connected to the concord automation panel?

thanks!