Are you trying to use them as iBeacons, or do you actually want to grab the temperature and humidity data from them?
From your iBeacon-4 screenshot, it looks like they are broadcasting iBeacon format for the UUID (the first string of numbers/letters starting with “ebef” and ending with “f525”), with fixed data (each line is the same), but then the last four numbers ("_2238" on the first line) are changing, which is weird.
Since you say this in only one of the Jalees, my guess is that the Jalee is using the major and minor data locations to carry the live temperature and the humidity data. So, just a guess, “2238” is the live temperature.
Another total guess: the temp might be being shown in hex. So 22 means “34 degrees C” and 38 means “.56 degrees C”. In other words, the temp is 34.56 degrees. The second line shows the temp went up to hex “2263” which would convert to 34.99 degrees C. (Use an online hex to dec converter for this)
Try putting it in the freezer to see how the numbers change.
So…if any of my above speculation is correct, it is acting like a beacon and broadcasting a fixed UUID (that’s correct beacon behavior), but it is changing the major and minor numbers (that’s not correct beacon behavior). That might be why the integration is getting angry and eventually deleting this device, i.e. “this thing was acting like a beacon for a little while, but now it is not acting like a proper beacon, so imma delete it!”
But the way, it’s also weird that under the “device” column on your screenshot, it is showing the UUID of the beacon, instead of the broadcast name of the beacon. On my HA, on this integration device page, it lists the names of all beacons in this column, not the UUID. I don’t think this should matter, since I assume it is actually broadcasting this UUID. But it’s a bit strange and makes me wonder what else they are doing oddly.
Warning: All of the above was 100% speculation. Lol