OneIP v4.1 Update

Pulse-Eight is pleased to announce the first update release of OneIP since its launch. This release encompasses multiple months of field deployment feedback and addresses installation feedback from our customers along with our on-going pro-active approach to bug and feature identification.

V4.1 primarily is intended as a stability enhancement release, with new features aimed purely at ease of setup and reduction in configuration and fault finding.

As always, if you encounter any issues in using our products, please email support@pulse-eight.com for further support.

New Features

Full support for dedicated OneIP TX and OneIP RX devices in a mixed network with OneIP TZ devices.

When devices are mirrored, Virtual Remote/IP Control messages (such as Power On/Off) are sent to ALL mirrored devices.

You can now selectively adopt individual devices into the Mesh rather than all or nothing. Additionally Offline devices are no longer forcibly removed during the adoption process.

IGMP Fast Leave detection has been added to the Advanced Diagnostics tools within the Web Interface

Improvements/Changes

SSDP/SDDP Advertisements are only done from a Master device, resulting in only relevant devices advertising. 

SDDP product name has been standardised across all three model types to avoid the need for multiple different Control4 drivers depending on what type of device was the master device.

Fan Speed has been adjusted to ensure it does not stall in all circumstances.

Direct Dish IP control support has been removed.

Sky has been renamed to Sky UK to reflect the region-specific nature of this IP control feature.

Default Multicast Control group has been adjusted to 224.8.8.8 to avoid bugs in Araknis switching hardware.

Built in Cable testing is now only supported for cable lengths more than 1 meter in length. NEXT and FEXT values cannot be relied on at very short distances.

Cross Pair Short is now referred to as “Excessive Cross Talk”, while not the official technical name, it is more widely understood.

Routing to Offline devices within the Web Interface is no longer possible, (i.e. the source is no longer draggable, and the sink is no longer droppable)

The built in Web Interface has been revised to improve accessibility and consistency between pages and more device types.

Bootloader version is now shown in the Hardware Details page.

Network Health value has been removed from the System Health page and can now be found in the Network Settings page instead.

The underlying Javascript and CSS is no longer minified and is left in a verbose readable state to allow developers/customers an easily modifiable template to work from.

System Health page now shows the Input and Output names on the User View to aid setup and deployment.

Realtime bandwidth usage Multicast Group data is show in the Network Settings page.

Mesh / System Health is no longer shown on Slave devices, only the Master device contains this information.

Multicast status (i.e. if IGMP is working) is shown next to each device on the Mesh Setup page. This can aid in debugging if IGMP traffic is not being forwarded correctly between multiple switches.

No Signal splash screen is now used when the connected source OneIP device is actually rebooting, instead of an error splash screen.

No Signal splash would show in preference of Device Offline splash, which was unintended.

Bug Fixes

Daisy Chained child devices no longer also try to subscribe to a video and audio stream independent of their parent.

IGMP Reports are now correctly sent every 30 seconds to prevent accidental automated leaves on some networking hardware.

Crash when changing EDID profiles in certain ways.

Autoscaling would sometimes not activate when intended.

Access-Control-Allow-Origin was missing in HTTP responses when the response was a 404 not found error.

1080i and other Interlaced video modes were not correctly scaled to 1080p (progressive) and instead would not be rendered.

General improvements to Cable Testing feature to improve accuracy and reliability of its reported values.

Enabling/Disabling CEC support setting was inverted in the GUI

Temperature values reported within the GUI was always 60c

Connecting status to the Cloud Monitoring Service would show as an Error rather than as a warning.

When a port was mirrored, it was not possible to also hide it.

Do not show the Virtual Remote for Offline Sink devices.

It is no longer possible to set the IP address for IP controlled devices to an invalid IP address.

Additional Discovered Network Devices section on Mesh Setup page no longer shows if there are no additional devices found.

Internal logging would not wrap in all circumstances if it exceeded 2mb in size.

API Changes/Improvements

It is now possible to route to ‘Nothing’ by setting the Input in Port/Set to -2

The API data structure returned by the call to System/Health has been adjusted to correct an issue where IR status information was in the Video data block.

/Network/Remote/FactoryReset has been added to do a global factory reset across all devices within the mesh. It is NOT recommended to call this method unless looking to start the entire deployment again. No settings are retained.

/Port/List now includes a Boolean ‘cec’ value against each input and output to indicate cec support of the OneIP device. (This still does not guarantee CEC is supported by the connected sink or source however).

When requesting a routing change via /Port/Set if the routing request is denied due to a source filtering setting, this is now recorded by a “SourceRoutingDenied” value being returned, rather than simply Result: false.

Known Issues

The following items are known about and are expected to be resolved in the next major release (v4.2)

Scaling to 1680x720 resolution is temporarily disabled.

It is not possible to remove a device from the Mesh via the Web Interface.

Certain small and medium screen size devices are unable to easily be used for the setup of a OneIP mesh, i.e. the mesh setup page is unusable due to incorrect sizing of table values etc. It is always advisable to just a large resolution device to do the initial setup however.

In certain circumstances when performing a reboot via the API the system will stall performing such a reboot. The device can still be remotely power cycled by toggling the PoE+ power on the connected network switch or physically disconnecting the power source from the device and reconnecting it. There are no negative effects from performing these actions.