Open Cloud-121 opened 17 hours ago
Setting StoreConfiguration__LoadWyzeSupportedCamerasOnStartup
to false allows the app to start but when the cameras are grabbed the same error is given within the web log.
PythonException: 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/api/user/login
Python.Runtime.PythonException.ThrowLastAsClrException()
Python.Runtime.NewReference.StealOrThrow()
Python.Runtime.PyObject.Invoke(PyTuple args, PyDict kw)
Python.Runtime.PyObject.InvokeMethod(string name, PyTuple args, PyDict kw)
Python.Runtime.PyObject.TryInvokeMember(InvokeMemberBinder binder, object[] args, out object result)
CallSite.Target(Closure , CallSite , object , string , string , string , string )
Cryze.API.Services.WyzeSdkService.DoLogin(PyModule scope, object wyze_sdk_library) in WyzeSdkService.cs
Cryze.API.Services.WyzeSdkService+<>c__DisplayClass12_0.<GetSupportedCameras>b__0() in WyzeSdkService.cs
Cryze.API.Services.WyzeSdkService.GetSupportedCameras() in WyzeSdkService.cs
Cryze.API.Services.WyzeSdkService.UpdateCameraList() in WyzeSdkService.cs
Cryze.API.Controllers.CameraController.GetAllSupportedCameras() in CameraController.cs
Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor+TaskOfIActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, object controller, object[] arguments)
System.Threading.Tasks.ValueTask<TResult>.get_Result()
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask<IActionResult> actionResultValueTask)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(ref State next, ref Scope scope, ref object state, ref bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(ref State next, ref Scope scope, ref object state, ref bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger)
Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
so you can set false, then log in following the directions on the UI. There's four total environment variable values involved with logging in.
I'm aware and I set all of them to what they should be, Are you saying start the containers with the only env being the false?
You should be able to set StoreConfiguration__LoadWyzeSupportedCamerasOnStartup=false, start only the api container, and then on the login page set the login variables and try loading the list of supported cameras. side note: I'm sorry for the mess, I was recovering from a surgery when I wrote this and my only goal was working cameras. Sanity was long gone ☠️
You should be able to set StoreConfiguration__LoadWyzeSupportedCamerasOnStartup=false, start only the api container, and then on the login page set the login variables and try loading the list of supported cameras. side note: I'm sorry for the mess, I was recovering from a surgery when I wrote this and my only goal was working cameras. Sanity was long gone ☠️
Your completely fine ^^
Great work on it <3 Very nice of you to release the fork and not just keep it private:3
I hope you're recovering well
so you can set false, then log in following the directions on the UI. There's four total environment variable values involved with logging in.
When I remove the User keys from the .env file and enter them inside the settings menu of the web interface, The cameras tab is able to pull the cameras but I'm unable to view the rtsp feed and a restart removes the login creds.
I'm doing much better now than I was, thanks for asking!
So config. Basically, the .env and the environment variables get read into IConfiguration and then pulled back out here: https://github.com/xerootg/cryze_v2/blob/main/cryze_api%2FModels%2FWyzeAPICredential.cs#L39-L42
Can you confirm you have all four? I know I had a typo at one point in the sample.env, but I think that should have been resolved.
Also, when you set the user/pass/key/secret, it gets written to a json file. If you set the 4, you should be able to retain the previously discussed value = false and just use the json for persistence.
Hello ^^ It appears this is a similar issue to #13 I have checked my config file for the WYZE_EMAIL ENV. Would you have any idea on the error?
LOGS