Filename: tcpdu_1_25.bin (1.4 MB)
Access-Control-Allow-Origin: *
for HTTP responses with dynamic values (/api/v1/read/status/
)./#/?signIn=user
when the Automatic sign in function is enabled.$
for user input, changed the backup filename to include more information, fixed some error messages, removed limit for setting on/off delay (was available only for OUT/VAR), fixed saving Network form (when changing from DHCP to static), added verification after updating FW on the page (might alert if the page is not available after update, so can update again in UI), fixed refreshing PM and CO2 values in I2C and 1-Wire page./api/v1/save/
and /api/v1/read/
).Filename: tcpdu_1_23.bin (1.4 MB)
Filename: tcpdu_1_22.bin (1.4 MB)
event
with a value for the mode option).Filename: tcpdu_1_19.bin (1.4 MB)
Filename: tcpdu_1_16.bin (1.4 MB)
reboot, on, off
, and the ability to send commands as in HTTP queries after using the cmd
prefix, e.g. 1234:cmd:out=out1
.iDValue1
and iDValue2
.Filename: tcpdu_1_10b.bin (1.3 MB)
An application that simplifies work with tinycontrol devices. It includes functions for finding them in the local network (Discovery function) and updating the firmware.
Integration allows you to use readings from tinycontrol devices and control their outputs inside Home Assistant. The current version includes support for LK4.0, LK3.5+, LK3.0, LK2.5, LK2.0, tcPDU and IP Power Socket V1/V2.
Currently, you need to install it as a custom integration, i.e. copy the integration files to the config/custom_components folder in Home Assistant (details in README.md).
We add devices using the Home Assistant UI, providing access data to the device (host, port, optionally username and password).
By default, added devices only have a few entities enabled, e.g. board temperature and voltage. The remaining entities can be turned on independently in the UI at your discretion. Entity availability varies by device.
After you update your device software, you may need to reload the integrations for them to properly support them.