Situation:
- I have one working setup on RPI4B , RooDial V1.30 with Microsoft surface dial (lot2044)
- Bought 2 additional RPI4B + 2 additional Microsoft surface dails but cannot get last step, bluetooth pairing,working!
- Have bought 4 licences RooDail
Did a lot of experiments yesterday to tackle the problem
“Situation B” was requested todo by @DrCWO but didn’t succeed.
Summary: (my observations)
1 V1.31 after “reset to factory defaults” WIFI RPI4 is lost, never comes back online!
2 Repeatablity is sometimes low when I repeat exact same steps on fresh RPI4 + fresh SD-card image.(reaction is different)
3 Microsoft surface dail (lot 2044) versus (lot2048) seems NOT a lead to the problem!
4 Bluetooth pairing step put status after few seconds to “sleeping” in Roon (Microsoft dial never pairs)
5 Checked the two non pairing Microsoft surface dials with Windows 10 they pair and work!! (than unpaired them in W10)
6 My third Microsoft surface dail died during the experiments.( get NOT getting it to pairing mode anymore)
7 After ALL experiments I went back to a fresh image of V1.30 and succesfully to connected again to my one and only working setup!
Because I have one working set-up I took it as starting point.(= Situation A)
"Situation A" : RPI4B + RooDial V1.30 with WORKING Micrsoft surface dail (lot 2044) **
- This set up is the one and only setup that works!!
- Visit http://IP_adress_RPI4
- “Reset to Factory defaults” (I didn’t expect this option to appear because of V1.30)
- Start Roon ==> enable RooDial
- Took second MS-Dail (lot2048) put it to pairing mode
- Pairing continues forever NO connect!
- Removed battery MS-dail shortly to stop pairing.
- Visit http://IP_adress_RPI4
- “Reset to Factory defaults”
- Start Roon ==> enable RooDial
- Took my old working MS-Dail (lot2044) put it to pairing mode
- Pairing succeeded after few second " paired"
- Visit http://IP_adress_RPI4
- “Reset to Factory defaults”
- Start Roon ==> enable RooDial
- Took my second MS-Dail (lot2048) put it to pairing mode
- Pairing continues forever NO connect!
“Situation B”: RPI4B + RooDial V1.31 on fresh SD-Card image
- Connected to Rooextend network → with key:1234567890
- Visit http://10.0.0.5 → selected my “Audionet” network
- Start Roon ==> enable RooDial
- Took my old working MS-Dail (lot2044) put it to pairing mode
- Status in ROON changed from “unpaired” → “Sleeping” within a few seconds??? (pairing doesn’t succeed) ** point4 summary**
- Visit http://IP_adress_RPI4
- “Reset to Factory defaults”
- The RPI4 disappear in my WIFI network and NEVER comes online again!! “point 1 summary”
- RPI4 blinks in one second ritme, non visible in network → ENDs this experiment
Repeated steps of “Situation B” with fresh SDcard image, SAME results V1.31 not working for me! (it disconnected from WIFI after “Reset to factory defaults”)
“Situation C”: RPI4B + RooDial V1.31 on fresh SD-Card image
- Connect LAN cable to RPI4 (difference with previous Situation B)
- Start Roon ==> enable RooDial
- Took my second MS-Dail (lot 2048) put it to pairing mode
- Status in ROON changed from “unpaired” → “paired” (for 1st time MS-Dail lot 2048 works!!) “point 3 summary”
For repeatibility I repeated “Situation C” with a fresh SD-card image:
“Situation D”: RPI4B + RooDial V1.31 on fresh SD-Card image
- Connect LAN cable to RPI4
- Start Roon ==> enable RooDial
- Took my second MS-Dail (lot 2048) put it to pairing mode
- Status in ROON stays on 'unpaired" and pairing continues WITHOUT success. “point 2 summary”
“Situation C” and “Situation D” should have given SAME results but it didn’t (I’am Lost)
“Situation E” : RPI zero W, Roodial V1.30 + Microsoft surface dial (lot 2048)
- I was not able to get my WIFI connected to this “RPI zero W” so gave it away to a friend.
- At his place :
- Connecting to his WIFI worked.
- Pairing in ROON worked (with Microsoft surface dail (lot 2048 !!) “point 3 summary”
- Working setup at his place.
Finally I went back to V1.30 with fresh SD-card image and first working Microsoft surface dial and that is still the ONLY one i get to work.
Hope this helps debugging the issue.