iSpindle Concentrators, Repeaters, Bridges, Hubs

[ZeSlammy]

Could be me but when installing the plugged in version using brewflasher,the 2nd file is not sent to the D1 mini,I assume this is the littlefs file?
Resulting in a hello world in my browser when going to it IP address.
The "wired" versions still working well.
Will use pyflasher in the meantime.
Cheers

It's not you, it's me (dreading words to hear)
I forgot to set the address where to upload from BrewFlasher.
Should work now.

 

[ZeSlammy]

Quick Update :
- Managed to have the "Change the name of the SSID" done : both the setting field is up and it works
- Working on the TimeZone selection
- Working on screen optimisation

Happy New Year folks

 

[wd16261]

Quick Update :
- Managed to have the "Change the name of the SSID" done : both the setting field is up and it works
- Working on the TimeZone selection
- Working on screen optimisation

Happy New Year folks

Happy New Year to you too and thanks for the quick change I will try it later today.

 

[ZeSlammy]

Happy New Yeart to you too and thanks for the quick change I will try it later today.

It's not pushed yet

 

[wd16261]

It's not pushed yet

Any idea when it will be pushed?

 

[ZeSlammy]

Any idea when it will be pushed?

I pushed a version where you can change the SSID and you can see which TZ you're using.

Next up, you can CHANGE said TZ

Then Screen Improvments.

 

[korev]

Inspired by ZeSlammy I am working on a colourful BPL-Display using a 2.8" ILI9341 TFT, and an 8266, which uses the MQTT facility of BPL, thus not interfering with BPL sending to Brewfather.
My request of @ZeSlammy is please could you adapt iSpindHub to provide a MQTT reporting/publishing function so that iSpindel data could be forwarded not only to Brewfather but also via MQTT.
Thanks

 

[ZeSlammy]

My request of @ZeSlammy is please could you adapt iSpindHub to provide a MQTT reporting/publishing function so that iSpindel data could be forwarded not only to Brewfather but also via MQTT.

I'll just add it to the list. How hard could it be (he asks innocently).

 

[korev]

I'll just add it to the list. How hard could it be (he asks innocently).

Thanks
Well, who knows!
Perhaps in a JSON, which with my very limited knowledge, I should hopefully be able to unscramble.
Cheers

 

[wd16261]

I'm unable to install the latest version for the 1.7" display.
I tried the new Brewflasher webversion and also the standalone version but both are stuck during the writing step.
With the webversion I get this message:

And with the standalone version it stops at this step:

Yesterday I could upload the previous version with both Webversion and standalone version without any problem.

 

[ZeSlammy]

That's weird.
Can you try with another version ?
Anyone succeeded ?
I'll check tonight.

 

[wd16261]

OK I did some additional tests.

I have 3x IspindHubs, one with a 1,4" display plugged onto a Wemos D1 Mini and 2x 1,8" display wired to an ESP8266 (this previously worked fine with the 1,7 display version).
And I have problems with both the 1,4" and the 1,7" version.
Both esp8266 with 1,8" display and the Wemos D1 mini are now giving me a white screen and the webserver is not running:

With the D1 mini version I even tried to upload the firmware.bin and the spiffs.bin files with another tools and I have the same result

White screen:

unfortunately I did not saved the previous versions so I can not rollback

 

[ZeSlammy]

What are logs saying ?
Smells like corrupted/missing filesystem

 

[wd16261]

I don't know what exactly you mean by 'What are logs saying?'
Were can I found these logs?
In the serial monitor I just saw some rubbish.

In the meantime I found the sources files on Github first of the previous version and I could install this with the command:
esptool.py --port COM3 --chip esp8266 write_flash --flash_mode dio 0x00000 C:\Temp\firmware.bin 0x100000 C:\Temp\littlefs.bin

After this the Wemos D1 mini version was working again (did not tested the 2 other yet).

After that I tried it again with the latest version and I noticed that the 2de file that was downloaded with Brewflasher called 'spiffs.bin' instead of 'littlefs.bin'!
So I also used the files of the latest version from GitHub and with the same command:
esptool.py --port COM3 --chip esp8266 write_flash --flash_mode dio 0x00000 C:\Temp\firmware.bin 0x100000 C:\Temp\littlefs.bin

But this time I had this error:
esptool write_flash: error: argument <address> <filename>: Detected overlap at address: 0x100000 for file: C:\Temp\littlefs.bin

The above was my mistake I inversed the names of the files after download. Once they were correctly renamed it worked!

So it looks like there is something wrong with the name of the littlefs.bin file when using Brewflasher?

I will try the above steps also with the other 2 iSpindHubs later.

 

[wd16261]

OK the reason why I renamed the files wrong is because they are also inversed on the github site!
I noticed this on the filesize. The firmware files is normally the smallest.

Maybe this is the reason why it does not work with Brewflasher?

 

[ZeSlammy]

DAMN !

Edit : should be better now
Sorry

 

[wd16261]

Yes I just saw that the files were renamed and tried it again with the web version of Brewflasher and now it worked:

I Will test it later to see if the new functions are working.
Thanks.

 

[wd16261]

OK the change of the SSID works after a reboot of the devices and the TimeZone seems to works also.

Maybe something to add to the ToDo list: Add the version number in the About page so that we can see if the update was completed.

 

[ZeSlammy]

Maybe something to add to the ToDo list: Add the version number in the About page so that we can see if the update was completed.

Something like this ?

 

[wd16261]

Yes that would be perfect for me.

 

[wd16261]

@ZeSlammy sorry but there still seems to be a problem with the 1,4" Direct plug version.
I can not install this version with Brewflasher (standalone nor webversion).
I think they can not download the firmware.bin or littlesf.bin file?

When I use the files from github to install them manually it works.

 

[ZeSlammy]

Can you retry via "native" BrewFlasher ? Might have been a SHA issue

 

[wd16261]

OK now it worked.

 

[wd16261]

Now I can connect my 4 ispindel to each iSpinHub for calibration this weekend

Many thanks!

 

[DaveS]

Is anyone else experiencing this with the latest direct version binary ...
After flashing with brewflasher or esptool,the captive portal comes up and can connect to my wifi network.
I can ping its IP address,web page fails to open.
LCD hangs showing Ispindhub by slammy and connected on the line below.
The previous direct binary worked perfectly on this hardware. Red tab 1.4" LCD

 

[ZeSlammy]

Hello @DaveS Which version are you trying to flash ?
do you know how to take logs ? Can you ?

 

[DaveS]

Hi @ZeSlammy I did not think of looking at the serial.
After looking at log output I noticed my firewall was blocking internet access to that device.
When allowed to access internet it works fine.
Thanks for reply !

Ispindhub LCD & web interface looking good now,thanks for all your effort.

 

[wd16261]

Ok does this means that the iSpindhub will not work if there is no internet?
My idea was to use the iSpindHub simply as a monitor on top of the fridge so I can follow the fermenting process within the same room without a PC nor mobile device.

 

[ZeSlammy]

I don't think it should need an internet access to work but I'll double check. Might be the NTP synch that acts as a blocker

 

[Thorrak]

I don't think it should need an internet access to work but I'll double check. Might be the NTP synch that acts as a blocker

Ooh, that makes sense.