Hello,
Since I last updated my FHEM to the latest version I suddenly have a continious dimdown command to several of my FS20 devices. I'm pretty convinced it has something to do with the update as I can't explain where it is elswhere coming from.
I have several simple FS20ST devices that don't even understand the dim command. Also I don't use any dim commands for FS20 devices in my cfg file.
Can anyone help me with this problem, I had to remove some of the fs20 devices now because otherwise it would have been very dark in the room :(
Thanks
Is the problem is related to the frontend, and if yes, which one are you using?
Can you please log a problem case with "attr global verbose 5", and share the output with us?
Hi Rudolf,
I'm using the standard web interface FHEMWEB. After setting the verbose to 5 I see amongs others the following repeatedly:
2015.02.10 20:23:41.947 4: CUL_Parse: CUNO1 F661B1F1405 -71.5
2015.02.10 20:23:41.947 5: CUNO1 dispatch 810b04xx0101a001661b1f0014
2015.02.10 20:23:41.948 4: FS20 FS20_661b1f dimdown
2015.02.10 20:23:41.948 5: Triggering FS20_661b1f (3 changes)
2015.02.10 20:23:41.948 5: Notify loop for FS20_661b1f dimdown
2015.02.10 20:23:42.686 5: CUL/RAW: /F661B1F1405
2015.02.10 20:23:42.686 4: CUL_Parse: CUNO1 F661B1F1405 -71.5
2015.02.10 20:23:42.687 5: CUNO1 dispatch 810b04xx0101a001661b1f0014
2015.02.10 20:23:42.687 4: FS20 FS20_661b1f dimdown
2015.02.10 20:23:42.687 5: Triggering FS20_661b1f (3 changes)
2015.02.10 20:23:42.687 5: Notify loop for FS20_661b1f dimdown
2015.02.10 20:23:43.426 5: CUL/RAW: /F661B1F1405
2015.02.10 20:23:43.426 4: CUL_Parse: CUNO1 F661B1F1405 -71.5
2015.02.10 20:23:43.426 5: CUNO1 dispatch 810b04xx0101a001661b1f0014
2015.02.10 20:23:43.427 4: FS20 FS20_661b1f dimdown
2015.02.10 20:23:43.427 5: Triggering FS20_661b1f (3 changes)
2015.02.10 20:23:43.427 5: Notify loop for FS20_661b1f dimdown
2015.02.10 20:23:44.158 5: CUL/RAW: /F661B1F1405
F661B1F1405 means
F: Protocol FS20
661B: Housecode
1F: Local master for area(?) 1.
14: dimdown
05: RSSI -71.5
Something is sending the dimdown command repeatedly. Using 1F as a device address is not common, but legal. It does not look like a FHEM software problem to me. It might be a CUNO problem, but this is also not very likely. I would restart the CUNO to make it sure though.
Hello Rudolf,
Thanks for your feedback. Somehow last night at 02.55 this ghost device stopped sending the dimdown command and it seems it's solved now. I did reboot the CUNO already 2 days ago to see if that solved the problem but no.
The 1f address I use as localmaster (1244) and is only configured on three fs20st switches and 1 remote. As the remote just functions correctly I can't believe that that device is sending the dimdown command. So I guess it will stay a mysterie for now :)
Thanks again,
Alex