Inputs stop registering after some time, pyro5 error

Mycodo Mycodo Issue/Bug
1

Everything was functioning correctly, then inputs seems to stop reading. Daemon log attached.

2025-02-27 21:10:19,605 - INFO - mycodo.controllers.controller_conditional_e7f6c8b3 - This INFO log entry will appear in the Daemon Log
2025-02-27 21:10:20,191 - ERROR - mycodo.controllers.controller_conditional_e7f6c8b3 - Exception executing Run Python Code
Traceback (most recent call last):
File “/opt/Mycodo/mycodo/controllers/controller_conditional.py”, line 183, in check_conditionals
self.conditional_run.conditional_code_run()
File “/opt/Mycodo/mycodo/user_python_code/conditional_e7f6c8b3-1f6c-46fa-8e6e-67c5e0ee4a47.py”, line 27, in conditional_code_run
measurement = self.condition(“d73a3f20”) # Replace ID with correct Conditional ID
File “/opt/Mycodo/mycodo/controllers/base_conditional.py”, line 78, in condition
return self.control.get_condition_measurement(full_cond_id)
File “/opt/Mycodo/mycodo/mycodo_client.py”, line 190, in get_condition_measurement
return self.proxy().get_condition_measurement(condition_id)
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/client.py”, line 510, in call
return self.__send(self.__name, args, kwargs)
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/client.py”, line 268, in _pyroInvoke
data = serializer.loads(msg.data)
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/serializers.py”, line 290, in loads
return self.recreate_classes(serpent.loads(data))
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/serializers.py”, line 256, in recreate_classes
return self.dict_to_class(literal)
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/serializers.py”, line 309, in dict_to_class
return super(SerpentSerializer, cls).dict_to_class(data)
File “/opt/Mycodo/env/lib/python3.9/site-packages/Pyro5/serializers.py”, line 235, in dict_to_class
raise errors.SerializeError("unsupported serialized class: " + classname)
Pyro5.errors.SerializeError: unsupported serialized class: urllib3.exceptions.NewConnectionError

2

Sorry some more details.
Inputs are:
Sht31 i2c.
Output state x2.
All three do not seem to be collecting any data

3

I do read measurements in the debug daemon log, but nothing shows on love measurements page or graphs.

2025-02-27 21:49:25,983 - DEBUG - mycodo.inputs.mycodo_output_state_d836c5bf - Output State: on
2025-02-27 21:49:26,012 - DEBUG - mycodo.controllers.controller_input_d836c5bf - Adding measurements to InfluxDB with ID d836c5bf-a87d-492a-af1a-f077cf3a8c1f: {0: {‘measurement’: ‘boolean’, ‘unit’: ‘bool’, ‘value’: 1.0, ‘timestamp_utc’: datetime.datetime(2025, 2, 27, 19, 49, 25, 987593)}}
2025-02-27 21:49:31,640 - DEBUG - mycodo.controllers.controller_input_b145a803 - Adding measurements to InfluxDB with ID b145a803-2c24-4ffd-bcb1-ee9a78bd42f3: {0: {‘measurement’: ‘temperature’, ‘unit’: ‘C’, ‘value’: 26.348516060120545, ‘timestamp_utc’: datetime.datetime(2025, 2, 27, 19, 49, 31, 579409)}, 1: {‘measurement’: ‘humidity’, ‘unit’: ‘percent’, ‘value’: 75.4665445944915, ‘timestamp_utc’: datetime.datetime(2025, 2, 27, 19, 49, 31, 579479)}}
2025-02-27 21:49:32,992 - DEBUG - mycodo.inputs.mycodo_output_state_f95ac6fc - Output State: off
2025-02-27 21:49:33,011 - DEBUG - mycodo.controllers.controller_input_f95ac6fc - Adding measurements to InfluxDB with ID f95ac6fc-39fe-4ec4-a352-d4f374889ad3: {0: {‘measurement’: ‘boolean’, ‘unit’: ‘bool’, ‘value’: 0.0, ‘timestamp_utc’: datetime.datetime(2025, 2, 27, 19, 49, 32, 998713)}}

Screenshot_20250227_214204_Chrome
Screenshot_20250227_214204_Chrome1080×2400 173 KB

4

How often does this occur?
What hardware is this running on?
What power supply is providing power?
What kind of storage device is the OS on?

5

Only started a few days ago, since then I havent been able to register any inputs. Wiped the whole disc, reloaded os, updated, reinstalled, then it worked again for a short while, then stopped again.
Power supply from a 5V supply
RPi 2B w bullseye OS on a 32g SD

6

It states in the readme on github that a Pi 2 is not recommended. You will find cryptic software issues running underpowered hardware. It could also be a low-performing SD card that cannot keep up with the read/write speeds necessary for the software to run properly.

7

Okay thank you
I missed that somehow. Was running an older mycodo version till relatively recently untill it starting giving issues, then updated without going through the readme completely. Thanks for that, will change to my rpi3. Agaim thanks for your amazing work and support.