We have taken a docker image to run a chirpstack NS . It works fine
From what i see at startup we are using
“starting ChirpStack Application Server” version=3.10.0
“starting ChirpStack Network Server” band=EU868 net_id=000000 version=3.9.0
“starting ChirpStack Gateway Bridge” version=3.8.0
“starting ChirpStack Geolocation Server” version=3.3.1
I m able to configure gateway profile .
But when i configure gateway there is now way to select a gateway profile in the GUI ?
I miss something ?
Guys ! it looks like there is a problem of consistency . Why is it still possible to configure a gateway profile if gateway profile is no longer available anymore in chirpstack new version ?
I confirm i can’t assign gateway profile to gateway but i m still able to provision a gateway profile object
@nbertaud which versions of the AS/NS are you using? As @sebasArboleda commented, Gateway Profiles are deprecated and will be completely removed in the newer releases. There is a note in the Gateway Profile Tab that states that they will be removed in newer releases (See attached screenshot).
Correct, it has been re-purposed a few releases ago. Support for configuring the Semtech UDP packet-forwarder has been removed from the ChirpStack Gateway Bridge, but it does support configuring the ChirpStack Concentratord
i download a docker image in the server i authorize 16 EU channels. I create a gateway profile and in the gateway profile i do not declare any extra channels. from what i see the devices are using all the channels and the the lora message are not filtered in the gateway all message are comming in application. How it is supposed to work ? in that configuration in understand only message with channels 0,1, 2 (standard channels) shoudl reach application ?
Then there is no need to select the gateway-profile. The Gateway profile only works together with the Concentratord as the Concentratord component knows how to handle the configuration messages to update its channel-plan.