#1
I just resurrected an old SickBeard instance recently and migrated it over to SickGear. Within NZB360 going to the SickBeard section I can access it with the correct API . I can see the SickGear history within the NZB360 app, but I cannot see any shows or future dates (this all used to work fine with SickBeard before migration). Looking at the SickGear log file I can see the following show up when I access the SickGear section within NZB360 app:

2021-04-18 21:26:46 DEBUG TORNADO :: API (app name (old key)):: xxx.xxx.xxx.xxx - gave correct API KEY: app name (old key). ACCESS GRANTED
2021-04-18 21:26:46 DEBUG API^WEB_1 :: API (app name (old key)):: cmd: 'future'
2021-04-18 21:26:46 DEBUG API^WEB_1 :: API (app name (old key)):: all args: '()'
2021-04-18 21:26:46 DEBUG API^WEB_1 :: API (app name (old key)):: all kwargs: '{'sort': 'date'}'
2021-04-18 21:26:46 DEBUG API^WEB_1 :: API (app name (old key)):: future: curKwargs {'sort': 'date'}
2021-04-18 21:26:46 WARNING API^WEB_1 :: API (app name (old key)):: SickBeard API call "future" should be replaced with SickGear API "sg.future" calls to get much improved detail and functionality, contact your App developer and ask them to update their code.


Also see the following (not show the old API lines -- if needed I can provide the entire relevant sections of the SickGear log file):

2021-04-18 21:26:47 WARNING API^WEB_2 :: API (app name (old key)):: SickBeard API call "future" should be replaced with SickGear API "sg.future" calls to get much improved detail and functionality, contact your App developer and ask them to update their code.
2021-04-18 21:26:48 WARNING API^WEB_0 :: API (app name (old key)):: SickBeard API call "shows" should be replaced with SickGear API "sg.shows" calls to get much improved detail and functionality, contact your App developer and ask them to update their code.
2021-04-18 21:26:51 WARNING API^WEB_1 :: API (app name (old key)):: SickBeard API call "history" should be replaced with SickGear API "sg.history" calls to get much improved detail and functionality, contact your App developer and ask them to update their code.

I also found the API that SickGear publishes: https://sickgear.docs.apiary.io/#reference/sick-beard

I thought this would just work out of the box but appears there are some API changes under the hood of SickGear that need updates on the NBZ360 side. Is anyone else having these issues? Thanks.
cron