Sensor process get sleeped #6
Comments
|
Hello, If you want to receive notifications when a temperature reading is filtered, or can not be completed in the update interval (one of which I expect is your issue), make sure the notification duration is long enough for you to catch it. Either way you should see messages in the log if the plugin ran into issues - one of the two below: https://github.com/jangevaare/cbpi-OneWireAdvanced/blob/master/__init__.py#L185 https://github.com/jangevaare/cbpi-OneWireAdvanced/blob/master/__init__.py#L196 |
|
Yes , I have the last version.
No msg in the log since I have raised de logging to Errors. Got to many
Info msg from de Ui.
Will change yours to Error level.
Any way that don't cause a while() freeze.
I suspect some exception ocurred after a long time running. Uptime is 8
days.
El El mié, 11 de jul. de 2018 a las 15:56, Justin Angevaare <
[email protected]> escribió:
… Hello,
Are you using the latest version? The most recent commit a couple months
ago, bdf93b0
<bdf93b0>
did away with initiating a subprocess (within the plugin anyways) for
getting a temperature reading. I can't speak to the threads CBPi may or may
not implement beyond the scope of this plugin however.
If you want to receive notifications when a temperature reading is
filtered, or can not be completed in the update interval (one of which I
expect is your issue), make sure the notification duration is long enough
for you to catch it. Either way you should see messages in the log if the
plugin ran into issues - one of the two below:
https://github.com/jangevaare/cbpi-OneWireAdvanced/blob/master/__init__.py#L185
https://github.com/jangevaare/cbpi-OneWireAdvanced/blob/master/__init__.py#L196
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4bcRNFSAQO9q1s21sJe8xSqwaw7P9pks5uFkplgaJpZM4VLke0>
.
|
|
The plugin only stores a single "last temperature" between loops, and a "warning count" so there's nothing in it that would change with a long running duration (if you find different in the code, let me know, but it's a pretty simple plugin). I can't speak to the overall reliability of CBPi or your wiring of DS18B20 sensors. In my experience communication with these sensors is very sensitive to electromagnetic interference, and for the high reliability you are looking for it is essential that best practices are used for your control panel and sensors. Anyways, turn on the logging for this plugin if you're trying to narrow down your issue - I hope that can help. For the number of sensors you have you may also have to increase the update interval as well. |
|
Yes, I have raised the interval to 15s . Make no sens on a 60L fermenter
any lower than a minute anyway.
My installation is anything but optimal. The CBPi is next to the Kettles
and the ferneters are 20m away.
To make thing worst one of the pumps in the kettle have a VFD that when
running pops a lot of warnings from your plug in.
This is not critical because it runs a short time and only the brewing day.
Will keep you posted.
El jue., 12 jul. 2018 a las 10:55, Justin Angevaare (<
[email protected]>) escribió:
… The plugin only stores a single "last temperature" between loops, and a
"warning count" so there's nothing in it that would change with a long
running duration (if you find different in the code, let me know, but it's
a pretty simple plugin). I can't speak to the overall reliability of CBPi
or your wiring of DS18B20 sensors. In my experience communication with
these sensors is very sensitive to electromagnetic interference, and for
the high reliability you are looking for it is essential that best
practices are used for your control panel and sensors.
Anyways, turn on the logging for this plugin if you're trying to narrow
down your issue - I hope that can help. For the number of sensors you have
you may also have to increase the update interval as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4bcevwkUV2uk3nx8aDghRNRBdowVwvks5uF1U0gaJpZM4VLke0>
.
|
|
At 15 seconds I wouldn't think you'd have any issues. I thought maybe you were <2 seconds, as some people try to push it as far as they can this way. I use a VFD with my system as well and it gave me a lot of temperature sensor issues at first. I had to address that with an EMI filter and better shielding. Now everything is good on my end. BTW: I actually don't use CBPi anymore - I use a custom dashboard made with node-red . |
|
I'm going to close this - feel free to reopen if you have reason to believe it's an issue with this plugin's code. Hope you've managed to sort out! |
|
No more problems with 15s refresh.
Any way will add a hold option to be used while rotating logs.
El El mié, 25 de jul. de 2018 a las 16:00, Justin Angevaare <
[email protected]> escribió:
… I'm going to close this - feel free to reopen if you have reason to
believe it's an issue with this plugin's code. Hope you've managed to sort
out!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4bcdJMEwxniIbkvAEYWaKhXlFHquzdks5uKMBTgaJpZM4VLke0>
.
|
|
I don't know how to reopen this. curl -X POST http://10.9.0.109:5000/api/sensor/1/action/init |
|
I'm sorry, I'm stumped as to what this could be. I don't see anything within the plugin code that would result in this - pretty basic plugin. If it is software, I would wager on it being an issue with CBPi itself, otherwise I'd guess intermittent hardware issue. Have you looked to see if there's any log messages? This plugin does send some messages to the app logger if it encounters problems. Have you tried the standard onewire plugin? Do you have the same issues with it? That would be my next suggestion. |
|
Yes, have put standard 1W plugin and have 1k or 2k spikes temps from time
to time.
The ones I want to filter ;)
Obvious 1 bit error in tx.
The stranger is that the errors are on the nearest probes.
El jue., 23 ago. 2018 a las 14:28, Justin Angevaare (<
[email protected]>) escribió:
… I'm sorry, I'm stumped as to what this could be. I don't see anything
within the plugin code that would result in this - pretty basic plugin. If
it is software, I would wager on it being an issue with CBPi itself,
otherwise I'd guess intermittent hardware issue.
Have you looked to see if there's any log messages? This plugin does send
some messages to the app logger if it encounters problems.
Have you tried the standard onewire plugin? Do you have the same issues
with it? That would be my next suggestion.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4bcZGP5rEQhuiqF54OgDau8uvDgoFBks5uTuYxgaJpZM4VLke0>
.
|
|
Will add lot of debug messages .
If it is a hardware problem should give error but not cancel.
Other option is a background task that check and restart the sensor
El 23 ago. 2018 14:36, "Eduardo Spremolla" <[email protected]> escribió:
… Yes, have put standard 1W plugin and have 1k or 2k spikes temps from time
to time.
The ones I want to filter ;)
Obvious 1 bit error in tx.
The stranger is that the errors are on the nearest probes.
El jue., 23 ago. 2018 a las 14:28, Justin Angevaare (<
***@***.***>) escribió:
> I'm sorry, I'm stumped as to what this could be. I don't see anything
> within the plugin code that would result in this - pretty basic plugin. If
> it is software, I would wager on it being an issue with CBPi itself,
> otherwise I'd guess intermittent hardware issue.
>
> Have you looked to see if there's any log messages? This plugin does send
> some messages to the app logger if it encounters problems.
>
> Have you tried the standard onewire plugin? Do you have the same issues
> with it? That would be my next suggestion.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#6 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AK4bcZGP5rEQhuiqF54OgDau8uvDgoFBks5uTuYxgaJpZM4VLke0>
> .
>
|
|
If you are inclined to try this again @lalo-uy , I created a new branch (untested), that puts the temperature reading function in a try block. https://github.com/jangevaare/cbpi-OneWireAdvanced/tree/trycatch |
|
OK, will do it a run and keep you posted |
My setup consist of 8 DS18B20 on a bus.
For a second time this week a sensor process keep sleeped while the rest of the app runs ok.
Not the same sensor.
The sensor is readable on the filesystem.
You can see in the log that it stop updating al 15:33
Upon restart goes ok.
2018-07-10 15:31:13,6.0
2018-07-10 15:31:14,6.0
2018-07-10 15:31:22,5.937
2018-07-10 15:32:08,6.0
2018-07-10 15:32:24,5.937
2018-07-10 15:32:34,5.937
2018-07-10 15:33:03,5.937
2018-07-10 15:33:09,6.0
2018-07-10 15:33:21,6.0
2018-07-10 15:33:40,5.937
2018-07-10 15:33:52,6.0
2018-07-11 14:11:04,-0.375
2018-07-11 14:11:12,-0.375
2018-07-11 14:11:20,-0.375
2018-07-11 14:11:28,-0.375
2018-07-11 14:11:36,-0.375
2018-07-11 14:11:44,-0.375
2018-07-11 14:11:52,-0.375
2018-07-11 14:12:00,-0.375
2018-07-11 14:12:08,-0.375
Is there a way to check the sleeped threads ?
The text was updated successfully, but these errors were encountered: