Netatmo - types and measurements lists are different sizes

Hello, who can explain to me what this error means and how I can fix it. I have no idea where to look.
I am using OH3 (latest snapshot). If you need more details ask me.

[WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.IllegalArgumentException: types and measurements lists are different sizes.
	at org.openhab.binding.netatmo.internal.handler.AbstractNetatmoThingHandler.getMeasurements( ~[?:?]
	at org.openhab.binding.netatmo.internal.station.NAModule4Handler.updateDayMeasurements( ~[?:?]
	at org.openhab.binding.netatmo.internal.station.NAModule4Handler.updateMeasurements( ~[?:?]
	at org.openhab.binding.netatmo.internal.station.NAMainHandler.lambda$7( ~[?:?]
	at java.util.Optional.ifPresent( ~[?:?]
	at org.openhab.binding.netatmo.internal.station.NAMainHandler.lambda$5( ~[?:?]
	at java.util.concurrent.ConcurrentHashMap$KeySetView.forEach( ~[?:?]
	at org.openhab.binding.netatmo.internal.station.NAMainHandler.updateReadings( ~[?:?]
	at org.openhab.binding.netatmo.internal.handler.NetatmoDeviceHandler.updateChannels( ~[?:?]
	at org.openhab.binding.netatmo.internal.handler.NetatmoDeviceHandler.updateChannels( ~[?:?]
	at java.util.Optional.ifPresent( ~[?:?]
	at org.openhab.binding.netatmo.internal.handler.NetatmoModuleHandler.requestParentRefresh( ~[?:?]
	at org.openhab.binding.netatmo.internal.handler.NetatmoModuleHandler.lambda$0( ~[?:?]
	at java.util.concurrent.Executors$ ~[?:?]
	at ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?]
	at java.util.concurrent.ThreadPoolExecutor$ [?:?]
	at [?:?]

with kind regards

It would mean one of the measures for your additional indoor module is no more provided by the API. This concerns the channels min/max for the current day (and theiir corresponding dates). For this module, you have min/max humidity and min/max CO2. Total of 8 channels with the dates.
Can you tell us what of these channels you linked ?
Can you unlink these channels one by one to identify which one is triggering the problem ?