jens-maus / RaspberryMatic

:house: A feature-rich but lightweight, buildroot-based Linux operating system alternative for your CloudFree CCU3/ELV-Charly 'homematicIP CCU' IoT smarthome central. Running as a pure virtual appliance (ProxmoxVE, Home Assistant, LXC, Docker/OCI, Kubernetes/K8s, etc.) on a dedicated embedded device (RaspberryPi, etc.) or generic x86/ARM hardware.
https://raspberrymatic.de
Apache License 2.0
1.52k stars 186 forks source link

devconfig.cgi RSSI list is empty #282

Closed Jensilein closed 5 years ago

Jensilein commented 6 years ago

Hello,

I have a PI3 with a HM-MOD-RPI-PCB and newest RaspberryMatic 2.31.25.20180225. When I open : "http://192.168.xxx.xxx/tools/devconfig.cgi?cmd=show_rssi&sid=@xxxxxxxx@" and click on RSSI only an empty page appears.

Maybe you can fix it or what else can i do to view the RSSI values?

Jensilein commented 6 years ago

Hello, can you please give me an answer how to overcome the issue with the missing RSSI values?

Thank you.

jens-maus commented 6 years ago

Sorry, but for me the RSSI values are not missing. Is this still the case?

Jensilein commented 6 years ago

Unfortunately yes, the values are not shown, the page is empty.

martz170 commented 6 years ago

Hello, i had this issue also some weeks ago - it was a problem with the Brower in combination with Kaspersky. Actually it works with Firefox 59.0.2 and 2.31.25.20180324 without any Problems.

Jensilein commented 6 years ago

Not here. Tried it on Windows as well as on MacOSX. RSSI values are not shown. Maybe it has something to to with the fact that I’m running Homematic IP devices?

moclub4 commented 6 years ago

Hi, same issue here. RSSI List is empty. Firefox, Chrome and Safari in newest versions on Mac 10.13.6. All the other views within devconfig are interpreted without any problems.

HMside commented 6 years ago

The RSSI list is displayed with HM-MOD-RPI-PCB and also RPI-RF-MOD. But i use HM-RF and HmIP-RF devices. Perhaps this behavior may only occur in systems where only HmIP-RF device are used.

jens-maus commented 5 years ago

This problem should be solved in the 3.41.x firmware line already. Please reopen ticket, if not.