Foxtrot2 packages

teco-cloud

Q: Is it the same cloud of SmartFox PLC?
A: Yes, it is.

Q: How can we add foxtrot2 PLC on this cloud, and if we use it, what is the difference between it and the TecoRoute service?
A: You can manage your Teco Cloud services using the SmartFox portal. You can register for free, but currently only one PLC can be registered under one free account.
The difference between the TecoRoute service and the Teco Cloud lies mainly in the communication protocol.
Teco Cloud uses websocket-based message routing, offering better performance and management. TecoRoute service is implemented directly in the PLC application, while the Teco Cloud service runs as a standalone process in the PLC’s Linux system. Therefore, the Teco Cloud package acts as a connector with the ability to route various communications from the PLC.

Q: What is the added value we will have if we use SFOXAPP and SFOXRAW with foxtrot2?
A: The service options in the Teco Cloud package allow you to enable or disable specific communication protocols and service routing to the Cloud. Some protocols are publicly documented, others are not. The protocols depend on the client on the other side of the message routing.
PLCCOMS is a raw text protocol as you know it.
SMARTHOME is a specific protocol we use with our server to implement smart home services (currently Google Home).
SFOXAPP and SFOXRAW are used by our smart home applications such as app.smartfox.cloud.

Q: If we use it, it will help us in any way to share data between smartfox PLCs and foxtrot2, or will it not be used for this reason?
A: No, it is not intended for that purpose.

Q: How does it help us if we use it with plccoms?
A: If you want to implement your own application based on one of the supported protocols and use Teco Cloud for remote access to your PLC, documentation for the client-side connection to Teco Cloud is available upon request.

teco-smarthome

Q: Is it possible to integrate with Google Nest and Google Home using this package with teco-cloud, or is it still not ready yet?
A: The teco-smarthome package implements a websocket server that allows communication with clients via various selectable protocols during connection establishment. It is a better alternative to PlcComS — essentially a wrapper around it — with standard connection handling and JSON-based messaging. You can access the server within your local network if enabled, or via localhost when limited to the Teco Cloud client.
In combination with the teco-cloud package, it is used to implement Google Home and Google Nest integration.
We are Google Home certified, so you can find the official Tecomat service in the Google Home app.
To use it, you must:

1. Use iControlLib-supported function blocks in your PLC program.
2. Enable the teco-smarthome package.
3. Connect the PLC to the Teco Cloud with your account using the teco-cloud package.
4. Add the Tecomat service in your Google Home app and log in with your Teco Cloud account.

The solution is fully functional, but currently used by only a few users, so we have not promoted it widely yet due to limited feedback.

Q: Do you have an Alexa skill for controlling the functions that are programmed on the project using iControlLib?
A: No, we do not have an Alexa skill, and we are not planning one at the moment.

Q: Does this package allow me to integrate with other services or just with Google and Amazon?
A: Currently, it is a solution only for Google Home — and, of course, for our own applications.

Q: If the answer to the previous question was yes, do you have a document for this usage explaining more about it?
A: Documentation for all smart home features is available in the iControlLib manual.

teco-homebridge

Q: Is it ready to use with Apple Home, or is it still under development?
A: It’s hard to say precisely. We use the public open-source project Homebridge for integration. Currently, the package uses an older version of this project, which may contain bugs already fixed in newer versions. However, newer versions do not run reliably in our PLC environment, as they use the Node.js framework, which is not ideal for the PLC’s limited performance.
Therefore, the package is not actively maintained, but our customers are still using it. Some report that it works fine, while others experience issues.

Q: As I can see, we can add the same PLC to 4 different Apple accounts. Is it correct?
A: The limitation of the bridge is that it can simulate only up to 100 devices at once. If you need more, you can create additional bridge instances — up to four in total. You can assign different groups of devices to each instance. If you want to add each bridge instance to a different Apple account, you can do so.

Q: To use it, we must enable the PLCOMS server on the PLC. Am I right?
A: Yes, that’s correct.

A: The best solution for smart home integration today would be the implementation of the new Matter protocol, which is currently the most promising option to unify all platforms under a single standard.
We are currently in the research and testing phase of this solution. Our goal is to support this protocol in our PLCs to implement a bridge solution, which would be the most sustainable and future-proof approach for long-term maintenance.
However, we cannot guarantee the future success or timeline of the development and implementation of Matter protocol support at this stage.