So, sometimes, Projects take a bit longer and need to be postponed, but I still got an Issue here:
I am trying to send a GET Request from a control server to some smart home devices (thermostats to be exact) and doing so I get an "Error 400 - Bad request" reply.
Shelly - TRV_Poll_Status - Error Polling Status: Crestron.SimplSharp.Net.Http.HttpException: HTTP/1.0 400 Bad Request
Server: lwIP/2.1.2 (http://savannah.nongnu.org/projects/lwip)
Content-Type: text/html
at Crestron.SimplSharp.Net.Http.HttpClient.Dispatch(HttpClientRequest aRequest)
at Shelly_Integration.Shelly.TRV_Poll_Status(String Device_IP, String Username, String Password)
at UserModule_SHELLY_TRV_V3.UserModuleClass_SHELLY_TRV_V3.POLL_OnPush_1(Object __EventInfo__)
at Amib.Threading.Internal.WorkItem.n()
at Amib.Threading.Internal.WorkItem.Execute()
at Amib.Threading.SmartThreadPool.f(WorkItem A_0)
at Amib.Threading.SmartThreadPool.r()
Talking to the manufacturer, this might be due to some "fragmentation" and the lwIP service not liking this, pointing to some "network" issue. That's why I am here. I can connect with a browser just fine to all those thermostats, but not with my control system. If a TRV sends an URL Out on it's own, it arrives in the control system and is processed just fine.
Now, I am looking for a way to improve this. This is my network topology:The CRS3112-4C-8XGM-RM is acting as a core switch, central router and Capsman - Manager with this config:
The CRS328-24P-4-S+ are basically my access layer switch, here is one example config:and then, aside from the config they receive by the Capsman, I fiddled a bit on the hap ACs:The control system is plugged to the core switch and the TRVs are all over the building, connected to the "Shelly" WiFi. So, the path is always: Core --> Access - Switch --> Access - Point. (The APs on the CRS112s are outside, so a TRV should not try to connect there).
Any ideas on which screws to turn?
I am trying to send a GET Request from a control server to some smart home devices (thermostats to be exact) and doing so I get an "Error 400 - Bad request" reply.
Shelly - TRV_Poll_Status - Error Polling Status: Crestron.SimplSharp.Net.Http.HttpException: HTTP/1.0 400 Bad Request
Server: lwIP/2.1.2 (http://savannah.nongnu.org/projects/lwip)
Content-Type: text/html
at Crestron.SimplSharp.Net.Http.HttpClient.Dispatch(HttpClientRequest aRequest)
at Shelly_Integration.Shelly.TRV_Poll_Status(String Device_IP, String Username, String Password)
at UserModule_SHELLY_TRV_V3.UserModuleClass_SHELLY_TRV_V3.POLL_OnPush_1(Object __EventInfo__)
at Amib.Threading.Internal.WorkItem.n()
at Amib.Threading.Internal.WorkItem.Execute()
at Amib.Threading.SmartThreadPool.f(WorkItem A_0)
at Amib.Threading.SmartThreadPool.r()
Talking to the manufacturer, this might be due to some "fragmentation" and the lwIP service not liking this, pointing to some "network" issue. That's why I am here. I can connect with a browser just fine to all those thermostats, but not with my control system. If a TRV sends an URL Out on it's own, it arrives in the control system and is processed just fine.
Now, I am looking for a way to improve this. This is my network topology:The CRS3112-4C-8XGM-RM is acting as a core switch, central router and Capsman - Manager with this config:
The CRS328-24P-4-S+ are basically my access layer switch, here is one example config:and then, aside from the config they receive by the Capsman, I fiddled a bit on the hap ACs:The control system is plugged to the core switch and the TRVs are all over the building, connected to the "Shelly" WiFi. So, the path is always: Core --> Access - Switch --> Access - Point. (The APs on the CRS112s are outside, so a TRV should not try to connect there).
Any ideas on which screws to turn?
Statistics: Posted by Jenswizzard — Wed Jan 17, 2024 4:13 pm