Is there a way I can update all my end devices with the same parameter in the same Application using the ttn-lw-cli without having to enter the same command for each device?
I can use the list command to get all my end device in my application but stuck on how to use the update command to set for instance supports-32-bit-f-cnt to true for all the end devices without having to enter the same command one after the other for all the devices using the device id.
I tried this command:
end-devices update my-test-stations all [flag]
I got this error:
end device with id all not found in application with id my-test-stations
I am kind of having the same issue with end device update
ttn-lw-cli devices downlink push
âapplication-id xxxxxxx
âdevice-id d54e5bffff134af8
'{âf_portâ:6,âfrm_payloadâ:âAWECALQ=â,âconfirmedâ:true}'error:pkg/applicationserver:device_not_found (device xxxxxxxx@xxxxxx not found)
device_uid=2xxxxxxxx
correlation_xxxxxx
I was able to confirm login via cli and list all the devices in the App also able to confirm the specific device exists
if i use the console to send downlink with the same command it works. but i need to update 100 devices .
Device not found isnât really the barrier to updating 100 devices, first you need to get the CLI to update one by using the documented format for the command.
And then you script it to read a file of ids to queue them one at a time - there is no bulk downlink send.
Where are these devices, I want to watch for the smoke coming out of the gateways.
I am just trying to update one device thatâs local to me in California , we have devices all over US , i dont want any smoke , i am not sure whatâs wrong with my command .
do you see any issue with the command?
we have 600 + devices in different application,
here is the command i am using
ttn-lw-cli devices downlink push --application-id xxxxxxxxx --device-id xxxxxxxxxxxx â{âf_portâ:6,âfrm_payloadâ:âAGE=â,âconfirmedâ:true}â
this is the error i am getting
error:pkg/applicationserver:no_payload (no payload)
Thanks for your help
i use this format and it worked ttn-lw-cli devices downlink push
âapplication-id âxxxxxxxxâ
âdevice-id xxxxxxxxx
âf-port 6
âfrm-payload 01610200B4
âconfirmed
No neither do we on the community network - confirmed downlinks are not just bad, but extra very bad - many discussions on this matter all over the forum. Hopefully you wonât end up with a perpetual downlink loop.
Yes, as I said, not formatted per the documentation.