plan44.ch

Firmware 2.8.4

General Recommendation for updates: before updating, please always use the "Download configuration backup" button to download a backup of your device's configuration

Preparation for Firmware 3.0

This 2.8.4 release is also a required intermediate step towards the upcoming 3.0 major release. 3.0 will bring many enhancements to the entire P44 device range (except for P44-DSB-DEH first version):

• Completely reworked Web UI, switchable E/D languages, dark/light themes, all status updated live as changes happen in hardware.
• All P44-DSB devices now can also work as standalone smart home controllers as a configuration option (like P44-LC), independently of DS integration.
• Matter controller (using matter accessories in DS and standalone modes) as a (beta) configuration option.
• Completely optional: integration for AI agents (MCP server) - just ask your agent to "create a scripted device for the Shelly 1 4G at 192.168.1.77"...
• Based on current OpenWrt 25.12 foundation.

The intermediate step is required because logins need to be migrated to the new UI's webserver - when upgrading to the 3.0 firmware you will be asked to validate the current login to make sure it will work in the new UI.

Changes since 2.8.3

General

• Window Status: fixed the long standing misnaming for window contact inputs - these designate closed windows when active, but the text label in input display said "window open". note that evaluators based on window contacts need to be reviewed, because the input associations might become invalid due to the label change. Just select the correct input again to fix.
• rrdb (sensor history): Sensors configured for recording time series (years old inofficial feature, ask in forum if you are interested) now have a nice dashboard page at /rrd.html showing one or multiple graphs and featuring grouping by sensor type to overlay multiple graphs of the same physical unit type.

Evaluators and Triggers

• Small but relevant change in WebUI: condition text fields now allow entering expressions on multiple lines, including comments - which can make complex conditions much more readable.
• Evaluator with no off condition set will now just follow the value of the on condition, instead of remaining on forever after first time on condition is met.

p44script

• DMX inputs: This is a relevant feature when it comes to using P44-LC/DSB based LED effects, smarthome elements or P44-AC controlled installations in a stage or event setup, where DMX is the common way of controlling gear. The new dmxinput() object can receive DMX via Art-Net and sACN, and virtual fixtures consisting of one or multiple channels() can be mapped onto any light or other functionality available in the P44 device with only a few lines of mainscript code.
• encrypted/encoded data handling: add encrypt/decrypt/encode/decode functions to work with AES encrypted and base64 encoded data.
• IPv4/IPv6: IPv4 peer addresses are now always reported in plain IPv4 format, even when internally mapped onto IPv6 (::ffff:1.2.3.4 style). This avoids breaking scripts that rely on plain IPv4 adresses.
• new/improved functions: New function between_times(). New average() function which returns the average of all non-null arguments. This is useful for example in trigger/evaluator conditions involving multiple room temperature sensors, of which some might not always have a value. min() and max() now also allow multiple arguments and also ignore nulls.

LED chain

• LED effects: fixed long standing bug with timing alignment, which could make fast moving scrollers stutter a bit in complex setups with other animations going on in parallel.

Proxy Devices

• DNS-SD based proxy discovery: Subsystems advertising the bridge API (with --bridgeapinonlocal --advertisebridge as _p44-br._tcp) can be found automatically by the main controller. Newly found subsystems must be confirmed once in the main controller before devices are included.
• proxy: Zone names are now synchronized between proxy targets and proxy host. Creating new zones on the proxy host will not accidentally use zoneIDs already in use in proxy targets.