Moin,
Am 27.11.21 um 01:11 schrieb Frank H. Ellenberger:
[...]
> YellowNet war wohl die Schnittstelle für die Schweizer PostFinance und
> ist irgendwann wegen ihrer Security-by-obsurity-Politik rausgeflogen.
[...]
Richtig, das Backen unterstuetzen wir nicht mehr. Man kann aber immer noch
YellowNe
Hi,
Am 10.07.20 um 05:54 schrieb Dan Howell:
[...]
> By sending the same request through cURL, but moving the parameter
> to right after (where it was with AqBanking 5), the query succeeds:
[...]
> So if this could be routed to the proper person who could fix this, I would
> be grateful for this
Hi,
Am 01.11.20 um 21:35 schrieb David Reiser via gnucash-user:
[...]
> The transactions are probably being sent, but aqbanking doesn’t handle
> brokerage account transactions well at all. The aqbanking author doesn’t have
> access to any US brokerage accounts to do testing. The net result is th
Hi,
just a general note on AqBanbkings OFX DirectConnect plugin:
Development on this plugin is pretty much on hold right now, because I
don't have access to any OFX server. Also, getting information on client
setup for OFX - especially regarding connection details such as server
url, protocol ver
Hi,
Am 15.03.20 um 20:17 schrieb John Ralls:
> I just made a MacOS build with the latest AQBanking so I could test it with
> my bank (USAA). No go, and a bit of troubleshooting reveals that it's because
> AQBanking now uses the XML-based OFX V2. AFAIK that's not supported by any US
> bank.
[...
Hi Chris,
could you please test the latest GIT version? It should create valid
OFXv1 requests now, however, I can't test it completely since I only
have access to an OFXv2 server...
Regards
Martin
Am 18.03.20 um 16:31 schrieb chris graves:
> An additional bit of information from /tmp/ofx.log:
OLDFILEUID:NONE
> NEWFILEUID:20200318135033.000
>
>
>
>
> 20200318135025.000
>
> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss <mailto:mar...@aqbanking.de>> wrote:
>
> Hi Chris,
>
> could you please test the latest GIT version? It should create valid
>
> Not sure if this could be the problem. Is there a way to set OFXHEADER
> and VERSION independently?
>
>
> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss <mailto:mar...@aqbanking.de>> wrote:
>
> Hi,
>
> you can change the header manually to 102
tring(buf, s);
> GWEN_Buffer_AppendString(buf, "\r\n");
>
> Because at the second test s has a value.
>
> The new code doesn't emit the trailing tags, so that may not have been the
> problem. The main difference other than the OFXHEADER: value now appears to
&g
FXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318144035.000
>
> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss <mailto:mar...@aqbanking.de>> wrote:
>
> Hi,
>
>
gt; SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318144035.000
>
> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss <mailto:mar...@aqbanking.de>> wrote:
>
> Hi,
>
> not ATM, but that can be
gt; ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200315112517.000
>
> 20200315112517
>
> ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y
>
>
> Regards,
> John Ralls
>
>>
Hmm, maybe the server is picky about the HTTP version? Some servers
are... That can currently only be changed directly in the configuration
file:
$HOME/.aqbanking/settings6/users/*.conf
Some servers only accept httpVMinor="0"...
Regards
Martin
Am 18.03.20 um 23:20 schrieb John Ralls:
> Sigh,
fx%2FOFXServlet"
> char appId="QWIN"
> char appVer="2300"
> char headerVer="102"
> int httpVMajor="0"
> int httpVMinor="0"
> }
>
> Regards,
> John Ralls
>
>
>> On Mar 18, 2020, at 4:15 PM,
the OFX specs show this example:
-X8
POST http://www.fi.com/ofx.cgi HTTP/1.0
User-Agent:MyApp 5.0
Content-Type: application/x-ofx
Content-Length: 1032
OFXHEADER:100
DATA:OFXSGML
VERSION:160
SECURITY:TYPE1
ENCODING:USASCII
CHARSET:NONE
COMPRESSION:NONE
Okay, we should now look for console logs.
I'm not sure how Gnucash handles log files, but you could try the
process of requesting statements using console-only:
1. get list of accounts:
# aqbanking-cli listaccounts
Column 6 contains the unique account id to be used in the next step.
2. get sta
ing account. Looking at the ofx.log file, they were
> returned!!!
> >
> > However the import process indicated that there were no
> transactions to be imported.
> >
> > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss <mailto:mar...@aq
X
>
>
> 2020030900
> 2020031800
> Y
>
>
>
>
>
>
> Taking out the \r\n's doesn't help either.
>
> Regards,
> John Ralls
>
>> On Mar 18, 2020, at 4:32 PM, Martin Preuss wrote:
>>
>> Hi,
>>
>
Dave,
you could try "AQOFX_LOG_COMM=PATH_TO_LOGFILE" ("=1" should still create
the default log file, but in newer versions of AqBanking you can also
set the path and name of the log file to use).
Martin
Am 30.03.20 um 06:10 schrieb David Reiser via gnucash-user:
> Giving Gnucash 3.9 full disk
" regardless of the
value given...
Martin
Am 30.03.20 um 22:03 schrieb Chris Graves:
> My experience is that setting AQOFX_LOG_COMM=1
>
> Creates the ofx log file in the current directory, however the name of
> the file is “1”.
>
>> On Mar 30, 2020, at 11:51 AM,
Hi,
Am 19.03.24 um 23:49 schrieb An Ku:
[...]
Installing 5.5.1 I do see those now. However, when I go to
File>Import>Import using AQBanking and select swift>SWIFT-MT940 followed by
the file, nothing happens. The window closes and that's it. I have not done
any kind of AQBanking installation or s
21 matches
Mail list logo
