gRPC created devices without metrics / device status request

Hello,
I’ve opened a new topic because I seem to have a bigger problem when creating the devices.
→ referring to my other question
(Periodic downlink - encodeDownlink() - device joinrequest after ~14 Days - #5 by Christian)

I’ve gRPCed most of my devices through BloomRPC so far. That all worked very well for swoeit. Because of the problem with the downlink from the other topic, I noticed that the devices probably have a problem in some way.

We are running Chripstack V4, the applications have an influxDB integration.
The devices are imported with the BloomRPC program

  • api.DeviceService Create - Device creation with tags and variables
  • api.DeviceService CreateKeys - device keys (enter the supplied application key in the nwk_key and app_key fields)

All devices join properly and pass their data on to the influxDB integration.

Now to the problem, the link and device metrics remain empty.
No device status request is sent either, although it is set.

Yesterday I started several attempts to delete devices and add them again, this time by hand. Chirpstack “recognizes” the device with all its old data (events, LoRaWAN frames).
But nothing has changed, no device status downlink, no metrics.

I have a couple of new temperature sensors here that I’ve been experimenting with.
Import with gRPC:

  • no metrics
  • no device status downlink
  • here even no integration, decoder is running, but no data is sent to influxDB

I have tried:

  • Device deleted and entered manually
    → Chirpstack still knew the old events / frames
    → transfer to InfluxDB works
    → metrics are there
    → device status downlink works

I did the same for a second device

  • Device deleted and entered manually
    → Chirpstack still knew the old events / frames
    → transfer to InfluxDB works
    → no metrics!
    → no device status downlink!

I don’t know what to do anymore, does anyone have an idea?
Are there any log files to look at?


Did you check the logs? :slight_smile:

could you tell me which logs are interesting?
I’m more in the frontend, can also check something in the background. everything else is up to the IT department

Hello,

I checked the logs with a colleague.
We don’t understand the last message, our region is actually enabled.
For the others, we don’t yet know how to eliminate them.

ERROR chirpstack::uplink: Deduplication error error=Zero items in collect set
ERROR up{deduplication_id=c0938195-eb9d-4ab9-b374-5fb8f6edb694}: chirpstack::uplink::data: Handle uplink error error=HTTP status server error (500 Internal Server Error) for url (http://172.25.0.23:9099/api/v1//attributes)
ERROR up{deduplication_id=e4aa11ef-3b74-469e-a50e-766d43854e49}: chirpstack::uplink::data: Handle uplink error error=error sending request for url (http://172.25.0.23:9099/api/v1//attributes): error trying to connect: tcp connect error: Connection refused
WARN up{deduplication_id=6b65c7aa-c4c3-4729-ba4e-16726bc35b6d}:data_up: chirpstack::uplink::data: No device-session exists for dev_addr dev_addr=260bcc77
WARN chirpstack::gateway::backend: Config exists, but region is not enabled. To enable it, add it to 'network.enabled_regions'