How does EnergyLabs calculate accurate energy savings? Berlin. September 2021. With our solution ActiveEnergy, saving energy becomes as easy as making a cup of tea. After our AE PowerStation is installed, it does not require any further actions from our partners and...
Berlin. August 2021. Recently, EnergyLabs traveled for some interesting installations. The installations of our MobileHubs took place within the critical infrastructure in Europe. We had to take a plane to be able to undertake those, being fully vaccinated of course....
Berlin, July 2021. When the topic of energy efficiency is brought up, what mostly comes to people’s minds seems to be building insulation. Heat and insulation are important components of our lives and homes. But our (residential) buildings are capable of much more....
Berlin, June 2021. The electricity grid is a network for the distribution and delivery of electrical energy from producers to customers and largely contributes to the comfortable everyday life we know. In this post, we will focus on the grid from EnergyLabs’...
Berlin, April 2021. It has been four months since the implementation of the carbon tax in Germany in order to achieve the global climate goals. EnergyLabs looks at the recent developments, what alternatives there would have been and why the decision on carbon pricing...
Berlin, March 2021. The ActiveEnergy solution, is a combination of hardware and software. The hardware, the AE PowerStation uses voltage optimization to adapt the voltage level in buildings. Together with machine-learning and high-resolution data monitoring, it is not...
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about the visitors of this website. To find out more about the cookies we use, read on..
Cookies in this category are being used to improve our services.
This cookie is used by google analytics to distinguish users.
This cookie is used by google analytics to persist session state.
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.
Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.
This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.
If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
This stores information about the user viewport such as size and dimensions.