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
Asking the time of susi server returns the time in GMT instead of local time, ignoring various information.
Example code:
importsusi_pythonassusiimportrequestssusi.ask("what is the time")
{'planned_actions': [], 'answer': 'it is 12 minutes past 8'}
# actual time is 16:08# send request with parameters is# https://api.susi.ai/susi/chat.json# {'q': 'what is the time', 'timezoneOffset': -540, 'device_type': 'Smart Speaker'}# now try to set location and send additional geo data, toores=requests.get('http://ip-api.com/json').json()
susi.update_location(longitude=res['lon'], latitude=res['lat'],country_name=res['country'], country_code=res['countryCode'])
{'planned_actions': [], 'answer': 'it is 12 minutes past 8'}
# actual time is 16:08# send request with parameters is# https://api.susi.ai/susi/chat.json# {'q': 'what is the time', 'timezoneOffset': -540, 'device_type': 'Smart Speaker', 'latitude': 36.4002, 'longitude': 136.4757, 'country_name': 'Japan', 'country_code': 'JP'}
Thus, susi server ignores
timezoneOffset
latitude and longitude
country_name and country_code
Expected Behaviour
I expect SUSI server to answer in local time.
The text was updated successfully, but these errors were encountered:
Digging through the source code, I see that the timezoneOffset and other infos are added to the recall, but never evaluated for normal answers. The only place where the timezoneOffset plays a role is in the planned action section, but for things like "what is the time" it is not used.
Actual Behaviour
Asking the time of susi server returns the time in GMT instead of local time, ignoring various information.
Example code:
Thus, susi server ignores
timezoneOffset
latitude
andlongitude
country_name
andcountry_code
Expected Behaviour
I expect SUSI server to answer in local time.
The text was updated successfully, but these errors were encountered: