Servoblaster is blocking Onewire at GPIO4 on RPi 3

[amigatommy]

Since updating my Pi and changed everything to devicetree functionality, i have a problem:
As long as servoblaster is active (PWM for LED dimming in a fishtank, from 8 am to 8 pm) the onewire Interface on GPIO4 is no more working. In this time i have no temperature readings from my DS18B20, it is not working and not present for the software. After 8 pm the onewire interface works normaly, now servoblaster is at 0% dimming. When its 8 am, no onewire measuring to 8 pm. I tried with the --pcm option, no luck. Defined in /etc/init.d/servoblaster is:

OPTS="--min=0% --max=100% --cycle-time=2000 --p1pins=11"

Whats wrong there, i dont see the problem, can you help me please ?

[amigatommy]

Sorry for the doublepost Stuart, continuing in richardghirst's repository !
Can you have a look at it please ?
Thanks a lot !
Greetings Thomas

[srcshelton]

Sorry, I've only just seen this!

Using the various 'pins' options should allow the remapping of GPIOs without disrupting other uses, and you're right that setting --p1pins=11 should avoid GPIO4.

Could you build the servodebug binary (gcc -Wall -O2 -o servodebug servodebug.c), run this, and then invoke servodagain with your --p1pins parameter, and confirm whether GPIO4 seems to be being updated?