editing ic2 value clears all sensors

[Ormingtrude]

I had very strange behavior on the i2c bus with an RPI5. It would not tolerate any run greater than 200mm and once I broke the 4-5 mark on i2c devices it became very unstable and acted erratic.

Adding an Adafruit LTC 4311 Active I2C terminator resolved the issue. May not be your problem but it is worth a try.

Hi. Thank you for the suggestion, I added the LTC 4311 I2C terminator to see if it might work and re-tested the system. In this case it didn’t resolve the issue.

 I hope it is a minor software incompatibility in the change from OP3 to OP4 which can be found soon. I will try using an ADS1015 in the meantime and see if those are compatible with OP4. 

I will report back with my findings, don’t hold your breath though it could take me some time.

I have just installed the ADS1015 and tested it and it behaves in the same way in OP4 as the ADS1115, in that it can be added, but when it is edited and a Signal K name allocated to any of the channels, all the entities in the I2C list disappear.

Considering the system works as expected in OP3 with the ADS1115, I am guessing that there might be a bug in OP4 with these analog to digital converters.

---

Hello,
I also have this same problem: impossible to enter a SK key for the ADS1115 sensor. This erases all other I2C sensors.
Have you found a workaround other than going back to V3?
My configuration: OP4 on RPi5/NVMe Pimoroni + Mac-Arthur hat
Thanks

Hello,

I have been unable to find or devise a workaround, sorry.  I am now hoping that someone will find the bug and be able to fix it, the only solution I have found is to revert to OP3 - not ideal, as you say.

I didn’t realize i had the same problem until i found this thread. My current thoughts are now to send the ADC rawdata via wifi from a Pico W or a Lora Arduino. Not sure if this was also explored, hopefully this is a workaround as i too don’t want to use an older version of OP.

Glad i found this as it was sending me down rabbit holes…

Weekend project task for me, would love to hear thoughts on this.

[MARIOI]

This seems to be a bug. I will try to reproduce it ASAP.

Hello Sailloog and all,


I'm having exactly the same issue with the latest versions and latest updates.

Has been found some way to work with this?

Many thanks

MaioI

[robheath]

I get the same issue. Adding an ADS1115 makes all my BME280 data disappear. Most peculiar.
Any suggesting appreciated.
Regards Rob

Raspberry Pi 4 with PiCAN-M hat.

[MARIOI]

Thanks guys.

For a while I thought I was the only one with this problem.

I tested ADS115, ADS1015, with and without trerminator and nothing works. always the same issue as described by @desolina_nz.


I hope that this problem can be easily found.

[Attila Mattei]

Hi guys,
I've the same problem with ADS115 connected to OpenPlotter4 on a Raspberry Pi5.
Does someone have any news how to solve this bug?

[Pizoton]

Solución al problema del ADS1115 en OpenPlotter 4.2.0: la configuración se corrompe al reiniciar el servicio I2C

 
 
Síntoma
Después de configurar un ADS1115 desde la interfaz gráfica de OpenPlotter I2C y asignar rutas de Signal K (SKkey)
 
ocurren uno o más de los siguientes problemas:

• La interfaz I2C deja de funcionar correctamente.
  
• Los sensores ADS1115 desaparecen o muestran errores.
  
• Se pierden configuraciones.
  

  • El archivo openplotter.conf cambia automáticamente.
 
Solución
1. Hacer una copia de seguridad
sudo cp \
/usr/lib/python3/dist-packages/openplotterI2c/openplotterI2cRead.py \
/usr/lib/python3/dist-packages/openplotterI2c/openplotterI2cRead.py.bak
 
2. Editar el archivo
sudo nano /usr/lib/python3/dist-packages/openplotterI2c/openplotterI2cRead.py
 
Buscar la línea:
conf2.set('I2C', 'sensors', str(i2c_sensors))
 
Justo antes agregar:
for sensor in i2c_sensors:
    if 'data' in i2c_sensors[sensor]:
        for d in i2c_sensors[sensor]['data']:
            if isinstance(d, dict) and 'object' in d:
                del d['object']
 
Debe quedar así:
for sensor in i2c_sensors:
    if 'data' in i2c_sensors[sensor]:
        for d in i2c_sensors[sensor]['data']:
            if isinstance(d, dict) and 'object' in d:
                del d['object']
 
conf2.set('I2C', 'sensors', str(i2c_sensors))
 
Guardar y salir.
 
3. Reiniciar el servicio
sudo systemctl restart openplotter-i2c-read.service
 
4. Verificar
 
grep "object at 0x" ~/.openplotter/openplotter.conf
No debería devolver ningún resultado.
 
5. Agregar los dispositivos 
 
 
Resultado
Después de aplicar el parche:

• ADS1115 funciona correctamente.
  
• Las rutas Signal K pueden configurarse normalmente.
  
• La interfaz I2C permanece estable.
  
• Los reinicios del servicio no corrompen la configuración.
  
• El archivo openplotter.conf permanece limpio.
  

 
Versiones afectadas
Detectado en:

• OpenPlotter I2C 4.2.0-stable
  
• Raspberry Pi OS Bookworm
  
• ADS1115 utilizando integración Signal K
  

 
Nota final
Este problema fue identificado analizando los cambios automáticos que realizaba openplotter-i2c-read sobre openplotter.conf después de cada reinicio. El origen resultó ser la escritura accidental de objetos Python temporales dentro del archivo de configuración permanente.