jamorham/python-usb-wixel-xdrip

xDrip wixel connected via usb for "wifi" wixel mode

python-usb-wixel-xdrip's Issues

List index out of range

I'd say around 1/4 of times I run the screen command and follow the script output I see a python list index out of range error.

It's a bit of a concern because I don't feel confident that the script is running after a reboot, so end up having to check it on each of my 3 USB Wixel devices.

0 Wixels found on Pi Zero

I have a Pi3 set up correctly (thanks!), and my Pi Zero just arrived. Running the install forusb.sh I get an error when it comes to flash the Wixel

Firmware ready
Install to USB attached wixel now? y/n : y
0 Wixels found.
Error: No Wixels found.

Could this be Pi Zero related? I have my Wixel connected via a USB hub. Unfortunately I need this as it's also my ethernet port. Ethernet and other USB devices work fine so I don't think it's the hub.

I connected the Wixel to another computer with the pololu utility and it recognised fine, so I assume my USB cable is fine. I wiped it, but still got the same issue back on the Pi Zero. It's not the Wixel as I have had that one working on my Pi 3.

Rasperry Pi loose contact with the Wixel

I have a Raspberry Pi 2 with 4 USB-ports. After a few hours/days the python sctipt loose contact with the Wixel (the Wixel collects signals, and the python script acknowledge requests from the phone). The scrips does not get any values from the Wixel, so I guess it has lost contact with the Wixel.

In your code you mention that the Wixel reboots and comes back as a new device. Have you written the code for the old Raspberry Pi with 2 USB-ports? Should I change the code to include all 4 USB-ports?

sometimes the wixel reboots and comes back as a different

        # device - this code seemed to catch that happening
        # more complex code might be needed if the pi has other
        # ACM type devices.

        if (os.path.exists("/dev/ttyACM0")):
            ser = serial.Serial('/dev/ttyACM0', 9600)
        if (os.path.exists("/dev/ttyACM1")):
            ser = serial.Serial('/dev/ttyACM1', 9600)

Color coded light indicator -script and hardware, suggestion?

On the basis of the experience with this great software that is so usefull in everyday life, as well as following advanced setup - smart home example from the author @jamorham https://jamorham.github.io/ I would like to ask for the suggestion about color coded light indicator, a RPi script that is good in combination with python-usb-wixel-xdrip and hardware (lights, leds) for RPi.
Edit: To clear possible misunderstandings, I forgot to emphasize that the script shoul be able to read BG data from NS or directly from xDrip+.
Thank you in advance.

No data for long periods

Hello, ant thank you for all your efforts with your software. Helps us a lot as family w/a 3yr old with T1D

I am having some problems getting this to work, and any help would be appreciated:

Hardware:

• Pololu Wixel (tried 2 separate wixels)
• Raspberry PI 3 Model B
• 1 x xDrip+ App running on Android x86 Computer
• 1 x xDrip+ App running on Android 5.1.1 Phone

I have followed the guide as best I can, and I get data to the xDrip applcation(s), but more often than not there is no data received. I can have data for 1h max (usually a lot less), but then it drops out for several hours, before coming back for a few readings again. It is the same readings showing on both xDrip app units

Running 'sudo screen -r wixel' I see that the xDrip apps are connected. What type of info would be usefull for debugging?

It is not a range-issue, as I did testing during evening & night w/my son sleeping 2m from the wixel. Also get some reading when he is on a different floor in the house, which indicates range is ok. Reboot of RPi doesn't fix this either. Behaviour is always the same.

Additional Info:

• I get the exact same behaviour when using the NodeMCU WiFi wixel
• Using Dexcom G4 + Animas Vibe

Autoinstaller does not accept 6-digital G5 transmitter ID?

@jamorham Thanks for sharing this code!

I'm trying to run sh forusb.sh for the first time, and the auto-installer returns an error when I enter my G5's transmitter ID, which is in the form ##ABCD:

Transmitter ID wasn't 5 characters long, this looks wrong - exiting

What's the trick? Should this line be edited to accept 6 digits?
https://github.com/jamorham/python-usb-wixel-xdrip/blob/master/forusb.sh#L73

Alerts make no sound - Only vibrate

Since moving from xDrip to xDrip+ my low alerts are not audible. I have tried changing the alert volume in the system, and the sound it uses. I missed 2 lows/rebounds overnight as a result.

Any ideas?

Trouble getting this running on my Fedora Machine

I have a Fedora 23 based NAS (Amahi). I want to get the script up and running and am having an issue.

With a new Wixel I get the below error when I run sh forusb.sh

Configuring source code for USB use

Please enter your dexcom transmitter number, eg: ABCDE: 680C4

Reconfiguring...

Restoring original from dexdrip.orig

Compiling wixel firmware: PLEASE WAIT

Compiling apps/dexdrip/dexdrip.rel
/bin/sh: sdcc: command not found
Makefile:181: recipe for target 'apps/dexdrip/dexdrip.rel' failed
make: *** [apps/dexdrip/dexdrip.rel] Error 127
Firmware failed to build :(

I thought maybe I could set up the Wixel on my Pi and load the python script in Fedora, but since the compiling is combined with the script I'm a bit stuck.

Any ideas?

Info

Could you please give me a bit more detail as to how this works?

Does the Xdrip app poll the Pi every so often or does the wixel contact the Pi and the ipconfig settings in xdrip are just to say which hosts are allowed?

What is the purpose of the remote hosts?

Just got set up thanks! xDrip+ Doesn't get readings from .local (mDNS)

I see data being collected in my Raspberry Pi console. I can also SSH from OSX to the Pi at raspberrypi.local but when I put raspberrypi.local:50005 in my receiver field on the android app, nothing happens.

I am using an xBridge also so I have selected "Wifi Wixel + xBridge Wixel" in my data source. When I'm close to the xDrip I get data. When I turn it off I get nothing from the RaspPi.

Any ideas?