Please wait, content is loading

SmartAPEX network automation gateway APX-MIP-P

MINI IP Gateway

PoE-powered Ethernet gateway for SmartAPEX CAN devices, Modbus TCP-to-RTU and supported RS485 curtain motors. One shared hardware unit, three mutually exclusive firmware roles.

3 firmware roles PoE 48V or micro-USB 5VDC power CAN-BUS + RS485
SmartAPEX APX-MIP-P, MINI IP Gateway, front view Manual render shown · real studio photo pending
3

Firmware roles

48 V

Standard PoE input

32

Modbus devices*

CAN / RS485

Bus interfaces

* Advanced capacity depends on RS485 wiring and polling interval.

Where it fits

One gateway, four practical jobs in the panel.

Pick the firmware role that matches what’s actually being connected.

CAN-to-Ethernet for APEX

Bridges SmartAPEX CAN-BUS devices to Ethernet for discovery, configuration and control — the Standard V40 role.

HVAC integration

Connects HVAC systems such as Daikin, Intesis, CoolMaster and similar gateways over Modbus.

Modbus power meters

Adds RS485 Modbus energy / power meters to the network through the Modbus Bridge role.

RS485 electric curtains

Controls supported RS485 curtain motors through the MiCURTAIN Bridge role and QuickApp.

Select the correct firmware role

One gateway, three mutually exclusive jobs.

The hardware is shared by three firmware roles, but only one role can run at a time. Installing a new role replaces the current role.

Role 01

Standard V40

Normal SmartAPEX CAN, built-in Modbus/HVAC, templates and full gateway services.

Use when: the installation needs normal SmartAPEX CAN discovery, configuration, bindings, built-in Modbus points, HVAC mapping or full gateway services.
Role 02

Modbus Bridge

Transparent Modbus TCP-to-RTU for Fibaro/Yubii or another Modbus TCP client.

Use when: the external client owns the Modbus register logic and needs transparent TCP-to-RTU access.
Role 03

MiCURTAIN Bridge

Control supported RS485 curtain motors through the supplied QuickApp.

Use when: connected RS485 devices are supported curtain motors and Fibaro/Yubii must control Up, Down, Stop and target position.
Installation requirementFirmware roleCurrent package
Normal SmartAPEX CAN, built-in Modbus/HVAC and full gateway servicesStandard Mini IP V40MINI_IP_vX.XXX.bin
External Modbus TCP client to RS485 meters or slavesMini IP Modbus BridgeMINI_IP_MODBUS_BRIDGE_vX.XXX.bin
Supported RS485 curtain motors controlled by Fibaro/YubiiMini IP MiCURTAIN BridgeMINI_IP_CURTAIN_vX.XXX.bin

Critical installer warning.

  • Do not install Modbus Bridge when the site needs normal SmartAPEX CAN, HVAC, templates or SmartAPEX TCP services.
  • Do not install Standard Mini IP when a Fibaro QuickApp expects a transparent Modbus TCP gateway on port 1502.
  • Do not install MiCURTAIN firmware for a Modbus device — MiCURTAIN is a proprietary curtain-motor protocol.
  • Use only the current approved MiCURTAIN field release; do not deploy test or unapproved builds.
  • Upload the encrypted package from the update-generator updates folder, not the raw STM32CubeIDE Release .bin.

Role 01

Standard SmartAPEX Mini IP V40.

The normal Mini IP gateway role for SmartAPEX CAN devices, built-in Modbus/HVAC configuration and standard TCP integration.

Project: SmartAPEX-MiniIP-V40  ·  Package: MINI_IP_vX.XXX.bin
Function areaStandard V40 capability
Ethernet gatewayNormal SmartAPEX TCP/IP services and web configuration.
CAN devicesDiscover, configure, refresh and bind compatible SmartAPEX CAN devices.
Modbus RTUBuilt-in bus, device and point configuration; register logic stays in Mini IP.
HVAC / templatesBuilt-in HVAC mapping, device templates and point configuration.
MaintenanceNetwork, diagnostics, reset and firmware update pages.

Do not use this role when

  • A third-party client expects a transparent Modbus TCP-to-RTU gateway.
  • A Fibaro Eastron QuickApp must send its own Modbus TCP requests directly to an RS485 meter.
  • The installation uses the proprietary MiCURTAIN motor protocol.

Important distinction. The Standard V40 Modbus section manages its own devices and points. It is not the same product role as the transparent Modbus Bridge and does not expose the same port-1502 workflow.

Role 02

SmartAPEX Mini IP Modbus Bridge.

A transparent Modbus TCP-to-RTU bridge for Fibaro/Yubii or another standard Modbus TCP client.

Package: MINI_IP_MODBUS_BRIDGE_vX.XXX.bin
Modbus TCP client
APX-MIP-P / port 1502
RS485 Modbus RTU slaves
  • Receives a Modbus TCP request and preserves its transaction ID.
  • Converts Unit ID and PDU to Modbus RTU on RS485.
  • Validates the RTU response and returns a Modbus TCP response.
  • Serializes RS485 requests so only one RTU transaction is active at a time.
  • Does not decode Eastron values — register interpretation remains in the external client or QuickApp.
SettingDefault
NetworkDHCP enabled
Modbus TCPPort 1502
RS4859600, 8N1
RTU timeout3000 ms
TCP clients1 simultaneous

Fibaro / Yubii settings

ParameterExampleMeaning
Gateway_IPMini IP bridge addressTarget gateway IP.
Gateway_Port1502Transparent Modbus TCP port.
Modbus_AddressMeter slave IDRS485 Unit ID selected by the client.
Read_Every30 s or slowerRecommended polling interval.

Capacity planning. Recommended: 1 to 8 meters. Supported: up to 16 with suitable polling intervals. Advanced installations may reach 32 only with correct RS485 wiring, termination, biasing and slower polling.

Role 03

SmartAPEX Mini IP MiCURTAIN Bridge.

A dedicated RS485 role for supported proprietary curtain motors controlled through the SmartAPEX QuickApp.

Project: MiCURTAIN  ·  Package: MINI_IP_CURTAIN_vX.XXX.bin
SettingDefault / range
NetworkDHCP enabled
RS4852400, 8N1
Motor ID0–99 (0 = group address)
Channel1–16
Fibaro QuickApp settingUse
Gateway_IPDevice network target.
Motor_IDSelects the motor.
ChannelSelects the motor channel (1–16).
ReverseReverses open/close direction — on only if needed.

Do not use this role when

  • The RS485 device is Modbus RTU.
  • The site needs normal SmartAPEX CAN or HVAC functions.
  • A generic Modbus TCP client must connect on port 1502.

Network discovery & role switching

Use the same protected update process for every role.

Use the same protected web update process for all roles, then verify the installed role after reboot.

Switching firmware roles

1
RecordSave the current IP and any settings required after conversion.
2
UpdateOpen /update, select the encrypted package and start the update.
3
RebootKeep power and Ethernet connected until the unit restarts.
4
VerifyOpen /version.cgi and confirm the new role and firmware version.
5
ReconfigureEnter role-specific settings and update controller parameters.

Network discovery

  • After factory reset, current firmware packages use DHCP by default.
  • Find the assigned IP with SmartAPEX Finder, the router/DHCP client list or supported discovery information.
  • Configure a static address on the Network page only after recording the current address.
  • If the saved static address is outside the installer subnet, reconnect correctly or follow the documented reset procedure.
RoleVersionEncrypted package
Standard Mini IP V40vX.XXXMINI_IP_vX.XXX.bin
Modbus BridgevX.XXXMINI_IP_MODBUS_BRIDGE_vX.XXX.bin
MiCURTAIN BridgevX.XXXMINI_IP_CURTAIN_vX.XXX.bin

Configuration does not guarantee migration. Standard CAN or Modbus templates are not a Modbus Bridge meter list, and MiCURTAIN motor settings are not Standard V40 records. Verify or re-enter role-specific settings after conversion. Use the encrypted packages from the update-generator updates folder — do not upload the raw STM32CubeIDE Release .bin through the web updater.

Specifications

Technical product specifications.

Model numberAPX-MIP-P
Power input48 V PoE (standard) or 5 VDC via the onboard micro-USB port
Power marking5 W
ConnectionsCAN-BUS, RS485 / MODBUS
CommunicationEthernet TCP/IP
Max. Modbus devices32* — see capacity planning above
Operating temperature-10 to 60 °C
Humidity5% to 95% non-condensing
Weight0.15 kg
MountingWall / enclosure mounting

LED status

IndicatorStatus
LKON: connected to the host.
CANBUSCAN-BUS data communication.
MODBUSModbus data communication.
PWFast blinking: not connected to the network.
PWSlow blinking: Ethernet connected; attempting to obtain an IP address.
PWVery slow blinking: module connected with a valid IP address.

Firmware role warning. The hardware is shared by three firmware roles, but only one role can run at a time. Always verify the role and package before updating.

Product manual

Install and commission with the exact technical guide.

Covers all three firmware roles, factory defaults, HTTP API references, network discovery, role switching and diagnostics — the authoritative source for anything electrical or firmware-related.