Replacement firmware for iSpindel (GravityMon)

[Diyhomebrewers]

If the device is not calibrated it should go into configuration mode automatically so can you check the serial output and see what the log states? If this is a gyro issue it will report that as an error. What pins are your gyro connected to ?

gyroscope:
VCC > 33
GND > 25
SCL > 26
SDA > 27

input pin to condig: 13 - 15

 

[mper]

gyroscope:
VCC > 33
GND > 25
SCL > 26
SDA > 27

input pin to condig: 13 - 15

The log output looks fine, thats the normal output but not the final part of the startup procedure. Do you have a "web server started later on?" The pins looks good also.

 

[Diyhomebrewers]

The log output looks fine, thats the normal output but not the final part of the startup procedure. Do you have a "web server started later on?" The pins looks good also.

I think not, in a few hours I'll prove it to you since I'm no longer at home and I'll update you. thx

 

[mper]

I think not, in a few hours I'll prove it to you since I'm no longer at home and I'll update you. thx

If you dont get any more output then its most likely related to some issue with the gyro hardware or the i2c bus used for communication. I dont think this is a software problem.

 

[Diyhomebrewers]

If you dont get any more output then its most likely related to some issue with the gyro hardware or the i2c bus used for communication. I dont think this is a software problem.

Hello good. I can enter!
But do I have to maintain the crossover between both pins and restart from the esp reset button? it's right? Is it not possible without pressing the reset button?

 

[mper]

Hello good. I can enter!
But do I have to maintain the crossover between both pins and restart from the esp reset button? it's right? Is it not possible without pressing the reset button?

It will check the pins at startup so you will need to do a reset

 

[Diyhomebrewers]

It will check the pins at startup so you will need to do a reset

It doesn't do anything, with the pins it only comes in if I cross the pins or restart at the same time.
But nothing happens, it also enters the configuration if I leave it at 90 degrees, it is enough for me, I was looking to be able to enter the configuration without opening it

thank you

 

[dtashmore547]

hi I have put two devices together based on the esp8266, I calibrated for 90 degrees on the horizontal then treated it on the vertical, one read 39 degrees and the other 50, is this normal or do I have a problem?
can I calibrate them like this if I set it at 25 degrees using a proportional value based on the difference between the horizontal and vertical values?

 

[mper]

hi I have put two devices together based on the esp8266, I calibrated for 90 degrees on the horizontal then treated it on the vertical, one read 39 degrees and the other 50, is this normal or do I have a problem?
can I calibrate them like this if I set it at 25 degrees using a proportional value based on the difference between the horizontal and vertical values?

looks like there is a problem, you should be able to get the full range between 0-90 degrees. What pcb are you using? Is the orientation of the gyro correct? Does it work with the standard ispindle firnware?

 

[dtashmore547]

thanks @mper
looks like I will have to do some digging and also check if it works with standard ispindel firmware

 

[dtashmore547]

hi @mper just updating my problem hopefully for anyone else having similar problems. after testing on Ispindel software and getting similar results and also the same on the gravitymon software and a esp32c3 build with the same issue I found I had to place the mpu6950 completely horizontal on all planes to get the correct calibration and 0 to 90 degrees of movement, I hadn't realized this when setting up initially and just had it level in the container which had the chip resting at an angle off horizontal. all is correct now thanks.

 

[mper]

Im looking for a few people to test the new User Interface for Gravitymon 2.0 and give me some feedback. I'm now starting the tedious testing process to check that all targets work as planned. I have rewritten the UI in VueJS in order to get rid of the older frameworks that are no longer developed.

 

[larsh]

I'll check it out. The "2.0.0-fwk" branch, right?
Will upgrade a spare CherryPhilip 4.0/ s2 mini/ MPU6050

 

[mper]

It will be on the dev bransch, i need to do a build with the latest ui app later today. I can publish the link here and in brewflasher

 

[mper]

I have now created a new build and created an release in github, it can be found here; Release 2.0.0 alfa release for UI testing · mp-se/gravitymon (github.com)

It should work fine to do an upgrade from an older version without issues. I will add this to brewflasher later on.

 

[larsh]

Upgraded from 1.3.0b3 to 2.0.0a1 without issues.
The UI is really fast! But the unit has not been in use for a while. Needs a charge

 

[mper]

Upgraded from 1.3.0b3 to 2.0.0a1 without issues.
The UI is really fast! But the unit has not been in use for a while. Needs a charge

Great, i really love the VueJs framework. It also much easier to maintain and add features compared to the older approach. You now have the wifi setup in the main UI so everything can be changed in one place. I have not added that many new features but i did quite a restructure. I removed the advanced tab and moved out all the settings to the right view.

Under the hood i also started to use my basic esp framework so i now have the same foundation for all my projects and this manages a lot of the common function and makes it much easier to maintain

 

[krump_lee]

esp8266 freezing when move the device to test gyro

 

[mper]

esp8266 freezing when move the device to test gyro

What version are you using ? What happends ?

 

[larsh]

First impressions: Fantastic work!

Question:
"Force gravity mode" in the Home screen = enable to avoid sleep mode?

Does not seem to work:
In Push Targets --> MQTT, I use iSpindel as the pre-defined format to match my former settings vs HA.
When I do a "Run push test", I get this error:
"No endpoint is defined for this target. Cannot run test."
No difference using mdns or IP as Server.
It still pushes the normal way though, according to Sleep Interval setting

 

[krump_lee]

What version are you using ? What happends ?

1.4.1 is perfect, upgraded to 2.0 alpha just fot fun..

booting, mesuring tilt and temp, menues ok, but when i touch the device lost connection and restart needed

 

[larsh]

1.4.1 is perfect, upgraded to 2.0 alpha just fot fun..

booting, mesuring tilt and temp, menues ok, but when i touch the device lost connection and restart needed

Have you tried to turn "Force gravity mode" on in the Home menu before touching the device? If your battery voltage is below the level configured, the device will exit config mode when you start moving it

 

[mper]

First impressions: Fantastic work!

Question:
"Force gravity mode" in the Home screen = enable to avoid sleep mode?

Does not seem to work:
In Push Targets --> MQTT, I use iSpindel as the pre-defined format to match my former settings vs HA.
When I do a "Run push test", I get this error:
"No endpoint is defined for this target. Cannot run test."
No difference using mdns or IP as Server.
It still pushes the normal way though, according to Sleep Interval setting

Force gravity mode is to disable sleep mode.

I will take a look at the MQTT part, I have not tested that yet, I also need to fix the line breaks in the format editor.

 

[mper]

1.4.1 is perfect, upgraded to 2.0 alpha just fot fun..

booting, mesuring tilt and temp, menues ok, but when i touch the device lost connection and restart needed

Well if it was calibrated at 90 degrees and you moved the device it will go into sleep mode unless you toggle the switch on the front page. Thats probably why you lost connection

 

[mper]

1.4.1 is perfect, upgraded to 2.0 alpha just fot fun..

booting, mesuring tilt and temp, menues ok, but when i touch the device lost connection and restart needed

Well, the device probably went into sleep mode so I have added some code to detect that and show a message to the user that there is no response from the device or you can do a lot of changes without having the ability to save them. Will do an update probably tomorrow.

 

[mper]

First impressions: Fantastic work!

Question:
"Force gravity mode" in the Home screen = enable to avoid sleep mode?

Does not seem to work:
In Push Targets --> MQTT, I use iSpindel as the pre-defined format to match my former settings vs HA.
When I do a "Run push test", I get this error:
"No endpoint is defined for this target. Cannot run test."
No difference using mdns or IP as Server.
It still pushes the normal way though, according to Sleep Interval setting

Good find, actually none of the testing functions worked, I had a mismatch in the VueJS code and Arduino. I will do an update tomorrow.

 

[mper]

New alfa with the reported bugs fixed.

https://github.com/mp-se/gravitymon/releases/tag/v2.0.0-alfa3

 

[wd16261]

I just tried the latest alfa version 3 and it looks great!!!
Just a small issue with the Push targets.
They were lost after the update and I forgotten to write them down so it took me some time to put them back in, but finaly it works.
Another thing that I noticed is that the Software version is not updated on the Homepage (but on the bottom bar it is correct.
(I'm using the ESP8266 version.)

 

[wd16261]

Maybe just another issue? When I click on the Create backup button in the other menu nothing happens.

And I always have the red message 'Save needed' in the upper rigth corner.

 

[mper]

I just tried the latest alfa version 3 and it looks great!!!
Just a small issue with the Push targets.
They were lost after the update and I forgotten to write them down so it took me some time to put them back in, but finaly it works.
Another thing that I noticed is that the Software version is not updated on the Homepage (but on the bottom bar it is correct.
(I'm using the ESP8266 version.)
View attachment 850280

Hmm, the configuration should be persistent so I will look into what could have happend there... And since the UI and Arduino code are two separate github projects they have different version numbers. I should make that more clear in the UI. Firmware vs UI Version or something.

 

[wd16261]

Hmm, the configuration should be persistent so I will look into what could have happend there... And since the UI and Arduino code are two separate github projects they have different version numbers. I should make that more clear in the UI. Firmware vs UI Version or something.

I did the update from version 1.2.0 (..90a5cb) directly to this latest version maybe this was the cause?

 

[mper]

I did the update from version 1.2.0 (..90a5cb) directly to this latest version maybe this was the cause?

Should not be a problem. I have changed the configuration format in 2.0 but the device should migrate the existing settings to the new format. Will have a look at that part. This narrows down the search to thanks for the update. You can always do a backup of the settings and store them if needed.

 

[wd16261]

Should not be a problem. I have changed the configuration format in 2.0 but the device should migrate the existing settings to the new format. Will have a look at that part. This narrows down the search to thanks for the update. You can always do a backup of the settings and store them if needed.

That was my second remark: The button to create a backup does not work in the latest version!

Third remark:
I'm also doing some test with the MQTT and I have the feeling that the Data format is always the ispindle format even if you change it?
The preview is correct but when I check on my Home assitent I always get the ispindle data format:

 

[mper]

That was my second remark: The button to create a backup does not work in the latest version!

Third remark:
I'm also doing some test with the MQTT and I have the feeling that the Data format is always the ispindle format even if you change it?
The preview is correct but when I check on my Home assitent I always get the ispindle data format:

View attachment 850283

I will take a look on the mqtt part, it should be visible in the serial console what data is sent and to what topics. Under other -> tools you can browse the file system and the format used for mqtt is in the file mqtt.tpl

I have noted that backup is not working on the device, this seams to be a compile problem with vuejs that I have seen before. I will fix that.

 

[mper]

That was my second remark: The button to create a backup does not work in the latest version!

Third remark:
I'm also doing some test with the MQTT and I have the feeling that the Data format is always the ispindle format even if you change it?
The preview is correct but when I check on my Home assitent I always get the ispindle data format:

From what I can see in the logs it seams to send the data as in the format template. I found an issue when storing the template so that could be the cause. When doing the testing it can be helpful to open a second window with a serial console so you can see what is going on. The MQTT logs would look something like this.

766874 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/tilt
766876 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/temperature
766877 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/temp_units
766879 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/battery
766880 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/gravity
766882 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/interval
766883 I: PUSH: MQTT publish successful on ispindel/gravitymone17d44/RSSI

I have fixed the backup function now and will do an update probably later today after some more testing.

Thanks for the feedback, very helpful.

 

[Terjedd]

I am setting up against Brewfather. Hitting the test button and gets Push target successfull - but the device is not showing up in BF like my other devices. Any idea why?

 

[mper]

I am setting up against Brewfather. Hitting the test button and gets Push target successfull - but the device is not showing up in BF like my other devices. Any idea why?

There are two different options for bf, ispindel and custom stream. It might be that you have the wrong format for the target. I just tested the ispindel options and that worked fine.

 

[mper]

A new UI test build https://github.com/mp-se/gravitymon/releases/tag/v2.0.0-alfa4

I think i have fixed all other things that have been mentioned here but let me know if I missed anything.

I still have a few issues to sort out, the following are things to address:
* Validate the configuration migration from older version
* Test all push targets

 

[Drinking Sensibly]

I'm waiting for some bits and pieces to arrive before building a couple of iSpindels.

Im looking for a few people to test the new User Interface for Gravitymon 2.0 and give me some feedback. I'm now starting the tedious testing process to check that all targets work as planned. I have rewritten the UI in VueJS in order to get rid of the older frameworks that are no longer developed.

I'm waiting for parts to arrive to build some iSpindels. Since I have parts for more than I need, assuming I don't break them in the manufacture, I'll definitely have a go.

 

[mper]

I'm waiting for some bits and pieces to arrive before building a couple of iSpindels.

I'm waiting for parts to arrive to build some iSpindels. Since I have parts for more than I need, assuming I don't break them in the manufacture, I'll definitely have a go.

You can just install it on a esp without sensors, it will work but you will get some warnings.