Trigger HTTP request after creating a device through the web interface

[bconway]

The notes from the 4.6.0 release today, there is a mention of the changing location of request log:

[release] ChirpStack v4.6

v4.6.0 Important note before you upgrade: If you are migrating from ChirpStack v3 to ChirpStack v4 and are still using the ChirpStack Gateway Bridge v3.14.x, then you must add v4_migrate=true to your configuration as described by the v3 to v4 migration documentation. Features End-to-end encryption This feature makes it possible to implement end-to-end encryption between the end-device and end-application. On OTAA join, the join-server will provide Chirpstack with the encrypted AppSKey, which …

It is likely that your Python package was updated. You will want to update your running ChirpStack instance and your own code, or pin the Python package to the version you were using previously.