I’ve been using RuuviTags for a while now to monitor environmental conditions at our garden plot (off-grid via GSM) and have been very impressed with their reliability and longevity. I’ve just recently replaced the first battery after around three years of continuous outdoor operation, which is absolutely amazing for a device reporting measurements wirelessly at a rate of about one per second. You’ve really done a great engineering job on these little tags!
Just recently I discovered the additional capabilities provided by hacking the tag’s firmware, in particular the vibration monitoring example discussed in the blog caught my interest. So I ordered a brand new RuuviTag Pro to try and recreate that example (is that even a good idea since the example is ~3 years old, were there any hardware changes in the meantime that would cause issues with codes from these older blog posts?). Since the example code is based on nRF SDK 15.2 but my tag came with a quite recent (15.3 based) firmware, I’m wondering what the most straightforward way is to get the vibration firmware running given that I don’t own a cable or DevKit for flashing firmware updates? I tried flashing the app-only as well as app+sd built from source code via DFU, both resulting in a continuous red light and no operation. I understand I can’t (or shouldn’t) downgrade the bootloader to SDK 15.2, are there any other options to get the vibration firmware uploaded to my tag? Or should I use one of my older RuuviTags (1.2.12 firmware) and upgrade using an app+sb+bootloader DFU images built from the example code? Is a cable connection the best option for flashing the older firmware examples from the Ruuvi blog?