HeimdallMidgard
Another bulk lot of additions
New new UI Add some debugging Remove migrations I made a logo!
Devices now need to be in the format
[{
"name": "Blah",
"type": "beacon",
"uuid": "blahblahblah"
}]
Settings will need to be moved to using bools/ints where appropriate
@HeimdallMidgard @andriensis if you could have a test of this when you get a chance that would be great. It's running pretty solid for me, would love to see if you guys are getting any errors.
Here's a new one!
Stack smashing protect failure!
abort() was called at PC 0x4016c517 on core 0
ELF file SHA256: 0000000000000000
Backtrace: 0x4008f604:0x3ffe34e0 0x4008f881:0x3ffe3500 0x4016c517:0x3ffe3520 0x400d3e3d:0x3ffe3540 0x400d7585:0x3ffe36f0 0x400da429:0x3ffe3730 0x400da4a1:0x3ffe3750 0x400da99c:0x3ffe37c0 0x400dde89:0x3ffe37e0 0x400e4e76:0x3ffe3800 0x400d6cff:0x3ffe3820 0x40090892:0x3ffe3840
Hate it when my stack gets smashed
@HeimdallMidgard @andriensis if you could have a test of this when you get a chance that would be great. It's running pretty solid for me, would love to see if you guys are getting any errors.
@nashant Will do but I am on my honeymoon at the moment. After this I will have time again :-)
@HeimdallMidgard Congrats! Hope you have a wonderful time :smile:
@andriensis I've made what I think is a significant change as far as the crashes go. Moving the clearScan() to before the startScan(). Now that the scan is asynchronous it was starting it then immediately clearing the results, that can't have helped!
Currently trying this branch! I've added an uptime sensor on my home assistant instance so we'll quickly see if there's any stability issues.
@nashant I've noticed the distance seems to be more stable but way less accurate than before.
I was really close to the ESP (less than 50cm) and it was reporting around 0.50 (which is correct) but I've moved now for around 5 minutes to about 5 meters from the ESP32 and it looks like the distance is slightly increasing at every scan (from 0.50 to around 1.0 now). Not sure if this is intended behavior
What I've tried to do is delete a distance reading every 2 scans. Sounds like that's not actually happening. Can you see your device showing in the scans at 5m? I'll add in some debugging showing it deleting a reading then hopefully we'll be able to root out the issue
