Convert "io5" on protocol "h02" to Battery level via Computed Attributes AND show it

Nina 16 hours ago

It's working! Both! I'm really happy right now:

2026.10.10, 08.25.56.png

Thank you again for your Help, Anton.

Unfortunately, a new problem came up now, and it's really weird. After setting the new Computed Attributes, the tracker does not report its location anymore. It still switches on and is working while it is being moved, but there is no location visible on the map or the history:

2026.10.10, 08.29.20.png

I realized this yesterday already, when I only used the testing-attribute. So it should not have anything to do with io5 * 1 or null. Am I (again) missing something?

Thanks
Nina

Nina 8 hours ago

So,

the problem is still there. I moved the device several times today and yesterday, see below: I set the range from yesterday (when I first set the "42") to now. 656 points were written, but no position is shown on the map:

2026.10.10, 15.50.46,560 (Screenshot).png

2026.10.10, 15.50.56,010 (Screenshot).png

The track from before I set the "42" is displayed without any problems (not shown on the screenshots, because of the set time range).

I will now unlink the Computed Attributes..

2026.10.10, 15.53.55,585 (Screenshot).png

.. and go for a drive.

Will report back here

Nina

Nina 4 hours ago

Alright, really weird...

After I unlinked the Computed Attributes, the position was shown on the map instantly. The position jumped a few hundred meters, from the spot where the tracker was just before I added the "42" yesterday, to where the tracker was after I unlinked the Computed Attributes 4 hours ago:

2026.10.10, 19.45.07,670 (Screenshot).png