# Firmware version detection **URL:** \ **Category:** General\ **Created:** [November 25, 2016, 3:19pm UTC](https://community.particle.io/t/firmware-version-detection/27507 "2016-11-25T15:19:27Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [November 25, 2016, 3:19pm UTC](https://community.particle.io/t/firmware-version-detection/27507/1 "2016-11-25T15:19:28Z")
Continuing the discussion from [Particle Tools Changelog](https://community.particle.io/t/particle-tools-changelog/26943/9): > [@Particle Tools Changelog](https://community.particle.io/t/particle-tools-changelog/26943/9): > > 11/25/16 - _Firmware version detection and automatic device status updates in Build IDE_ > > Since its release, Electron users were able to see what firmware version is running on their devices from tools like Build IDE. Now this feature is also available for Photons, P1's and some compounds like Bluz. Is there also a fix in the pipeline to have the Electons _"On the device:"_ info refresh without the need to OTA flash and clear the cache? ---
**Author:** ![suda](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/suda/32/18449_2.png) [@suda](https://community.particle.io/u/suda)\ **Post date:** [November 25, 2016, 3:39pm UTC](https://community.particle.io/t/firmware-version-detection/27507/2 "2016-11-25T15:39:54Z")
This information refreshes when a device sends a new describe message. Usually you can force the update by flashing something new to the device. There is an edge case where we’re unable to identify what’s on the device and we leave the previously detected version in the device document. We could add an “unknown version” feature where every describe update would be reflected. ---
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [November 25, 2016, 4:04pm UTC](https://community.particle.io/t/firmware-version-detection/27507/3 "2016-11-25T16:04:40Z")
The point is, that OTA updates for Electrons might consume more data then desirable for just a status update/describe message. Could maybe the SIGNAL (previously IDENTIFY DEVICE) be used to trigger the device to send a describe message? Another option might be to allow a “forced” OTA update with “apparently” incompatible version. When **_I_** know I have the correct system version on the device I don’t want to be forced to first flash old version for the status update and then again the actually desired version (unnecessary data consumption). Give me a warning and a PROCEEDE ANYWAY just as done for the general OTA. ---
**Author:** ![CJ\_](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@CJ\_](https://community.particle.io/u/CJ_)\ **Post date:** [December 11, 2016, 5:35pm UTC](https://community.particle.io/t/firmware-version-detection/27507/4 "2016-12-11T17:35:30Z")
I’m having this same issue where my build IDE shows the electron with version 0.4.9 but the CLI shows 0.5.3 after particle identify. I have tried clearing the cache and flashed new code to the board OTA but it still shows up as 0.4.9. If I try to flash with version 0.5.3 firmware I get the incorrect version message and no option to flash. Can you point out if I’m missing something or should the IDE be updating the version after I flash using the “on the board” version even though it’s wrong? ---
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [December 11, 2016, 5:43pm UTC](https://community.particle.io/t/firmware-version-detection/27507/5 "2016-12-11T17:43:17Z")
> [@CJ\_](#): > > or should the IDE be updating the version after I flash using the "on the board" version even though it's wrong? exactly that, but since 0.4.9 doesn't exist for the Electron you'd need to build for 0.4.8 and need to flash OTA. _After_ that you might need to repeat the clear cache stuff. ---
**Author:** ![CJ\_](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@CJ\_](https://community.particle.io/u/CJ_)\ **Post date:** [December 11, 2016, 6:02pm UTC](https://community.particle.io/t/firmware-version-detection/27507/6 "2016-12-11T18:02:41Z")
Thanks for the quick reply. I just tried flashing again compiling for 0.4.8 and got the same result, IDE still shows version on board is 0.4.9. I have been compiling for 0.5.3 and flashing over serial and everything seems to be working so I’m not sure if it’s just an issue with the IDE or if it will correct itself in time. Either way, my electron is working as expected. If you have any further advice I’m open to suggestions but I don’t think it’s causing any problems as of right now. ---
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [December 11, 2016, 6:15pm UTC](https://community.particle.io/t/firmware-version-detection/27507/7 "2016-12-11T18:15:40Z")
It is only an IDE bug and should not impact your device - you just won’t be able to OTA flash more recent target apps via Build. Are you sure your 0.4.8 firmware got properly flashed OTA from Build? Maybe put your device into Safe Mode first and then flash via Build (e.g. a simple Blink-A\_LED sketch) You could also try a different browser or incognito mode - or even a different machine. ---
**Author:** ![CJ\_](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@CJ\_](https://community.particle.io/u/CJ_)\ **Post date:** [December 11, 2016, 7:33pm UTC](https://community.particle.io/t/firmware-version-detection/27507/8 "2016-12-11T19:33:36Z")
Removing the electron and reclaiming solved my problem.