Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
| Name |
Domain |
Purpose |
Expiry |
Type |
|
wpl_user_preference |
digifolio.co.uk |
WP GDPR Cookie Consent Preferences. |
1 year |
HTTP |
|
__stripe_mid |
digifolio.co.uk |
For processing payment and to aid in fraud detection. |
1 year |
HTTP |
|
__stripe_sid |
digifolio.co.uk |
Stripe Cookie to process payments |
Session |
HTTP |
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
| Name |
Domain |
Purpose |
Expiry |
Type |
|
_fbp |
digifolio.co.uk |
Facebook Pixel advertising first-party cookie |
3 months |
HTTP |
Analytics cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
| Name |
Domain |
Purpose |
Expiry |
Type |
|
_ga |
digifolio.co.uk |
Google Universal Analytics long-time unique user tracking identifier. |
2 years |
HTTP |
|
IDE |
doubleclick.net |
Google advertising cookie used for user tracking and ad targeting purposes. |
2 years |
HTTP |
|
sbjs_migrations |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_current_add |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_first_add |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_current |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_first |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_udata |
digifolio.co.uk |
Sourcebuster tracking cookie |
55 years |
HTTP |
|
sbjs_session |
digifolio.co.uk |
SourceBuster Tracking session |
Session |
HTTP |
Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
| Name |
Domain |
Purpose |
Expiry |
Type |
|
mailchimp_landing_site |
digifolio.co.uk |
Mailchimp functional cookie |
28 days |
HTTP |
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
| Name |
Domain |
Purpose |
Expiry |
Type |
|
_gcl_au |
digifolio.co.uk |
--- |
3 months |
--- |
|
_ga_0ZG4Z6E7EE |
digifolio.co.uk |
--- |
2 years |
--- |
|
_ga_8T3NRBS21G |
digifolio.co.uk |
--- |
2 years |
--- |
|
FCNEC |
digifolio.co.uk |
--- |
1 year |
--- |
|
m |
m.stripe.com |
--- |
2 years |
--- |
 Weekly Elec. (KWh) on 'Smart' Page Daily Elec. (KWh), on 'Smart' Page Monthly Elec. (KWh) on 'Smart' Page Current Ele(mA), Current Power(W), Current Voltage(V), Please note it's not bidirectional meter, it can only measure the consumed power. and only show positive data on App. Technical […]){kind=link}
D***l
works with z2m but power (kWh) is a delta from last measure, need to check retain flag in settings
J***z
It works perfectly and fulfills its mission, but you must take into account some things if you want to integrate it into Home Assistant.
There is still no official support with ZHA (I do not know if with Zigbee2MQTT it works since I do not use it). Home Assistant finds the device but then shows no consumption sensor. To solve this you must look for a “quirk” file and install it where it corresponds so that the sensors are generated.
Once recognized as God intended, it works perfectly.
o***d
conforme
S***a
Energy consumption counting does not work well with Zigbee2MQTT on home assistant. Instant power and voltage seem correct.