iSpindle - DIY Electronic Hydrometer

[BreeBrew]

From the brewfather documentation:
Make sure your iSpindel reports gravity in Plato (it will be converted to SG) and temperature in Celcius. Add [SG] to the name of your iSpindel if you use SG based formula. If the gravity is displaying 1.004 in Brewfather you are using the wrong formula, use the formula that reports in Plato or use the tag above.

If you get no gravity reported: Check that the formula is not too long.(as of 6.5? of the iSpindel firmware it is 250 characters; what the max. length is in brewfather I don't know), There's a max character length. Instead of "tilt*tilt*tilt" put *tilt^3"(instead of what I told) etc.
If it still fails: Upgrade to the latest iSpindel firmware or try to use the second degree polynomial formula for your iSpindel.

 

[NSMikeD]

From the brewfather documentation:
Make sure your iSpindel reports gravity in Plato (it will be converted to SG) and temperature in Celcius. Add [SG] to the name of your iSpindel if you use SG based formula. If the gravity is displaying 1.004 in Brewfather you are using the wrong formula, use the formula that reports in Plato or use the tag above.

If you get no gravity reported: Check that the formula is not too long.(as of 6.5? of the iSpindel firmware it is 250 characters; what the max. length is in brewfather I don't know), There's a max character length. Instead of "tilt*tilt*tilt" put *tilt^3"(instead of what I told) etc.
If it still fails: Upgrade to the latest iSpindel firmware or try to use the second degree polynomial formula for your iSpindel.

I did all that except I haven't been able to determine if my iSpindel is reporting in Plato.



bummer. It reported to Brewfather at 9;56am this morning our s as of 10:43 I have no update with the internal setting of 900.


This has been a huge headache all because of some esoteric wifi setting that prevents such a simple process (connecting to the wifi) to occur. Good grief what a waste of money so far.


Edit note. I cannot connect using my home wifi which I looked at several times an found no unusual settings. I can connect with the iPhone personal hotspot for an initial reading but it will not update - which sort of makes this useless. well I am going to increase my batch size a bit to account for hydrometer and refractometer readings

 

[BreeBrew]

except I haven't been able to determine if my iSpindel is reporting in Plat

Where did you get the formula from?
What version of the iSpindel firmware do you use?
Reporting only once could indicate that there is a hardware problem where it can't get out of deep sleep for some reason. Google: iSpindel deep sleep

 

[NSMikeD]

Where did you get the formula from?
What version of the iSpindel firmware do you use?
Reporting only once could indicate that there is a hardware problem where it can't get out of deep sleep for some reason. Google: iSpindel deep sleep

I used the online formula iSpindel Calibration


I'm recharging right now, but I did update the firmware

 

[BreeBrew]

I used the online formula iSpindel Calibration

You can actualy specify the gravity units there, default is SG, if you did not change that your formula is SG and you should add [SG] to the name of the iSpindel in order to let brewfather know the iSpindel is reporting SG.

 

[gello22]

How do you measure the pressure? I have wondered about those tyre sensors that relay to the car but they only turn on with movement I think. My fermenter isn't rolling about.
If your thermowell is at the bottom and Ispindel at the top could be a temperature difference especially as a couple of fahrenheit isn't that much.
I must set up a brewpi or equivalent and get this extra info and control you are garnering.

I had a 5v 100psi stainless sensor from an engine project I never did uhm 20 years ago. The range is not ideal but with the proper RC filter I get a decent reading from the brewpiless. It is just teed into the spunding valve connection. Took a while to find the fittings to go from 8mm tube to 1/4" male pipe.

 

[DuncB]

@gello22 I see that's a good way of doing it teed off the spunding valve. I see now that there are pressure sensing and even autospunding options on brewpiless but I've not seen any real world talk about them.

 

[HarryB]

Repeatidor + iSpindel - loss of reports..
I heard a hint of a suggested update for one or the other, which fixes the issue, but failed to make a note of it.

Ispindel worked fine reporting direct to my router, never problem. I then built a repeatidor, tested it, it seemed OK and gave me more options for data display, as well as a local display on the unit. Mid way through my first brews, it stopped reporting, so I then ran a 'dry test' with the two just a couple of feet apart. The dry test soon failed, so I restarted it and it ran for 3 weeks, reporting every 10 minutes, before again failing. At the point of failure, the battery report was 4.08v, so not that.

It seems when this occurs, that the Repeatidor goes into a state of frequently rebooting - its display goes blank, then shows signs of a reboot, gets an IP from my router, but fails to connect to the iSpindel for data. Even at two feet apart, I notice that the full strength connection to the iSpindel (****), can sometimes drop to just one *.

Has anyone heard of the fix please?

 

[DuncB]

Hi @HarryB
I've made my repetidor ( two in fact ) and find that it just gives up after a while. I have to reboot to get it to reconnect and start working again. It shouldn't be my network as the repeater is a separate network really ( brewpiless). I did dialogue with the developer and my comments are on the repeater page. He says all fine and that it is release 2 of his software ( whatever that means ) and not had problems with wifi dropout.
I'm going to address the issue by turning one of the esp8266 boards into a NAT router that can boost signal and interface with my network using martin-ger/esp_wifi_repeater then my ispindel signal should get back to the network and then get into brewpiless device as well.

Ideally this software and some display software -+ brewpiless all on the one esp8266 although that might be demanding too much memory etc from this device.
I did notice that after several days of signalling from my ispindel to the repeater that the blue light was on all the time instead of only flashing when it sends a signal. I'm not sure why or if this is contributing.

Do you do a hard reset of the repeater using the button or unplug and restart to get it working again.
Are you logging during this dry test and if so have you looked to see if the memory area for this gets filled up and causes a problem perhaps the bootloop?

 

[HarryB]

Ideally this software and some display software -+ brewpiless all on the one esp8266 although that might be demanding too much memory etc from this device.
I did notice that after several days of signalling from my ispindel to the repeater that the blue light was on all the time instead of only flashing when it sends a signal. I'm not sure why or if this is contributing.

Do you do a hard reset of the repeater using the button or unplug and restart to get it working again.
Are you logging during this dry test and if so have you looked to see if the memory area for this gets filled up and causes a problem perhaps the bootloop?

Have you a URL for the repeater updated firmware?

I don't think it's a memory issue (bootloop), because it ran continuously in my dry run much longer than my actual brew takes. I have never seen the blue LED remain on in my iSpindel. I don't think it is a network access problem, because even when iSpindel on its own, in an actual brew, it never missed a single report. When I ran the dry test, both items were in the same room as the router. My brews (wine) are usually finished within 10 days, whereas the dry run ran for more than double that before it stopped reporting - both at a 10 minute report interval. The run time to failure also seems to be random.

I reboot the repeater, by unplugging it. I must admit I did notice a problem when initially trying to get both working together, when starting a brew - I not sure what works best, booting the iSpindel or the repeater up first. My usual method is to mess about rebooting them in the dry, until I get at least two reports, then pop the iSpindel in the brew.

 

[DuncB]

@HarryB
Just noticed the bit about other software. I just used the software on github that the page linked to. I assume he has removed the version 1.

 

[HarryB]

Too be honest, I don't know what the version number I installed was - I have since bought myself a new laptop and my new one does not have a copy of the fimrware on it, to be able to check which version I installed. Thanks, I will try installing that 1.1 version and test again.

 

[DuncB]

@HarryB my software version says 4.0 so I'm not convinced.
There is something on the Gers site re the repeater for wifi only that mentions about power supply issues causing problems and I will update.

 

[HarryB]

I unfortunately managed to snap the socket off from the repeatidor, when trying to plug it into my USB to update it, so for now it has to wait until I have the patience to try to resolder it back in place.

I ought to have run some hot glue around the socket to help support it, before this - it is not the first one to give way under the strain of plugging and unplugging :-(

 

[HarryB]

I have just noticed that a new version V1.2 has appeared on the site, which seems to suggest it addresses the wifi issue.

 

[DuncB]

@HarryB
Well spotted, I even reinstalled the old one again a couple of days ago, I really should try and read better.
I'll load it up and see how it goes.
He'd even told me about it didn't he I just failed to follow the clues.

 

[DuncB]

Hi I have an issue with one Ispindel that seems to start reliably sending to brewspy and then after say 5 days it becomes less reliable in sending data. Sometimes going many hours or a day without sending any info and then gives up.
I thought that it was an issue with signal getting to the router, but have made a wifi relay ( access point ) as per martin-ger/esp_wifi_repeater with an esp8266 and that is in the ferment fridge.
I can detect the esp access point by the router and even log onto it so no problem of that signal getting out of the fridge. Another ispindel monitoring the keg fridge directly opposite is signalling the same wifi relay and is nearly faultless.
The problem spindel Voltage dropped from 4.1 V to 3.95v over 6 days sending every hour, signal strength seems to be in the - 81 to -89 level . Haven't had a reading for 2 days now and it hasn't sunk this time.

The keg fridge spindel 4.2v to 4.07v over the last 5 weeks sending every 45 minutes signal around -65 to - 77.

Seems strange the signal strength so low for the problem ispindel given that it is inches from the relay .

Is it possible I need to set the ispindels to have there own fixed ip?

Could the frequencies ( channels ) of the wifi networks be clashing not sure how to adjust that on the martin ger device.

Or could it be that the wifi module in the problem ispindel a bit naff.

Any ideas. I know that any question always brings a load of others.

I haven't calibrated the battery conversion factor on either battery due to a lack of a digital voltmeter that can do this. Something I think I need.
Thanks

 

[tonny]

Hi,
By it's nature (it sends data, no one connects to it), I do not think the ispindels needs an fixed ip.
But that being said, like everything i my network that is not an end user device, I do have it set to a fixed IP in the DHCP server.
I have one minor reasons to do so: I like to know where the are. But also one major: Control/Limit/block internet access.

I'm not very fond of repeaters unless the have at least two radio's (one used to talk to the real AP, the other to send out the SSID on an other channel)
I've seen cases where a WiFi client first connects to the 'real' AP just because it answers a little faster than the repeater. They might later switch the the repeater since it has a better signal. The ispindel however is already back to sleep by then You might try to see if the repeater can send out an different SSID and connect your ispindel to it.

//Tonny

 

[DuncB]

Hi,
By it's nature (it sends data, no one connects to it), I do not think the ispindels needs an fixed ip.
But that being said, like everything i my network that is not an end user device, I do have it set to a fixed IP in the DHCP server.
I have one minor reasons to do so: I like to know where the are. But also one major: Control/Limit/block internet access.

I'm not very fond of repeaters unless the have at least two radio's (one used to talk to the real AP, the other to send out the SSID on an other channel)
I've seen cases where a WiFi client first connects to the 'real' AP just because it answers a little faster than the repeater. They might later switch the the repeater since it has a better signal. The ispindel however is already back to sleep by then You might try to see if the repeater can send out an different SSID and connect your ispindel to it.

//Tonny

I think it's a bit more than a repeater based on this description.

"A full functional WiFi repeater (correctly: a WiFi NAT router)

This is an implementation of a WiFi NAT router on the esp8266 and esp8285. It also includes support for a packet filtering firewall with ACLs, port mapping, traffic shaping, hooks for remote monitoring (or packet sniffing), an MQTT management interface, simple GPIO interaction, and power management"

But the ispindel is set up to only connect to this access point ( which I have given a different name to is that SSID? ) in the configuration. The access point uses the main router for DHCP so i should find the MAC address of the ispindel and then define the fixed ip on the main router?

Bizarrely the ispindel fired out some data today after being quiet for 3 days but now quiet again.

 

[tonny]

which I have given a different name to is that SSID

Yes, SSID is commonly known as the wifi name

.....
"A full functional WiFi repeater (correctly: a WiFi NAT router)
.....
so i should find the MAC address of the ispindel and then define the fixed ip on the main router?
.....

No, if the repeater performs NAT (network address translation), it will have one IP address (which it got from the router) to talk to the home router, and will give a totally different IP address for your ispindel. NAT will 'hide' all devices from your home router. so your home router will see all traffic coming from the devices 'behind' your repeater (ispindel) as if it was generated by the repeater itself.

*IF* they are in the same network -lets say your home router uses 192.168.54.x addresses and your repeater also gives 192.168.54.x addresses to the ispindel, you will have issues.

So please make sure your home network and the repeater's AP are using different network addresses. (I would not recommend either of them to use 192.168.4.0/24 for that is used by the esp in config mode, and might cause network issues when you have multiple and put one in config mode)

 

[DuncB]

@tonny
Thank you, I will have to look at that and see what's going on. That could be the reason I'm having issues. Pretty sure the repeater might be on the .4.x/24 subnet .
I will investigate. Thanks again.

 

[Lalo_uy]

The esp can work on Station/Access point mode, with the station part getting ip by dhcp from the main router and the AP part on a different network (192.168.4.x/24 by default).

 

[DuncB]

Any advice please.
I have made several ispindel over the weekend and several in the past, but the latest build has an issue.

Appears to flash software via usb ( completes without errors ) but when I turn it on and then reset to get to ispindel access point I don't get the log in page. All I get is a Farylink_xxxx access point which I can't access.
Reading this thread it suggests this is due to the temp sensor not being functional either because broken or not soldered correctly .
I have tried 3 different temperature sensors and repeated reflashing after each but the response always the same.

Is there a way I can test the sensor / Sensors to check I haven't got a succession of duds?

How can I test the circuit to see if it's an attachment to the motherboard or a problem with the D1 mini?

I do have a multimeter and also have an esp8266 NodeMcu if that would help for the diagnosis of the temp sensor issue ( if that's the cause ).

Thought I was using the latest firmware for all of them and they have been fine.
Actually just found out there are updates, 6.6 and 7.0 but when I tried these on the misbehaving one I don't see the farylink AP just blue flashing light.
Returning to 6.5.1 again see the farylink AP.
Motherboard jeffrey 2.69.

Thank you

 

[Lalo_uy]

Flash it with the arduino temperature ds18b20 example. Just change pin fron 10 to 6. You should read the sensor in the terminal window.

 

[DuncB]

Flash it with the arduino temperature ds18b20 example. Just change pin fron 10 to 6. You should read the sensor in the terminal window.

Flash the D1 mini ?
Is it a solder job to move something connected to pin 10 to pin 6?
I have managed to load and use putty. Output said unable to read one wire ( temp sensor ) tried 2 more sensors and feel sure they can't all be duff.

I removed the D1 mini and replaced it and it all works.
The problem turned out to be with the D1 Mini and not the temp sensor.

So some lessons learnt here.

Now trying to decide whether I should upgrade firmware to 7.0 or 7.1

Seems scant information on github as to the gains I might get. Experts always assume that they are communicating to experts.

Thanks though.

 

[Lalo_uy]

The example expected the sensor on D10 and iSpindle have it on D6, so you have to modify the example , it is in the few first lines.

 

[Bluesfastduce]

I have to be missing something I just flashed my firmware 7.1.2 and when I try to connect to the network I see network micropython-d063d0 but its asking for a password. I cant find a default passwords.

never mind I found it

 

[DuncB]

Yes, SSID is commonly known as the wifi name

No, if the repeater performs NAT (network address translation), it will have one IP address (which it got from the router) to talk to the home router, and will give a totally different IP address for your ispindel. NAT will 'hide' all devices from your home router. so your home router will see all traffic coming from the devices 'behind' your repeater (ispindel) as if it was generated by the repeater itself.

*IF* they are in the same network -lets say your home router uses 192.168.54.x addresses and your repeater also gives 192.168.54.x addresses to the ispindel, you will have issues.

So please make sure your home network and the repeater's AP are using different network addresses. (I would not recommend either of them to use 192.168.4.0/24 for that is used by the esp in config mode, and might cause network issues when you have multiple and put one in config mode)

Worked out the dire performance issue when I got the ispindel out of the brew at the weekend.

It was set to my original network so struggling to get signal out of fridge and to the hub. The relay sitting next to it was being ignored. I think I didn't press save when I changed the SSID and password.

Now working great to relay and happy with the new firmware.

 

[beernoobs]

Hi everyone,

I found this project very interesting. I would like to know if it is possible to use either a M5Stick5 or ESP-watch than building everything from scratch. M5Stick has 6 -axis IMU sensor, ESP32 (Wifi+bluetooth), integrated battery charger, grove sensor socket to integrate temparature sensor, OLED screen. Everything included it is just less than $15. I have the M5Stick5, so would appreaciate if anyone of you done this before guide me on how to use that as a base.
m5stack/M5StickC

 

[DuncB]

Hi everyone,

I found this project very interesting. I would like to know if it is possible to use either a M5Stick5 or ESP-watch than building everything from scratch. M5Stick has 6 -axis IMU sensor, ESP32 (Wifi+bluetooth), integrated battery charger, grove sensor socket to integrate temparature sensor, OLED screen. Everything included it is just less than $15. I have the M5Stick5, so would appreaciate if anyone of you done this before guide me on how to use that as a base.
m5stack/M5StickC

I'm not sure on your reasoning. The screen is superfluous in the beer you'd never read it and would need to work out how to keep it off, as the light might upset the beer.
Would still need a battery and would it fit in a petling? The device you build does have to float and have the aerial ideally at the top.
You might end up taking it out of the container and disabling screens etc.

Software would probably need reworking I suspect. Is it a saving at all once these hassles and improbabilites are factored in?

Given my non electronic background I have built several, both jeffery style and original stacked motherboards it is better to build them yourself or get a group together and build a few each.
The jeffery MB is well laid out, better aerial position and temp sensor than the original MB i used ( but still working okay ),plenty of instructions that are clear and the Ispindel is well supported.