Stefan
Stefan
As @johntdavis84 I worked on getting SSL working on my pi-hole, as the documentation states this is important > Port 443 is to provide a sinkhole for ads that use...
> Remove what from where? Please link to the exact section that you are referring to. I'm referring to the quoted paragraph ("Port 443 is to provide...") above, it's in...
> I gotcha Thanks!
Same here with npm. No problem - but a lot of warnings - with yarn.
I have the same problem using DKB and the official test script. get_sepa_accounts works, get_balance and get_transactions not. simple_sepa_transfer works also.
A simple workaround: Define 'heading_name' and 'heading_state' in your card definition. E.g. entity: sun.sun filter: include: - sun.sun.next_rising - sun.sun.next_setting - sun.sun.next_dawn - sun.sun.next_dusk type: 'custom:entity-attributes-card' heading_name: Name heading_state: State
I understand, I already assumed, that this will be not easy possible. I have an older model TSOL-MS600, but with probably exotic firmware RSW_400_V1.00.20
Of course. I assume, there are sensible private data inside these traces, which should not published. How can I remove them?
Great, thank you.
@s-allius I've been using version 0.8.0 for a few days now, and at the moment I seem to be having a lot of connection problems, so a lot of data...