AWESOME!!!
Now on to testing 5 channel remotes 
Ok here are my findings with 5 channel remotes:
To sum up:
with the latest snapshot sending works perfectly (so far), however receiving doesn’t. I was unable to get binding to add any new devices to my Inbox when using the latest snapshot.
Using the 2.1.0.201702121220 version Devices were detected and added to inbox but they appeared offline.
I then simply switched to the latest snapshot and they came online and i could send commands.
Long version with logs:
Using binding version 2.1.0.201702121220
240 | Active | 80 | 2.1.0.201702121220 | Homeduino Binding
Receiving log - works perfect - new devices discovery works
2017-02-16 00:51:42.336 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5268 1556 732 360 10832 0 0 0 0123232323232323233223323232323232322332233232233232232332323232233223322332233224
2017-02-16 00:51:42.342 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:535300684_1' to inbox.
2017-02-16 00:51:48.193 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5112 1716 732 360 10984 0 0 0 0123232323232323233223323232323232322332233232233232232332323223323223322332233224
2017-02-16 00:51:48.199 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:535300684_2' to inbox.
2017-02-16 00:51:50.398 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5264 1556 728 364 10984 0 0 0 0123232323232323233223323232323232322332233232233232232332323223233223322332233224
2017-02-16 00:51:50.407 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:535300684_3' to inbox.
2017-02-16 00:51:52.099 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5268 1716 732 360 10836 0 0 0 0123232323232323233223323232323232322332233232233232232332322332323223322332233224
2017-02-16 00:51:54.879 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5260 1716 728 364 10836 0 0 0 0123232323232323233223323232323232322332233232233232232332322332233223322332233224
2017-02-16 00:51:54.887 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:535300684_5' to inbox.
Thing setup - error - device offline
SHUTTER3-535300684.0
Homeduino Shutter3
A Shutter3 device.
Status: OFFLINE - CONFIGURATION_ERROR RFXCOM device missing deviceId or subType
Channels
Shutter
homeduino:shutter3:32466789:535300684_0:shuttercontent_copy
Shutter channel
Status: OFFLINE - CONFIGURATION_ERROR RFXCOM device missing deviceId or subType
Switch to the latest snapshot:
240 | Active | 80 | 2.1.0.201702152258 | Homeduino Binding
Error when receiving - new devices discovery occasionally throws Error Unsupported token: '11' for protocol Protocol (what is this?)
2017-02-16 00:59:11.974 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5092 1720 716 360 10992 0 0 0 0123232323232323223223323232323232322332233232233232232332322332223223322332233224
2017-02-16 00:59:11.977 [ERROR] [ernal.messages.HomeduinoEventMessage] - Error occurred
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '11' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:43)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.homeduino.Shutter3Message$Protocol.process(Shutter3Message.java:87)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:224)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.java:75)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBridgeHandler.java:233)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConnector.java:160)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
EDIT:
ON followup i tested with another remote and 4/5 channels were detected without problem, 1 failed, but then when i pressed the button again it was resolved - 2nd remote i tested all 5 channels worked … with occasional error :
2017-02-16 18:13:36.271 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5260 1716 744 352 10800 0 0 0 0123322323323223323223323232323232322332233232233232232332323232323223322332233224
2017-02-16 18:13:36.282 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_0' to inbox.
2017-02-16 18:13:42.048 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5260 1712 740 352 10988 0 0 0 0123322323323223323223323232323232322332233232233232232332323232233223322332233224
2017-02-16 18:13:42.067 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_1' to inbox.
2017-02-16 18:13:43.663 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5260 1712 740 352 10840 0 0 0 0123322323323223323223323232323232322332233232233232232332323223323223322332233224
2017-02-16 18:13:43.675 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_2' to inbox.
2017-02-16 18:13:45.119 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5104 1720 736 356 10988 0 0 0 0123322323323223323223323232323232322332233232233232232332323223233223322332233224
2017-02-16 18:13:45.131 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_3' to inbox.
2017-02-16 18:13:46.576 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5260 1560 740 352 10996 0 0 0 0123322323323223323223323232323232322332233232233232232332322332323223322332233224
2017-02-16 18:13:46.586 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_4' to inbox.
2017-02-16 18:13:47.904 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5208 1596 656 300 10852 0 0 0 0122322222323222323222323232323232322232223232223232222232322232223222322232223224
2017-02-16 18:13:47.910 [ERROR] [ernal.messages.HomeduinoEventMessage] - Error occurred
org.openhab.binding.homeduino.internal.exceptions.InvalidInputForProtocol: Unsupported token: '11' for protocol Protocol
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.map(HomeduinoProtocol.java:43)[240:o rg.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.homeduino.Shutter3Message$Protocol.process(Shutter3Message.java: 87)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.homeduino.HomeduinoProtocol.process(HomeduinoProtocol.java:224)[ 240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.messages.HomeduinoEventMessage.getInterpretations(HomeduinoEventMessage.j ava:75)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.handler.HomeduinoBridgeHandler$HomeduinoMessageListener.packetReceived(HomeduinoBr idgeHandler.java:233)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.connector.HomeduinoSerialConnector.sendMsgToListeners(HomeduinoSerialConn ector.java:160)[240:org.openhab.binding.homeduino:2.1.0.201702152258]
at org.openhab.binding.homeduino.internal.connector.HomeduinoStreamReader.run(HomeduinoStreamReader.java:91)[240:or g.openhab.binding.homeduino:2.1.0.201702152258]
2017-02-16 18:13:53.553 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5112 1708 736 356 10992 0 0 0 0123322323323223323223323232323232322332233232233232232332322332233223322332233224
2017-02-16 18:13:53.562 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:shutter3:32466789:37381 9980_5' to inbox.
2017-02-16 18:14:32.536 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Checking Homeduino transceiver connection, thing s tatus = ONLINE
Thing settings - things discovered using version 2.1.0.201702121220 work normally:
SHUTTER3-535300684.0
Homeduino Shutter3
A Shutter3 device.
Status: ONLINE
Channels
Shutter
homeduino:shutter3:32466789:535300684_0:shuttercontent_copy
Shutter channel
first quick comparison of sent code - still more to check:
CH0
STOP
2017-02-16 01:02:34.285 [DEBUG] [l.connector.HomeduinoSerialConnector] - Sending message: RF send 4 7 366 736 1600 5204 10896 0 0 0 3210101010101010100110010101010101011001100101100101101001010101010110011001100114
RF send 4 7 366 736 1600 5204 10896 0 0 0 3210101010101010100110010101010101011001100101100101101001010101010110011001100114<LF>
Pimatic vs OH2 - MATCH!
Did you have to hardcode the 14 or just modify the code?
I incorrectly switched the footer 14 vs 04 for not program mode vs program mode. So it was just a correction in the code, nog strange hard coding was required.
Hi Martin,
I have tested to add the pir sensor without success. I have the following problem:
The Sensor was found as pir2 at the inbox under paper ui, I have tried to add them, but I get the message (at the right corner under paper UI) “ERROR 409 - Confict”. The thing was not created. The log shows the following:
18:44:11.681 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1516 15516 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:11.690 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'homeduino:pir2:4ea8812e:10_21' has been added.
18:44:11.690 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homeduino:pir2:4ea8812e:10_21' to inbox.
18:44:11.941 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 504 1516 15520 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:12.198 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1516 15512 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:12.456 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1516 15512 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:35.130 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1516 15520 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:35.389 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1516 15516 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:35.661 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 504 1516 15520 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:44:35.906 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 504 1516 15512 0 0 0 0 0 01100110011001100110011001100110011001
And a little bit later:
18:45:16.237 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type homeduino:pir2.
Do you know what is the problem?
Thanks in advance
Greetings
Johannes
Hmm, feels like an error I made before, i mapped message types on so much places that it is hard to keep track. It’s one of the actions on my list to make this more easy for development.
If you need more information please tell me…
No I got it quickly but decided to fix the underlying problem, now there are only a few places left where new mappings have to be added. I also made the number of repeats configurable.
org.openhab.binding.homeduino-2.1.0-SNAPSHOT-201702181241.jar.zip
Hi Martin,
fantastic, pir2 is running without problems. But I have two annotations:
- The item state of the pir sensor is set to OPEN after initialization. After that homeduino receives commands from the pir sensor. Why the state doesn’t change to CLOSED?
For rules actually I use receive Update, but with this solution every rule is triggered two times. I think the pir sensor receives two updates with one movement detection. Is this right?
18:33:15.041 [INFO ] [marthome.event.ItemStateChangedEvent] - PIR21021_Contact changed from NULL to OPEN
18:33:15.281 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1524 15544 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:33:15.285 [DEBUG] [g.homeduino.handler.HomeduinoHandler] - Received message from bridge: homeduino:homeduino:4ea8812e message: org.openhab.binding.homeduino.internal.messages.homeduino.Pir2Message@1d47034
18:33:15.540 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1520 15544 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:33:15.547 [DEBUG] [g.homeduino.handler.HomeduinoHandler] - Received message from bridge: homeduino:homeduino:4ea8812e message: org.openhab.binding.homeduino.internal.messages.homeduino.Pir2Message@3aff7
18:33:15.799 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1520 15540 0 0 0 0 0 01100110011001100110011001100110011001100110011002
18:33:15.804 [DEBUG] [g.homeduino.handler.HomeduinoHandler] - Received message from bridge: homeduino:homeduino:4ea8812e message: org.openhab.binding.homeduino.internal.messages.homeduino.Pir2Message@1517e77
18:33:19.074 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Checking Homeduino transceiver connection, thing status = ONLINE
18:33:29.266 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 508 1520 15560 0 0 0 0 0 01100110011001100110011001100110011001100110011002
- After installing the new snapshot of homeduino from today there were several new devices in my inbox (paper ui). E.g. weather1, switch2. I ignored them without any problems with the installed devices. What is the reason for this behavior?
Greetings and a nice evening
Johannes
You even receive 4 or more events, I think the expire binding might come to the rescue here
Did you recreate your transceiver? if not can you share the names of items, especially the difference between the ones which were already configured and newly discovered (and ignored) items. I had the same problem but I thought it to be caused by the fact that I recreated my transmitter to properly support and test the repeats parameter.
An example of such a name: homeduino:weather1:d05c1755:29_1
Hi Martin,
No recreation of the transceiver
My fault, I checked the log and only found homeduino:weather1:4ea8812e:186_3. This was the only discovered device. Sorry I didn’t want to create disorder.
I don’t understand your proposal with the expire binding. After initializing of the sensor I have the state “open”, and no other defined states. Could you please explain your solution?
Greetings and have a good night
johannes
Hmm, not as trivial as I thought, but the main problem is that the device does not send an off and sends multiple on’s.
But I think the usage of the expire binding requires configuring the items by hand, I’ll check it out first.
I did a quick test, if you configure your item manually like the following it works
Switch TestSwitch2 {channel="homeduino:switch1:d05c1755:17638398_1:command", expire="15s"}
You can copy this identifier from the overview of things, eg. by using inspect element in your browser and copying it from that view.
I have tested it, but my problem is, that the switch or contact changed between a defined state and a undefined state. My problem is the rule for such a state change. Can you point me in to the right direction…
Thank you!
You can also use expire="15s,OFF" to switch to off instead. Can you post your current rule as a start?
Hi Martin,
here a rule example:
rule "Test Bewegungsmelder Wohnzimmer"
when
Item Bewegungsmelder_Wohnzimmer_contact changed to CLOSED
then
logInfo("pir2", "Bewegungsmelder Wohnzimmer")
end
and the .items file contains:
Contact Bewegungsmelder_Wohnzimmer_contact {channel="homeduino:pir2:4ea8812e:10_21:contact", expire="5s,OPEN"}
These rule doesn’t fire because there is no state defined. There is no state “Open” and no state “Closed” defined. Only the command reveiveUpdate fires the rule but between 2-4 times. I made the same test with item switch (On, Off) with the same result.
Please give me a hint.
Thank you!
Lets start with the simple question, did you install the expire binding?
Can it be that you reversed the states, I think it should be closed by default. So the rule should state changed to OPEN
expire should be set to CLOSED.
Expire binding is installed, after the first initialization the state was set to open, that’s why I have chosen open for the expire option. But after the first initialization I never could find again a state of the item.
I will test it with reversed state (closed).
Thank you and have a nice evening!
Ok, the reversed state was the reason! Thank you for your patience!
Now every thing runs like expected.
Hey! Nice to see that someone is developing this binding!
I’m also using pimatic for 433 sending and receiving.
Would be nice if there were support for the following protocols:
switch14
contact4
switch2
switch3
best regards!