Interest in a homeduino binding

I assume it occurred during sending signals via openHAB, it’s caused by the performance of the/your transmitter. It cannot keep it with the speed on which fire requests at it. You should be able to improve it by decreasing the number of repeats. I hope that it will recover after a minute so should not have to restart openHAB completely.

What version do you have installed? I was broken in the past but has been tested successfully by others as well.

I just added a new version with additional support for switch3 and contact4, the total support is now the following:

  • contact4
  • switch3
  • pir1
  • pir2
  • switch1
  • switch2
  • switch4
  • weather1

Download: 2.1.0.201702211848

Notes at: https://hackmd.io/s/BkVLvEeFe

You’re great! Will check the installed version and install the latest.
Why isn’t this binding in the official repo?

Thanks in advance!

Because its still work in progress and I want to make sure that the the maintainers of the homeduino / rfcontroljs don’t have any problems with us porting the reverse engineered protocols to another platform; before putting it in to the official repo

Thumbs up! Just updated to your latest release. It discovered my door contact (CONTAC4) instantly. Works great!

Thanks for your work! Is it possible to enable debug / raw output when receiving rf? This way I would be able to give you some data for switch14 if needed.

See:

Would it be possible to implement rolling1protocol - https://github.com/pimatic/pimatic/issues/386?
Sending only, but that should be enough.

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) :slight_smile:
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: https://github.com/pimatic/rfcontroljs/blob/master/src/protocols/switch14.coffee 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.