Its currently most likely behind a firewall (as its on a users premises).
NB We are trying to swap it out as we have another one ready, but can’t get it running - the ol’ ‘Breathing Cyan’ issue - I really wish that I understood that, as it seems to happen whenever we start to use a new device. We play with trying to fix it and eventually it starts working - could it be trying to uldate system firmware for a few hours ???. On my local units I use the CLI to flash the 0.4.6 bins (although I JUST foud a post which says add --usb to force LOCAL update ;-O - I ‘thought’ that was what I was doing but apparently not.
Sorry to go ‘off topic’ but its all related - honest ;-))
As for dumping the EEPROM - if its just an app to read content and send it - then my device is effectively doing that already - as its reading my 3 values and publishing them (along with other non-EEPROM data) every minute - its how I can see when it goes bad ;-)).
The 3 values are temperature settings (0-90 degC) so if it suddenly goes to 255 its pretty obvious ;-). My code actually now automatically tests for this when reading and if ANY of the 3 bytes are > 90 (ie like 255!!) it resets them back to 5,5,50. So again I can see these values a minute later.
BTW: These photons are GREAT devices - a little unstable as yet and limited docs but thats what you get for working at the ‘bleeding edge of technology’ ;-)). Keep up the good work