Joel Kåberg
                                            Joel Kåberg
                                        
                                    Hi @jonmchan, longtime bastion Duo user here running latest tag (yes bite me 😆) and I haven't noticed any issues with the latest release you guys have pushed - all...
@bob-tm Thanks for sharing, this is my approach which is very similar to yours :-) ``` from typing import Literal from datetime import datetime, timezone from homeassistant.components.recorder import get_instance from...
I'd just like to point out this resource aswell: https://spot.56k.guru/homeassistant -> https://github.com/Hexagon/spotweb (also based on ENTSO-e) and https://www.strompriser.no/artikler/api-for-strompriser
this fixes #94 also please deploy an new container version while at it 😄
If you have an office365 or outlook.com account you can view the (same) output here (as z-push would've pushed out) https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml
Thanks for looking into this @fmbiete Still errors tho; > 20/08/2014 18:46:00 [20728] [ERROR] Unable to complete autodiscover because login failed for user. Error: Unauthorized > 20/08/2014 18:46:00 [20728] [FATAL]...
@redhell Tried that, still errors in /var/log/z-push/autodiscover-error.log > 21/08/2014 11:50:43 [27009] [FATAL] FatalException: Invalid input XML: not a mobilesync responseschema. - code: 0 > 21/08/2014 11:50:43 [27009] [ERROR] Unable to...
@redhell Samme error still It's trying to download the http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006 and I'm pretty sure thats why autodiscover.php errors And just for the record, same error with this one aswell http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006...
@Ivshti are there any documentation on how to do the other stuff? eg what parts/packages does one actually need? I'm willing to undertake this and cobble together an solution based...
Also I'd like to point out one major argument that advocates for decentralization; and that's the heavy dependency on the centralized API/service. While in theory the current model *should* hold...