Hi Martin,
I have installed the new homeduino Snapshot and after installation I found 4 new things. Attached a picture of the devices. Apart from that, every thing is working fine, actually 4 switches and 2 temperature and humidity sensors. Please tell me if you need more precise information.
You can enable DEBUG mode via karaf console by typing
log:set DEBUG org.openhab.binding.homeduino and monitor output in openhab.log file or the karaf console itself
To diable debuging output enter log:set DEFAULT org.openhab.binding.homeduino
Thank you for the advise. Last time Martin only wanted to know which device types the binding refund after a update.
Greetings
Johannes
Ok. Here is the debug output for my shutter screen (switch14) 
Hope this helps you. Let me know if you need more information. Thank you!
UP
20:25:47.047 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 828 276 8544 0 0 0 0 0 01011010010101101001100110101010101010101010011012
STOP
20:28:51.883 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 820 284 8524 0 0 0 0 0 01011010010101101001100110101010101010100110101012
DOWN
20:30:28.880 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 824 280 8536 0 0 0 0 0 01011010010101101001100110101010101010101001101012
Thanks for the heads up, so everything works you just reported about new devices that popped up?
Looking at rfcontroljs source: rfcontroljs/src/protocols/switch14.coffee at master · pimatic/rfcontroljs · GitHub I see an on/off state for switch14 are you sure that up/stop/down should be handled by switch14?
Thats the protocol that worked for me in pimatic. Its some EV1527 protocol but there isn’t any special implementation yet. Does the output helps you to find out which protocol fits better?
Here’s a link to the shutter screen: eSmart MIMOTO 120"
Could you use it with up, down etc in pimatic? Or just as switch on/off?
I’ve created my own Button-Array. There wasn’t a dedicated item for that.
It looked like that:
{ "id": "rf-shutter-buttons", "name": "Leinwand", "class": "HomeduinoRFButtonsDevice", "buttons": [ { "id": "shutter-down-button", "text": "DOWN", "protocols": [ { "name": "switch14", "options": { "unit": 2, "id": 845056, "all": true, "state": false } } ] }, { "id": "shutter-stop-button", "text": "STOP", "protocols": [ { "name": "switch14", "options": { "unit": 3, "id": 845056, "all": true, "state": false } } ] }, { "id": "shutter-up-button", "text": "UP", "protocols": [ { "name": "switch14", "options": { "unit": 4, "id": 845056, "all": false, "state": false } } ] } ] }
Thank that clears up things for me
Short update: in irregular time steps, openhab finds a thing “contact4”. I can remove it, but in a while there is a new one.
Have a nice weekend.
Did you remove it or suppress it, if you remove it it will pop up again if you suppress it the same device should not pop up again.
I removed it, but since one day no new pop ups.
Any progress on the switch 14 implementation? The other sensors / actors are running very well for now.
Hi MartinVW,
do you see any way to control the dimmer intertechno ITLR-300?
This device is autolearning, but it is not reacting on dimmer1 commands.
Thanks.
P.S.: It could be, that this device is compatible to CoCo Technologies, D-IO (Chacon), Intertechno, KlikAanKlikUit, Nexa
Hi martin,
the homeduino binding works like a charm in my setup (4 Switches, 2 Temperature and Humidity sensors).
I have only one point to optimize. When I receive the data from the temperature and humidity sensor the temperature is give in the following format:
HK_WEATHER1Aussen_Temperature changed from 13.800000000000000710542735760100185871124267578125 to 13.9000000000000003552713678800500929355621337890625
There are 48 positions after the decimal point. Is it possible to limit the positions?
An other point is the following message:
[ernal.messages.HomeduinoEventMessage] - Protocol not parsed successfull, most likely a false positive
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '00' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:44)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.Weather1Message$Protocol.process(Weather1Message.java:83)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:228)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:79)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:237)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
I can not find any problem inside my installation. Can you explain to me what it means?
Thank you for your great work on this binding.
Have a nice evening
Johannes
No progress its relatively complex and I first wanted to direct some attention the RFXCom module because some features were missing which stop me from moving to OH2. I’m not sure when I have time to pick it up.
It should be the protocol dimmer1, a base for the support for this protocol is already in the code so it should be implemented quite quick.
I put it in on the list I don’t know ifand if how other plugin’s resolve it?
[quote=“johannesbonn, post:176, topic:8017”]
An other point is the following message: Protocol not parsed successfull, most likely a false positive[/quote]
I think some error correction is missing in the homeduino, so sometimes corrupt messages are received, I think it’s nothing to worry about.
#Wrapping up
I just e-mailed a core developer of rfcontrol a reminder to validate whether they are actually okay with publishing this plug-in if so, I’m planning to make a pull request and add the extra protocol’s later.
Just found some old notes which could mean that doorbell1 would work too (instead of switch14)
This would be a better fitting protocol!
STOP
debug [pimatic-homeduino]: doorbell1: { id: 1420, unit: 1791, state: false }
UP
debug [pimatic-homeduino]: doorbell1: { id: 1420, unit: 1023, state: false }
DOWN
debug [pimatic-homeduino]: doorbell1: { id: 1420, unit: 1535, state: false }
Just fyi 
Thanks for your work!
Hi Martin,
I wanted to turn ON a switch with homeduino (switch 2) and nothing happened. No reaction of the system till the point Karaf showed me this:
23:06:51.725 [INFO ] [ernal.messages.HomeduinoEventMessage] - Protocol not parsed successfull, most likely a false positive
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '1010' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:44)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.Switch2Message$Protocol.process(Switch2Message.java:84)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:228)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:79)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:237)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
23:06:51.739 [INFO ] [ernal.messages.HomeduinoEventMessage] - Protocol not parsed successfull, most likely a false positive
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '1010' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:44)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.Switch2Message$Protocol.process(Switch2Message.java:84)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.Switch3Message$Protocol.process(Switch3Message.java:68)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:228)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:79)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:237)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
23:06:51.750 [INFO ] [ernal.messages.HomeduinoEventMessage] - Protocol not parsed successfull, most likely a false positive
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '1010' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:44)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoCoCo1.process(HomeduinoCoCo1.java:40)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:228)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:79)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:237)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
23:06:51.760 [INFO ] [ernal.messages.HomeduinoEventMessage] - Protocol not parsed successfull, most likely a false positive
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '1010' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:44)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoCoCo1.process(HomeduinoCoCo1.java:40)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:228)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:79)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:237)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[243:org.openhab.binding.homeduino:2.1.0.201702211848]
After 2 or 3 minutes everything was fine again and the switch reacted like expected. This is the same message like I posted before. But now during a time period with noreaction of the switch.
Mysterious is, that the two other switches (also switch 2) in this room react directly during the failure.
Do you have an idea about the problem? If you need more information please let me know.
Have a nice evening
Johannes
Hi Martin … how difficult would adding Contact2 and 3 would be?
I have some existing Contact2 devices and would love to use those
Hello Martin,
How are you. I wanted to inquire how you plan to proceed with the homeduino binding?
Have a nice evening
Johannes