So I posted last week in regards to my dual WSM setup and then posted that Stoker had told me to clear the DB when the fans and probes would 'criss-cross' such that fan 1 on wsm 1 was being controlled by the pit probe on wsm 2.
Well - I did a dual test run this weekend and I cleared the db and everything looked good on the stoker web page - everything was associated properly and working well....until...
I started working with Stokerlog. The minute I set the hi/low temps for the fire probes and temps for the food probes etc - the probes 'criss crossed' immediately after stokerlog wrote to the stoker.
I shrugged it off the first time and closed Stokerlog, re-setup everything under the web page on the stoker - restarted StokerLog and when it wrote the data for hi/low and food temps - bam - switched again.
So after setting it all up one more time - I never allowed Stokerlog to write to the Stoker and did all settings under the web page and let Stokerlog just read and monitor - it worked perfectly for the whole cook.
Any thoughts or is this a known issue with StokerLog and dual cooker setups?
Well - I did a dual test run this weekend and I cleared the db and everything looked good on the stoker web page - everything was associated properly and working well....until...
I started working with Stokerlog. The minute I set the hi/low temps for the fire probes and temps for the food probes etc - the probes 'criss crossed' immediately after stokerlog wrote to the stoker.
I shrugged it off the first time and closed Stokerlog, re-setup everything under the web page on the stoker - restarted StokerLog and when it wrote the data for hi/low and food temps - bam - switched again.
So after setting it all up one more time - I never allowed Stokerlog to write to the Stoker and did all settings under the web page and let Stokerlog just read and monitor - it worked perfectly for the whole cook.
Any thoughts or is this a known issue with StokerLog and dual cooker setups?