Skip to main content
Archived

This project has been archived by its maintainers, and is no longer receiving any updates.

license buy_me_a_coffee

aioxcom

This library is depricated and no longer maintained.

Please switch to using the pystuderxcom library, which has adds support for Udp and Serial and makes available async and sync classes.

Some minor class and function renaming is required when making this switch.


Python library for retrieving sensor information from Studer-Innotec devices. This component connects directly over the local network using the Studer xcom protocol.

The custom component is comfirmed to be compatible with:

  • Xtender XTH 8000-48, XTM 4000
  • Xcom-CAN (BSP connection to a third party BMS)
  • Xcom-LAN (which actually is a Xcom232i with a Moxy NPort 5110A)
  • BMS
  • RCC-03
  • VarioTrack

It should also be able to detect and handle

  • Xtender (any other XTH, XTS and XTM models)
  • VarioString
  • RCC-02

Disclaimer: this library is NOT created by Studer-Innotec, but is based on their documentation of the Xcom protocol. That documentation can be found on: Studer-Innotec Download Center -> Software and Updates -> Communication protocol Xcom-232i

Prerequisites

This device depends on having a Studer Xcom-LAN (i.e. an Xcom-232i and a Moxa ethernet gateway) acting as a Xcom client and connecting to this integration. For older systems this will be a separate component, for future systems Studer have indicated that LAN connection will become part of the Xtender range.

The Studer Xcom-LAN will be able to simultaneously send data to the Studer online portal as well as sending data to this integration.

Configuration steps:

  1. Download and install the Moxa DSU tool (Device Search Utility)

    • Open www.moxa.com in a browser
    • Select Support -> Software and Documentation
    • Choose NPort 5100A series (or whatever specific device you have)
    • Scroll down under 'Related Software, Firmware and Drivers' to find 'Device Search Utility'
    • Download and install the utility
  2. Locate the Moxa NPort device on the local network

    • Run the Moxa Device Search Utility

    • Press the 'Search' button and wait until the search finishes

    • The utility should display the found NPort device

    • Double click on the found device to open its configuration page

      dsu_search_results

  3. Configure the Moxa NPort device

    • In the Main Menu, select 'Operating Settings' -> Port 1

    • Verify that 'Operation Mode' is set to 'TCP Client'

    • Add the ip-address of your HomeAssistant as 'Destination IP address'

    • Set Delimeter 1 to '0d' and Enable

    • Set Delimeter 2 to '0a' and Enable

    • Set Delimeter Process to 'Strip Delimeter'

    • Press the 'Submit' button

    • Press 'Save/Restart'

      moxa_operating_settings

Usage

The library is available from PyPi using: pip install aioxcom

To read an infos or param or write to a param:

from aioxcom import XcomApiTcp, XcomDataset, XcomVoltage

dataset = await XcomDataset.create(XcomVoltage.AC240) # or use XcomVoltage.AC120
info_3023 = dataset.getByNr(3023, "xt")  # the "xt" part is optional but usefull for detecting mistakes
info_6001 = dataset.getByNr(6001, "bsp")
param_1107 = dataset.getByNr(1107, "xt")
dataset = None  # Release memory of the dataset

api = XcomApiTcp(4001)    # port number configured in Xcom-LAN/Moxa NPort
try:
    if not await api.start():
        logger.info(f"Did not connect to Xcom")
        return

    # Retrieve info #3023 from the first Xtender (Output power)
    value = await api.requestValue(info_3023, "XT1")    # xt address range is 101 to 109, or use "XT1" to "XT9"
    logger.info(f"XT1 3023: {value} {info_3023.unit} ({info_3023.name})")

    # Retrieve param #6001 from BSP (Nominal capacity)
    value = await api.requestValue(info_6001, "BSP")    # bsp address range is only 601, or use "BSP"
    logger.info(f"BSP 6001: {value} {info_6001.unit} ({info_6001.name})")

    # Update param 1107 on the first Xtender (Maximum current of AC source)
    value = 4.0    # 4 Ampere
    if await api.updateValue(param_1107, value, "XT1"):
        logger.info(f"XT1 1107 updated to {value} {param_1107.unit} ({param_1107.name})")

finally:
    await api.stop()

A complete list of param and infos numbers can be found in the source of this library in file src/aioxcom/xcom_datapoints_240v.json

A complete list of all available device families and their address range can be found in file src/aioxcom/xcom_families.py

Param writes to device RAM

When the value of a Studer param is changed via this library, these are written via Xcom to the affected device. Changes are stored in the device's RAM memory, not in its flash memory as you can only write to flash a limited number of times over its lifetime.

However, reading back the value from the entity will always be from flash. As a result, the change to the entity value is not visible in the RCC or remote console. You can only tell from the behavior of the PV system that the Studer param was indeed changed.

After a restart/reboot of the PV system the system will revert to the value from Flash. So you may want to periodically repeat the write of changed param values via an automation.

IMPORTANT:

Be very carefull in changing params marked as having level Expert, Installer or even Qualified Service Person. If you do not know what the effect of a Studer param change is, then do not change it.

Credits

Special thanks to the following people for providing the information this library is based on:

Metadata

Release files for aioxcom 2.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aioxcom 2.5.0
File Size Uploaded Provenance Actions
aioxcom-2.5.0.tar.gz 81.7 kB With provenance Details for aioxcom-2.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for aioxcom 2.5.0
File Interpreter ABI Platform Actions
aioxcom-2.5.0-py3-none-any.whl Python 3 none any Details for aioxcom-2.5.0-py3-none-any.whl

Total release size: 159.4 kB

Release files / aioxcom-2.5.0.tar.gz

Download URL aioxcom-2.5.0.tar.gz
Size 81.7 kB
Tags Source
SHA-256 checksum
How to use checksums
b592bcb21b3a6a9cf4459a0c5ae840702c6818aa27d8cc1f91cb3d55d7fb2ebf
BLAKE2b-256 checksum
How to use checksums
3f445f49a6c8f95d1167ed8e3ab7e9cdf407bc4002344ce8420678d4b6a5190b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2025.

Transparency log

Release files / aioxcom-2.5.0-py3-none-any.whl

Download URL aioxcom-2.5.0-py3-none-any.whl
Size 77.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1f76bbd9c6e622718dd523aa6eeac803fbb2ae144b7f536b9bdcaa2c36662e70
BLAKE2b-256 checksum
How to use checksums
3bd3d6c4a6bf652be73767787b9168d1bf808f00e76b1e6014a9ff635d131c70
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2025.

Transparency log

Security for aioxcom 2.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for aioxcom-2.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2025.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page