10-17-2021, 04:41 PM
I assumed the tank temp was fine until you enabled the second port, I find that fishy as well, the programs definitely dosing what it should.
If I remember, you had issue where one sensor would knock them both out and a restart was required, is that right?
My hope/thought is that wouldn't happen any more based on how I manage the sensors. If it's not there it doesn't attempt to read it which could have caused it to hang. Still better to run two 1-wire buses as you have though.
To make my auto system for the ds18b20 I needed to edit some system files on the Pi related to 1-wire. You may or may not have noticed, in reef-pi if you plug in a sensor it can take up to 10 seconds to be detected, if you unplug a sensor reef-pi might report that sensor available for up to 2 minutes. This is all based on the Pi. I found direction to make some changes and now the Pi updates the /sys/bus/w1/devices/ location every 1-3 seconds. It finds new sensors in 1 second and in 3 seconds or less it detects any missing.
After I made that change I discovered quite a few more errors when trying to read sensors, sometimes the 1-wire bus is gone, maybe a sensor or bad data from a sensor.
In the database go to the "errors" table. You could see a variety of errors related to ds18b20, during the read process there's 4 checks and I've seen them all fail at one point or another. Every time something happens the sensor will disappear on the home page as I hide it because in theory it's not available so no point in showing.
So it is common to see 1 or all sensors randomly disappear from the dashboard and then reappear. I am going to make it so it needs to be gone a couple read cycles before it actually disappears on dashboard.
The important thing to watch is the min / max, those are captured every reading so nothing gets by it. If a max of 108 was shown that means that value was used through-out the system, that's why it's important to use a delay when activating macros based on temperature. If a bad reading like that got through it wouldn't cause any ill effects as the custom rule would need say 10 seconds of a valid reading. I run 3 sensors all on the same bus and haven't seen a bad reading but doesn't mean it can't happen.
If I remember, you had issue where one sensor would knock them both out and a restart was required, is that right?
My hope/thought is that wouldn't happen any more based on how I manage the sensors. If it's not there it doesn't attempt to read it which could have caused it to hang. Still better to run two 1-wire buses as you have though.
To make my auto system for the ds18b20 I needed to edit some system files on the Pi related to 1-wire. You may or may not have noticed, in reef-pi if you plug in a sensor it can take up to 10 seconds to be detected, if you unplug a sensor reef-pi might report that sensor available for up to 2 minutes. This is all based on the Pi. I found direction to make some changes and now the Pi updates the /sys/bus/w1/devices/ location every 1-3 seconds. It finds new sensors in 1 second and in 3 seconds or less it detects any missing.
After I made that change I discovered quite a few more errors when trying to read sensors, sometimes the 1-wire bus is gone, maybe a sensor or bad data from a sensor.
In the database go to the "errors" table. You could see a variety of errors related to ds18b20, during the read process there's 4 checks and I've seen them all fail at one point or another. Every time something happens the sensor will disappear on the home page as I hide it because in theory it's not available so no point in showing.
So it is common to see 1 or all sensors randomly disappear from the dashboard and then reappear. I am going to make it so it needs to be gone a couple read cycles before it actually disappears on dashboard.
The important thing to watch is the min / max, those are captured every reading so nothing gets by it. If a max of 108 was shown that means that value was used through-out the system, that's why it's important to use a delay when activating macros based on temperature. If a bad reading like that got through it wouldn't cause any ill effects as the custom rule would need say 10 seconds of a valid reading. I run 3 sensors all on the same bus and haven't seen a bad reading but doesn't mean it can't happen.