Is API and MCP access in your Crestron scope?

Best Practice series, part 1.

Eighteen months after handover, the client wants something new connected to the control system. In an office it might be the room booking system. In a university it might be the timetabling system, and in a home it might be the alarm or a new voice assistant. The control system already knows most of what they need, and the programming works. Then the quote comes back, and a good part of it is reprogramming.

This happens because most custom Crestron programs are written with one way in. The touch panels and keypads talk to the processor, and nothing else was planned for. When a new system needs to read room status or send a command, the programmer has to go back into the code, work out what to expose, decide how the other system should connect, test it and recommission. That is billable time, and it repeats with every new system that comes along.

What API access means here

An API is a documented way for other software to talk to the control system. On a Crestron installation that could mean asking which rooms are occupied, setting a scene, reading a temperature or receiving an event when something changes. The important word is documented. Another developer, possibly years later and possibly from a different company, should be able to use it without reading the original program.

Plenty of programmers do this well when asked. The trouble is that it often isn’t asked for, so it isn’t priced, and a programmer working to a fixed quote has no reason to add it.

Why MCP is the next question

MCP, the Model Context Protocol, is an open standard that lets AI assistants and agents use outside systems through a defined set of tools. It has quickly become the usual way to connect the main AI assistants to business software. In an office or on a campus, that could be an assistant that books a meeting room and has it set up before people arrive. At home, it could be asking an assistant in plain language to set the house up for the evening.

MCP doesn’t replace an API. It sits on top of one. If the control system already has a good API, adding MCP is a small piece of work. If it doesn’t, the API has to be built first and you are back to reprogramming. Your clients may not be asking for AI access to their systems yet, but on a system expected to run for ten years or more it is sensible to assume they will.

The cost of adding it later

At the scoping stage, an API is a design decision. The programmer structures the code knowing other systems will connect, and the extra cost is usually modest. After handover it becomes a retrofit. Someone has to understand code they may not have written, find the signals worth exposing, add a way in and make sure nothing that already works has broken. If the original programmer has moved on, the new one starts by learning the old program, and you pay for that as well.

There is also a dependence problem. If the only person who can connect a new system is the person who wrote the code, every future change goes through them, at their price and when they are available.

The security side

An API added in a hurry is often a TCP port opened on the processor that accepts commands from anything on the network, with no authentication and no record of who sent what. It works, and it is exactly the kind of thing that turns up later in a security review. An API planned from the start can have authentication and logging designed in, and someone is clearly responsible for it.

Questions to put in your scope

If you write scopes or tenders for Crestron work, these are worth including:

  • Will the system have an API that other software can use, and what will it cover?
  • Will the API be documented, and will that documentation be handed over with the project?
  • How will other systems authenticate, and can their access be limited or revoked?
  • Who owns the code and the API documentation at handover?
  • Is MCP access included, or at least planned so it can be added without reprogramming?

A programmer who raises these before you do is thinking about how the system will be used after they leave site. If yours hasn’t, ask them, and ask for the answers in writing.

I’m Neil Silver at LCD. We have been writing secure APIs into audio visual scopes and projects for over 10 years, and I’m happy to talk through a scope if it would help.

Password Management in AV Projects

Password management is a challenge within an audio-visual (AV) project, just as it is for individual households and businesses. AV integrators use default admin passwords to simplify the hardware installation and credential management. But new infrastructure security laws are on the horizon, requiring AV integrators and installers to be more careful with privileged passwords. 

On January 1, 2020, California implemented legislation through Senate Bill 327 that requires a unique preprogrammed password for each device. The UK is working on similar legislation called The Product Security and Telecommunications Infrastructure (PSTI) Bill that will take effect in 2022. Breaking these laws has significant penalties. So, AV integrators should pay attention. 

Unique Password Challenges for AV Integrators 

The new regulations mean that AV Integrators need to make password change management an integral part of the project planning. Integrators and installers have to set up unique passwords and have a reliable way to manage the individual passwords for subsequent administration of the controller boxes and connected AV devices. 

Generally, an installer is the first person to touch an AV controller. But after the setup, the installer should not have visibility of the newly set password. So, AV integrators need a method to set passwords securely for multiple devices. 

But multiple unique passwords create a scalability problem. When AV integrators connect to the hardware remotely for maintenance, they have to factory reset the units and start with default passwords. It can complicate hardware maintenance and become a bottleneck. 

Our approach for More Efficient Password Management 

At Lighting Control, we set up a complex common password for all devices during the commissioning phase of an AV project. We can work faster without dealing with unique passwords at this stage. Then, at the end of the commissioning process, we use scripting tools to improve the security of the systems and add multiple user accounts. 

But if the scripting tools use plain text configuration files, the control passwords and IP configurations are easily accessible. It can become a potential security risk. So, we found that the best solution is to use PowerShell scripts with Active Directory (AD) accounts. As a result, the passwords are encrypted. It ensures that installers and users can run the scripts without accessing the credentials directly. 

We hope our password management best practices help you with your AV projects. If you are interested in our AV products and AV consultancy services, please feel free to contact us today. 

Neil Silver Crestron CSP

Neil Silver

Lead Developer LCD – Crestron Programmer , CSP

Managing the Development and Custom Programming Teams on a day to day basis and responsible for Product Design and Project Oversight.

Select currency
GBP Pound sterling