LiveNoise Version 2

LiveNoise Version 2 Support

LiveNoise networked noise monitors for indoor and outdoor noise measurement with cloud based reporting. These devices connect to a SoundEar noise warning sign or noise processor, which is included in the package.

Support Request

Name
Email
Question

Frequently Asked Questions

Networking and Communications

The LiveNoise monitors communicate with the LiveNoise cloud server over your local area network, using either a wired Ethernet connection or a Wi-Fi connection.

The display on the noise monitor (LN2-SE) or on the SoundEar device (LN2-EAR, LN2-IND, LN2-320) should be showing the current sound level, updating every second. If not, please check that the power supply is connected. This would suggest a fault with the power adapter or cable.

The noise monitor needs connecting to your network using a wired Ethernet connection or Wi-Fi. Please follow the instructions in the User Manual for configuring the Wi-Fi. If the device is already connected by cable or Wi-Fi but still no live data there may be a routing or firewall issue. This is covered in the User Manual but, in summary, here are the details you need to know.

The noise monitor communicates with our server using Secure WebSockets (wss) on Port 443. This means the communication looks very similar to a web browser visiting a secure website (https). If the noise monitor does not have access to the Internet or if the WebSockets on Port 443 are being stopped it will not be able to communicate with our server.

The address of our server is account.livenoise.net

Neither the local or public IP address of the noise monitor needs to be fixed. The LiveNoise monitor initiates all communication directly with our cloud server, it's IP address is not relevant.

General Information

All LiveNoise v2 noise monitors have 16 GB of internal memory. This is enough to store the last three years noise measurements. When the device has been in use for over three years it overwrites the older data with new so there is no need to clear the memory.

This storage is much larger than actually needed. It is only used as a buffer in case your noise monitor is offline for a period of time and cannot connect to the cloud server. Once the connection is reestablished it sends the buffered data automatically.

That means it could be offline for up to three years and, as long as it still has power and has no other issues such as microphone damage, the measurements will be available after reconnecting.

Yes, your version 1 noise monitor can be upgraded to version 2, but it will have to be returned to us to carry out the upgrade. The two devices are physically the same so we would only be upgrading the code, but unfortunately that can't be done remotely because of security measures that the device has in place.

LiveNoise v2 noise monitors do not work with the Supervisor and Reporter Windows software. They talk only to our cloud server and all real-time sound levels and long term reporting is done using your web browser.

The outdoor model (LN2-SE) requires 24V DC and the indoor versions (LN2-EAR, LN2-IND, LN2-320) require 5V DC. Both indoor and outdoor versions are provided with a suitable power adapter.

All versions of LiveNoise monitors demand a maximum power of 12W.

The outdoor model (LN2-SE) comes with a 10m, 33ft extension cable fitted. The power adapter itself must be mounted indoors or in a weatherproof enclosure.

The code that carries out the noise measurements and reporting can be updated by NoiseMeters remotely if we have new features that you want. However, this update is not carried out without first seeking the owner's permission. We do not carry out automatic forced updates.

These updates are carried out via our cloud server. For security reasons we do not have direct access to your device. Updates are not carried out by SSH, FTP or any similar direct method. There is no access to the device by SSH or FTP, these ports are closed.

System level updates are not available remotely. While this can sometimes be convenient in a remote product we consider the security risks involved to be too high.