More details: I suspect it's manifested as a timing related issue, because the frequency of the symptom changes when I add or remove slf4j logging in other Subscriptions. Also, at home today the bug happens nearly all the time; even if I close both my app and the OpenICE supervisor and restart both. It also happens if I remove the tracker.sawIdentity() call above, so it doesn't seem related to what tracker.sawIdentity() does (which is to do a deep copy of the DeviceIdentity object).

To reproduce, I start my code, then start OpenICE Supervisor on the same PC, then use the Supervisor to create a simulated Pulse Oximeter. The code I show above receives the Pulse Oximeter's DeviceIdentity, but often (not always) that DeviceIdentity has a blank (0 length; not null) model String rather than a string like "Pulse Ox (Simulated)".

Another thing to check: that both pcs are on the same IP subnet. For example, IP addresses 74.125.28.51 and 74.125.28.125 are on the same subnet (the first 3 numbers match); 74.125.28.51 and 74.125.33.7 are on different subnets (because the first 3 numbers differ). You can find your pc's IP address in Windows by opening a command prompty and typing ipconfig. Under Linux, you can usually find it by typing ifconfig.

Short version for others who run into the problem: I can login from outside the corporate network, then I stay logged in when I'm on the corporate network. Once logged in, it seems to stay logged in across instances of visiting community.openice.info.

I'm following up with UserEcho, the hosts of this community, to resolve the issue.

One hint I have so far: Listen for DeviceIdentity data and cache that so that when you see a unique_device_id you can find the model etc. of the device that sent it.

Now my question is: what if my app is a late joiner and the device has already broadcast it's one-time-only DeviceIdentity? Is there a way to request a given unique_device_id to re-send its DeviceIdentity? I see this appearing when I start my late-joiner app, but today I suspect that the OpenICE Supervisor is cacheing that info for me - is that true? Or does the device adapter report the DeviceIdentity when a new Subscriber appears?

Thanks as always,
Brad