You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, let me congratulate you for the great work and for taking the time to share it. I have installed pycryptobot on my Windows 10 box and it is running, so far no orders were triggered though. I have it using Binance and configured for BTC-BRL pair.
I noticed that there seems to be a mix of local time in some messages and a different time in others. I am posting a screen capture so you can see. My system is configured for ETC-3 (Brazil). You will see that at the time I took the capture (local time was about 16:44) there are previous messages showing time at 19:30. Maybe some messages derive time from the API of Binance? Or something related to time zones.
Let me know if you need more info on the case.
The text was updated successfully, but these errors were encountered:
It looks like the data being processed is returning the timestamp from the exchange and the polling of the price is using your local time. I don't think this would actually be causing a problem. It's more of a cosmetic issue. I'll take a look at how I can fix this for you.
Hi Michael
First, let me congratulate you for the great work and for taking the time to share it. I have installed pycryptobot on my Windows 10 box and it is running, so far no orders were triggered though. I have it using Binance and configured for BTC-BRL pair.
I noticed that there seems to be a mix of local time in some messages and a different time in others. I am posting a screen capture so you can see. My system is configured for ETC-3 (Brazil). You will see that at the time I took the capture (local time was about 16:44) there are previous messages showing time at 19:30. Maybe some messages derive time from the API of Binance? Or something related to time zones.
Let me know if you need more info on the case.
The text was updated successfully, but these errors were encountered: