d
DanielH
02/09/2023, 4:35 PMDanielH
02/11/2023, 3:27 PMThis error is caused by hive is set to not allow empty client id and in this case chirpstack fails to create random id.
DanielH
02/11/2023, 3:27 PMsolution: change config map and set id:
j
Jermuk
02/11/2023, 7:10 PM@Ferdinand FYI
Jermuk
02/11/2023, 7:10 PMlets put it into learn
d
DanielH
02/12/2023, 10:49 AMi am not sure of which setting you use as default for hive, in the documentation for the older mqtt standard it looks like they have a max length of 8 signs for the client id since the old mqtt could not handle longer but if i read the documents correct at hive the default setting now should be 65535 so the problem should not be the length of the id, instead it must be that id is missing.
DanielH
02/12/2023, 10:52 AMDanielH
02/12/2023, 10:53 AMDanielH
02/12/2023, 10:53 AMDanielH
02/12/2023, 10:54 AMcould also be that the generated id is not utf-8
j
Jermuk
02/12/2023, 3:28 PMdo you have the logs of HiveMQ when chirpstack fails to connect? as far as I know we did not change anything in the defaults
d
DanielH
02/12/2023, 7:31 PMNo unfortunately not. Unless it saves the logs on the disk? Then i can check
DanielH
02/12/2023, 7:31 PMWhich mqtt version do you use?
j
Jermuk
02/13/2023, 1:22 PMmost of our services use v3
Jermuk
02/13/2023, 1:23 PMI added a note to our upgrade guide regarding the client-ids and it will be published in the upcoming days
d
DanielH
02/13/2023, 1:26 PMthe 3.1 standard only allows 23 signs for client id.
2 Views