Nodon SIN-2-RS-01 new Model (Firmware) not working #70
-
Hello all, I have 3 modules Nodon SIN-2-RS-01 Two of them work 100% (old modules firmware 1.3 and 1.2) The 3rd and newest module does not work (firmware 1.5.1) What is the reason ? Can you help me please ?
|
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 4 replies
-
Hi @vbreit, I don't think this is related to the firmware. To recreate a clean device database, I suggest to:
By the way, I may all but strongly suggest you avoid using accents and whitespaces in a device name. |
Beta Was this translation helpful? Give feedback.
-
Hello mak-gitdev thank you for your answer. Unfortunately, the reset of the devices has not helped. I have try it 3 times. All (old) nodons work except the new one. And only the new one says this in the log:
i think its the new Firmware 😄 |
Beta Was this translation helpful? Give feedback.
-
Could you please share your current device configuration file ? |
Beta Was this translation helpful? Give feedback.
-
Hello mak-gitdev 😄 yes i renamed the devices because of your hint with the accents and whitespaces
|
Beta Was this translation helpful? Give feedback.
-
yes i forgot one 🙈
yes i can confirm that i also control the "old nodons" via set-position. There it works, but that doesn't matter because open / close / stop doesn't work on the "new nodon" either:
|
Beta Was this translation helpful? Give feedback.
-
Ok this is a bug at enocean-mqtt level. When a send request is received, we have to determine which sensor is targeted. Fortunately, fixing this is simple. Thanks for discovering this one 👍 |
Beta Was this translation helpful? Give feedback.
Ok this is a bug at enocean-mqtt level.
And as previously explained, this is not related to the firmware.
When a send request is received, we have to determine which sensor is targeted.
To select the correct sensor, a name comparison is done between the MQTT topic and the list of sensors.
At the moment, this name comparison checks whether a sensor name is IN the MQTT topic.
Thus, when a request targeting
shutterwz/terrasse1
is received, asshutterwz/terrasse
appears first in the list of sensors and as "shutterwz/terrasse" is also in "shutterwz/terrasse1", it will pass the current name comparison and it will be selected as the targeted device.Then as the wrong device is selected, you end …