I’m mixing EnOcean device with Shelly actuators and CometDECT radiator headers using AVM FritzBox as bridge.
Shellys especially were I don’t want or can’t exchange pole-changing switches, or for multiway switching and especially in basement were I run anyways an WiFi AP. Price and size is also an advantage, but quality seems, well solala. For all Shelly actuator I maintain status and sensor items, e.g. WiFi signal quality.
So I started to maintain something similar for my EnOcean actuators, PEHA, Nodon and Eltako. Two channels spotted my attention, rssi and lastReceived, available equally on all EnOcean things. I came that far:
RSSI does come back in dBm values, what I scale into a signal quality transformation:
]-55..]=4 ]-65..-55]=3 ]-75..-65]=2 [..-75]=1
The scale are going back to best practise found in WWW and collecting local dBm values I get from actuators sitting almost beneath my RPi @ enoceanpi (OG) and my farthest thing, an ETHSA TF20 in basement.
So, does anybody of you have a more accurate scale here? A “better” best practise?
Second, how could I get openhab property icon “qualityofservices” correctly running here? It seems just to act on the raw values coming out of the channel, what is still dBm value …
And at the last, what I can see PEHA and Nodon actuators do update by themselves occasinal to my EnOCean bridge, even not used for while. The Eltakos (TF61), albeit bidirectional, just update those values at the time they were used … doesn’t matter how “autoupdate” is set, true or false.