hi,
i am new at the FHEM forum and kindly ask for help.
- I have a CUL that controls my Somfy Shutters.
- only one of the shutters is not reacting. :-X
- obviously it seems that I have lost the rolling code and it's out of sync to the shutter motor.
I really tried to find an answer about this topic in the forum, but I could not understand all the topics in detail...
Additionally I have set the flag autoStoreRollingCode = 1 which is a new feature to get the correct rolling code back after a system crash...
I am somehow lost and tried several approaches. e.g. I want to read the rolling code from my shutter device, but I think this is simply impossible? so I did a look into the fhsm.save logfile and tried to define the shutter with a modified command according to the values I have read in the fhem.save file:
define rollokoppix A00004 AF 08BC
After doing this the rolling code and the enc key are back on initial values. So I think this is not the correct way.
I read some postings which describe that it's possible to run a command which produces a loop or something and fires the rolling code with an incremented value...and then you need to wait until the rolling code sent from the CUL is higher than the rolling code from the shutter. If this occurs the command need's to be stopped and the shutter's rolling code is in sync with the rolling code generated from the FHEM backend and everything is fine.
I want to get this working, so please help me. I do appreciate your feedback!
Loosing rolling codes might be one reason for not being able to control a certain SOMFY device, especially if it is only a single one where this is happening. Additionally rolling codes get not lost if they are in the .save file, so if you see them in the save file it should be also in the device?
Another reason might be a range problem (reachibility) between the sending device on FHEM and the shutter. Is this shutter further away than most of the working ones, I would first investigate if there is a problem with reaching the shutter from FHEM.
Problem is after testing some time without having a connection to the shutter device will certainly bring rolling codes out of sync, since they are maintained independently in the shutter and in FHEM (as in any manually operated remote).
Some things to try out:
- Define a new device for the one not working with a NEW address and try to "prog" it with the shutter not working. If this is working you are sure not having a range problem. Then you might be able to just use the new device and remove the old one. This should work if you do not have a lot of remotes connected to the shutter and if there are not frequent changes to these
- If the new device is also not able to work with the shutter then you have to check what might have caused a range problem: direction of antenna, change in furniture, move of FHEM-sending device, ...
But be aware - for the existing device (rollokoppix) the rolling codes might be out of sync
- To recover an unknown rolling code. Set the shutter into a middle position / redefine the current somfy device to have a rolling code that is certainly below the current value (e.g. 000000 or from a backup of fhem.save when the device was still working). Have a repeating at to test all rolling codes 1 by 1 every 5 seconds:
define testrollingcodes at +*00:00:05 set rollokoppix on
and wait until the shutter moves. With a rolling code of 0xbc as in your example below, this will take substantial time, when starting from zero
Hi Viegener,
thank you for your feedback.
As the shutter was already working with FHEM in the past, I directly go ahead and did a test with the statement.
define testrollingcodes at +*00:00:05 set rollokoppix on
Now I can check that every 5 seconds a new code is sent to the shutter and the new keys are shown in the FHEM shutter configuration. Unfortunately, nothing seems to happen. I am waiting for more than 30 minutes.
Do you have an idea of how long it could take?
Not sure if you read my statement - it was clear that it worked in the past, but something might have changed.
And your question is also not something anybody can answer based on the state ;D
How should I say that since I do not know which value your shutter has been last active with and which value you started the procedure with?
But you can easily calculate the progress yourself - in an hour the are about 720 codes are checked meanng a progress of approximale 0x2d0 (hex)
yes i read your reply. there was neither a change in the hardware nor of the raspberry and even no change in the positions of shutter or raspberry or anything like moved furniture or new walls. ;D
I calculated about 910 hours approximately for the procedure from 0000 to FFFF. This is quite a lot :o
I will just let the testrollingcodes run and wait if something happens. I cross my fingers I will not fall asleep until the shutter is reacting in the end...I assume the testrollingcodes will go ahead when the shutter is reacting or does it automatically stop - somehow ?
is it possible to start the generation at e.g. DDDD?
Zitat von: koppix am 20 Mai 2020, 12:46:00
is it possible to start the generation at e.g. DDDD?
Yes and I mentioned that already. But that will not make any sense if DDDD is higher than the Rolling Code of your shutter.
If there are questions to my statements, feel free to ask. Happy to help, but please also read the advice, that makes helping easier...
Q: Have you tried to define another SMFY device as stated before? If not why not - If yes what was the result
Q: Have you checked a backup from a time frame that was guaranteed to work and used the rolling code from that time?
thanks again for your feedback I am really happy that you want to help me ;)
another day another try... :o
I search for all backup files for fhem.save in the fhem log directory:
$ cd /opt/fhem/log
$ ls -l fhem*
-rw-rw-rw- 1 fhem dialout 11357 Mai 22 10:09 fhem.save
-> only one file detected.
As I do not have a fhem.save backup for the last known working configuration, I have defined a new SOMFY remote with a free channel A00114:
- define EG.Rollo.LivingRoomGross SOMFY A00114 AA 0000
- with the remote control, I have activated the shutter in program mode
- I have run the "set prog EG.Rollo.LivingRoomGross" command in fhem
-> No feedback from the shutter
-> No idea what to do
further topics
- I am not sure if there is any dependency between the ENC_KEY and the ROLLING_CODE for FHEM or the shutter?!? Do you have any information about this?
- I tried to increase the ROLLING_CODE in fhem with the DEF statement. I think it's possible to increase the fhem's ROLLING_CODE with DEF. So this could be a way how to increase the ROLLING_CODE, but I am not sure if this is the recommended way to do it.
- Additionally I found a post in the fhem forum which the advice that the FHEM's ROLLING_CODE can/shall be higher than the shutters ROLLING_CODE, but this is in conflict with your last answer.
I would appreciate your feedback! 8)
https://wiki.fhem.de/wiki/SOMFY
Zitat:
Bekannte Probleme
Bei Umzug von einem FHEM-Server auf einen anderen (oder Rückspielen eines Backups) kommt es vor, dass die FHEM-Fernsteuerung einen niedrigeren Rolling Code hat, als der Rollladen erwartet / zuletzt gesehen hat. In diesem Fall reagiert der Aktor (Rollladen) solange nicht - nicht einmal auf erneute Anlern-Versuche! - bis der gesendete Rolling Code ausreichend hoch ist!
-> i would expcet the fhem rolling code >= shutter rolling code
Zitat von: koppix am 22 Mai 2020, 10:31:29
thanks again for your feedback I am really happy that you want to help me ;)
another day another try... :o
I search for all backup files for fhem.save in the fhem log directory:
$ cd /opt/fhem/log
$ ls -l fhem*
-rw-rw-rw- 1 fhem dialout 11357 Mai 22 10:09 fhem.save
-> only one file detected.
As I do not have a fhem.save backup for the last known working configuration, I have defined a new SOMFY remote with a free channel A00114:
- define EG.Rollo.LivingRoomGross SOMFY A00114 AA 0000
- with the remote control, I have activated the shutter in program mode
- I have run the "set prog EG.Rollo.LivingRoomGross" command in fhem
-> No feedback from the shutter
-> No idea what to do
further topics
- I am not sure if there is any dependency between the ENC_KEY and the ROLLING_CODE for FHEM or the shutter?!? Do you have any information about this?
- I tried to increase the ROLLING_CODE in fhem with the DEF statement. I think it's possible to increase the fhem's ROLLING_CODE with DEF. So this could be a way how to increase the ROLLING_CODE, but I am not sure if this is the recommended way to do it.
- Additionally I found a post in the fhem forum which the advice that the FHEM's ROLLING_CODE can/shall be higher than the shutters ROLLING_CODE, but this is in conflict with your last answer.
I would appreciate your feedback! 8)
If the new SOMFY device is not working, this is strongly supporting one of the assumption from the beginning, that you have a range problem. Your sending device can not reach the SOMFY shutter. In this case finding the rolling code is the second problem to solve. First you need to ensure that your shutter is reachable from FHEM (again). This might get a little bit tricky since you stated not being aware what has changed and it is virtually impossible to help here with specific advice.
Best would be to move your FHEM sending device nearer to the shutter and try firts to solve the problem. Again - finding the rolling code can not be solved without reaching the shutter consistently and always.
hi,
thank you again.
You are completely right. I have moved the CUL to a new position and I could successfully define the shutter as a new device with:
define SHUTTERNEW SOMFY A00114
It was obviously a problem with the range / reachability of the sending device to the shutter!
Thank you so much for all you help!
hi,
I have one last question:
one of my shutters does only react if I send the command twice. Although I have changed the position of the CUL as near as possible to the shutter, it seems it just needs a second chance ;)
I have set the attribute repetition = 2, but this does not help.
Do you have a tip / trick for me?
Zitat von: koppix am 23 Mai 2020, 12:34:13
hi,
I have one last question:
one of my shutters does only react if I send the command twice. Although I have changed the position of the CUL as near as possible to the shutter, it seems it just needs a second chance ;)
I have set the attribute repetition = 2, but this does not help.
Do you have a tip / trick for me?
That sounds as well like a a range problem or a problem with your CUL.
Possibly you need to consider having another CUL or possibly a signalduino
hi, well I have read about signalduino and maybe it's worth to upgrade. So it's possible to get the current status of the shutter and hopefully its a more stabile solution. The CUL is from time to time disconnected --> I need to reboot the raspberry to get the CUL connected again - this is not an ideal solution.
Zitat von: koppix am 27 Mai 2020, 22:17:17
hi, well I have read about signalduino and maybe it's worth to upgrade. So it's possible to get the current status of the shutter and hopefully its a more stabile solution. The CUL is from time to time disconnected --> I need to reboot the raspberry to get the CUL connected again - this is not an ideal solution.
Yes, Signalduino has the advantage of being able to receive also SOMFY commands from other remotes. But Signalduino does not solve the range problem you seem to have. I would consider adding a signalduino and having that located differently.
With disconnects of CULs this might have different causes - e.g. timeouts (led flashing fast) or power issues or ...