Which installed without issue. I could then run speedtest or speedtest-cli from the command line and get results. I can see both executables in /usr/bin, which leads me to think that the issue is with Ookla’s instructions on their website. However, I’m not clear if this will actually work.
It also results in error messages when running sudo apt-get update due to the lack of a release file.
Is it possible to add a Item with the TimeStamp of the last SpeedTest run?
I tried to implement it with a manual item (not connected to the binding) but i don’t get it working
Hi Alex, good idea. I will consider this during the next update. It will be only available for openHAB 4, as there is no maintenance of this binding for openHAB 3.
As workaround you could use a timestamp-update profile e.g. on the resultUrl channel:
Is this binding working with OH4?
For me unfortunately not. The channels are missing
2023-08-19 01:01:45.501 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'speedtest:speedtest:f55a0f0b6e' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2023-08-19 01:01:45.504 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'speedtest:speedtest:f55a0f0b6e': {thing/channel=Type description speedtest:ping_jitter for speedtest:speedtest:f55a0f0b6e:ping_jitter not found, although we checked the presence before.}
Removing the .jar and installing via gui fixed it.
Only problem is now the unit for the ping.
Before the update the ping was 12,4 (which is correct) now it is 0,0124.
How can I set the unit to the correct one? What do I need to add at the meta data unit for the item?
Checked again the way how the binding is implemented. It is updating the Channel using a QuantityType. Means the only configration that your ping item needs is a proper State Description, i.e. pattern="%.2f ms if you would like to show the value in ms instead of s.
Hi Mike,
could it be that the marketplace version 3.4.0 is broken?
Because it only has two channels (ISP/Server).
My speedtest VM is still running with oH 3.4.0 because i hadn´t the time to update the underlying debian for oH 4.