EnergyLabs

Berlin, 2020. EnergyLabs offers a portfolio of solutions that realizes energy and CO2 savings for buildings. With our ActiveEnergy solution, we unlock saving potentials that are currently unused resources. We aim to create the digital future of energy and, together with our partners, turn buildings into active protectors of the environment.

We unlock a building’s potential to contribute towards a more sustainable world and the digitalization of energy. Our scalable solution can be implemented across entire building portfolios. It is customer-specific and dependents on the yearly kilowatt-hour consumption of the building.

We offer a comprehensive and straightforward evaluation of building portfolios. Thus, we are able to identify your building’s energy and CO₂ saving potential. Our exceptionally high data resolution enables us to discover previously unrealized energy-saving possibilities for our partners.

Our ActiveEnergy product provides high energy savings on demand by safely regulating and lowering the voltage level. By uniquely combining innovative hardware and software, we work precisely and provide valuable insights.

EnergyLabs_building_portfolio_energy_saving

EnergyLabs enables your buildings to respond autonomously to a changing environment. We also support you and your building portfolio to meet emission reduction targets and be prepared for possible regulatory changes. We consider ourselves a partner on the decarbonization path.

Our dependable ActiveEnergy solution is only the first of many products we plan to develop to optimize the building sector. It is our first step of turning buildings into active protectors of the environment – more products to follow.

Pictures: Unsplash

Cookie	Duration	Description
cookielawinfo-checkbox-necessary	1 year	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
pll_language	1 year	This cookie is controlling the preferred language and set every time a page is being loaded. It does not store any personal data.
viewed_cookie_policy	1 year	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

Cookie	Duration	Description
_ga	2 years	This cookie is used by google analytics to distinguish users.
_ga_	2 years	This cookie is used by google analytics to persist session state.
_hjAbsoluteSessionInProgress	30 minutes	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjCachedUserAttributes	session	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.
_hjClosedSurveyInvites	365 days	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.
_hjDonePolls	365 days	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.
_hjFirstSeen	session	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.
_hjid	365 days	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.
_hjIncludedInPageviewSample	30 minutes	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
_hjIncludedInSessionSample	30 minutes	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.
_hjLocalStorageTest	under 100ms	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.
_hjMinimizedPolls	365 days	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.
_hjRecordingEnabled	session	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.
_hjRecordingLastActivity	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).
_hjSession{site_id}	30 minutes	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.
_hjSessionRejected	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.
_hjSessionResumed	session	A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
_hjSessionTooLarge	session	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.
_hjSessionUser{site_id}	365 days	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.
_hjShownFeedbackMessage	365 days	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.
_hjTLDTest	session	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.
_hjUserAttributesHash	session	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.
_hjViewportId	session	This stores information about the user viewport such as size and dimensions.

Your partner in energy saving

EnergyLabs