New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rflink 433Mhz gateway platform and components #4547

Merged
merged 75 commits into from Jan 31, 2017

Conversation

Projects
None yet
@aequitas
Copy link
Contributor

aequitas commented Nov 23, 2016

Description: The change is intended to add support for the Rflink gateway devices (http://www.nemcon.nl/blog2/ & https://www.nodo-shop.nl/nl/21-rflink-gateway) which allow receiving and sending of 433Mhz packets much like rfxtrx. It builds on the rflink python package (https://pypi.python.org/pypi/rflink) which was initiated for this cause.

At the moment this is a very rough (but working) sketch with a lot of debugging. Expect much of the code to be changed, move around or migrate towards the rflink package to be available for a broader audience.

Feel free to leave feedback or feature requests.

I try to model this close to the rfxtrx platform but since this platform is developed asyncio first not a lot can be shared (yet).

Please help by testing this out with your own Rflink device and providing feedback.

What works at the moment:

  • Receiving and sending of on/off switch events to control lights.
  • Automatically adding discovered devices (but not stored yet)
  • Temparature & humidity sensors

Todos:

  • add tests
  • fix linting
  • cleanup
  • doorbell support
  • covers support?
  • persistent devices from configuration.yaml
  • assumed state configuration? (per device?)
  • temperature unit per device configuration
  • (debug) logging through log framework
  • shared known devices (light can be configured as switch)
  • component.rflink spawns devices? or event to create platform device?
  • use service pattern instead of direct bus events?
  • rflink unsupported devices debug enable
  • leave last box unchecked
  • config validation
  • loading previous state from recorder

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#1715

Example entry for configuration.yaml (if applicable):

rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__0042_55632313338351B08080-if00
  # send simultaneous commands as quickly as possible (may cause commands to fail)
  # wait_for_ack: false
  # ignore_device:
  #   - digitech_*
 
light:
  - platform: rflink
    # adds new devices to this group if not configured below
    new_devices_group: New Rflink Lights
    devices:
      newkaku_00000001_a:
        name: bedroom
      newkaku_00000001_b:
        name: kitchen
        aliasses:
          - kaku_000000_3

sensor:
  - platform: rflink
    # adds new devices to this group if not configured below
    new_devices_group: New Rflink Sensors
    devices:
      digitech_002f:
        # a single rflink packet can contain multiple values (eg: temperature and humidity)
        # setting value_key allows to specify which key should be used from the packet
        value_key: temperature

switch:
  - platform: rflink
    devices:
      newkaku_00000001_1:
        name: ventilator
        icon: mdi:fan

If you want to test this on for example your laptop/desktop without having to modify your existing HASS server but you don't want to have your Rflink hooked to the serial port of your laptop/desktop, this module support connecting through TCP as well. On the host connected to the Rflink install socat and run:

socat -ddd /dev/ttyACM0,b57600 TCP-LISTEN:1234,reuseaddr

This will expose the serial line on a tcp connection.

Then configure the component like this:

rflink:
  host: hostname
  port: 1234

light:
  - platform: rflink
@mention-bot

This comment has been minimized.

Copy link

mention-bot commented Nov 23, 2016

@aequitas, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @fabaff and @rmkraus to be potential reviewers.

@aequitas aequitas force-pushed the aequitas:rflink branch 3 times, most recently Nov 23, 2016

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Nov 27, 2016

Support for loading devices from configuration added.

@aequitas aequitas force-pushed the aequitas:rflink branch 4 times, most recently Nov 27, 2016

homeassistant/components/rflink.py Outdated
"""Send command to rflink gateway via asyncio transport/protocol."""
command = event.data[ATTR_COMMAND]
yield from protocol.send_command_ack(*command)
def send_command(event):

This comment has been minimized.

@houndci-bot

houndci-bot Dec 1, 2016

expected 1 blank line, found 0

@aequitas aequitas force-pushed the aequitas:rflink branch Dec 1, 2016

@balloob

This comment has been minimized.

Copy link
Member

balloob commented Dec 2, 2016

Please change title and leave a note when ready for review 👍

@aequitas aequitas force-pushed the aequitas:rflink branch 4 times, most recently Dec 4, 2016

@Danielhiversen

This comment has been minimized.

Copy link
Member

Danielhiversen commented Dec 16, 2016

Any progress on this?

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Dec 16, 2016

@Danielhiversen Currently working on refactoring the Python module (https://github.com/aequitas/python-rflink). Hope to work those changes into the component this weekend to simplify the HA implementation a little.

@mjj4791

This comment has been minimized.

Copy link
Contributor

mjj4791 commented Dec 18, 2016

@aequitas
I was working on an rflink component as well; but found your implementation cleaner. So I started evaluating your implementation. Overall, not disappointed at all!

If you are interested, I used your first beta and added:

  • explicit config checking
  • enhanced reading sensor config (current implementation only allows for 1 value_type per sensor in configfile)
    • allow for multiple value_types per sensordevice
    • configure unit of measurement per value_type (with fallback to default unit)
  • added conversions in rflink library for all value types rflink supports

Two things to add to your todo list:

  • (re)connecting to rflink on separate reconnect loop (reconnect when disconnected & allow HA to start when rflink is not found (yet))
  • add signal-repetitions config to send out commands more than once (sometimes lights are not switched due to distance / other devices transmitting)

I have attached my modifications to your code in a zip file (based on rflink 0.0.7 library)
rflink.zip

@pepeEL

This comment has been minimized.

Copy link
Contributor

pepeEL commented Dec 19, 2016

Hi
But how i can add configuration for my sensor temp from weather station ? In Domoticz System it will be automatically found my devices/sensors. Now how i can to this step by step in HA ?

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Dec 19, 2016

@mjj4791 cool, thanks for contributing, I will check it out soon.

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Dec 19, 2016

@pepeEL it will automatically detect and add any new sensor it finds. Currently not all sensors are supported, this should be fixed soon.

@pepeEL

This comment has been minimized.

Copy link
Contributor

pepeEL commented Dec 19, 2016

But can you describe step by step how add RFLink Gateway(i have on Arduino Mega by USB) to Home Assistan and then how add devices like sensor temp, like blinds somfy, like switch anslut(from Jula Shop) or sensor/switch contact ? Please i am begginer and i want to go to working HA but now i use Domoticz and Domoticz is no good.

@Danielhiversen

This comment has been minimized.

Copy link
Member

Danielhiversen commented Dec 19, 2016

@pepeEL This is work in progress, and it is currently not added to the official version of HA

@pepeEL

This comment has been minimized.

Copy link
Contributor

pepeEL commented Dec 19, 2016

ok i am waiting for add officialy with good easy manual how configure it and add devices.

Thanks for good JOB :)

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Dec 19, 2016

@mjj4791 I added your changes to rflink: aequitas/python-rflink@42e4380

Refactored them a little to match the style and added the tests.

For the changes to home-assistant, could you please create a pullrequest on this branch? It will be easier for me to maintain and give feedback.

@boschr

This comment has been minimized.

Copy link

boschr commented Dec 19, 2016

Keep up the good work! When RFLink is implemented I will try HASS instead of Domoticz.

@pepeEL

This comment has been minimized.

Copy link
Contributor

pepeEL commented Dec 20, 2016

I also wait for working RFLink and also start use HA instead Domoticz. But now i search how use Razberry Zwave. How install and how pair with devices.

@kabturek

This comment has been minimized.

Copy link

kabturek commented Dec 20, 2016

Thanks for work, i've tested it in HA and it discovered my switches (and my neighbors too ;-)
I have some problems with OFF state beeing ON but that is a problem with rflink too afaik (OFF turns ON my light).
Good work!

@kabturek

This comment has been minimized.

Copy link

kabturek commented Dec 20, 2016

yeah so i've found that i have to:
10;TRISTATEINVERT=ON;
to rflink, will test at home

@Lampy09

This comment has been minimized.

Copy link

Lampy09 commented Feb 8, 2017

@aequitas: Big thumbs up for this, I'm using this with success now for my Kaku lights and a oregon weather station. However I have a couple of small issues, my Kaku lights are also linked to a group switch on my remote but HomeAssitants doesn't pick this up. I was able to capture the command with rflink -vv:

DEBUG:rflink.protocol:received data: 20;01;NewKaku;ID=009d1be
DEBUG:rflink.protocol:received data: 6;SWITCH=1;CMD=ALLON;
DEBUG:rflink.protocol:got packet: 20;01;NewKaku;ID=009d1be6;SWITCH=1;CMD=ALLON;
DEBUG:rflink.protocol:decoded packet: {'id': '009d1be6', 'node': 'gateway', 'switch': '1', 'protocol': 'newkaku', 'command': 'allon'}
DEBUG:rflink.protocol:got event: {'id': 'newkaku_009d1be6_1', 'command': 'allon'}
newkaku_009d1be6_1 allon

Can this also be integrated?

Another minor thing, HomeAssistant complained about the weather sensor's 'sensor_type' should be required but I'm not sure this is true I though I've read somewhere in the docs they're optional right?

Edit:
I can also see some RFLink related errors in the log, however they're not triggered by me so I don't have a clue where they come from (my neighbor?)

17-02-09 07:32:48 WARNING (MainThread) [rflink.protocol] no valid packet 17-02-09 07:32:49 ERROR (MainThread) [rflink.protocol] failed to parse packet: None Traceback (most recent call last): File "/home/homeassistant/.homeassistant/deps/rflink/protocol.py", line 98, in handle_raw_packet packet = decode_packet(raw_packet) File "/home/homeassistant/.homeassistant/deps/rflink/parser.py", line 229, in decode_packet key, value = attr.lower().split('=') ValueError: too many values to unpack (expected 2)

Ordep pushed a commit to Ordep/home-assistant that referenced this pull request Feb 9, 2017

Rflink 433Mhz gateway platform and components (home-assistant#4547)
* Initial sketches of rflink component.

* Add requirement.

* Properly load configuration.

* Bump rflink for graceful parse errors and protocol callback.

* Cleanup, documentation and linting.

* More documentation, first sensor implementation (temp & hum).

* Add brightness/dim support for newkaku protocol.

* Use separate class for dimmables.

* Make sure non-dimmable newkaku devices are turned on.

* Move some code around, add switches. Support loading from config.

* Fix bug in ignoring devices.

* Fix initial state assumption.

* Improve reliability on invalid conditions.

* Allow configuration of group for new devices.

* Sensor icons.

* Fix parsing negative numbers.

* Correct icon.

* Allow sending commands serial.

* Pluralize.

* Allow adding sensors from config.

* Fix ignoring devices and bugs in previous commit.

* Share know devices so devices from configuration don't get added as lights.

* Lookup unit from value_key.

* Remove debug.

* Start implementing event protocol in place of packet protocol.

- Added first test suite for sensors.
- This currently breaks light and switch.

* Refactor switch component to fit new rflink changes. Add test suite.

* Fix style.

* Refactor and test lights. Bring coverage to 100%.

* Use non-broken and production tested rflink module.

* Update requirements.

* Bump for logging.

* Improve readability.

* Do not use global variable but keep known device state in intended place.

* Improve docs.

* Make icon support generic.

* Disable overriding icons in config, as it belongs in customization. Only keep custom icon for entities that are able to detect a icon based on the thing they represent (sensors in this case).

* Implement configuration schema, overall refactor of magic values.

* Fix bug in config/test wait_for_ack.

* Small refactors.

* Move command logic into separate class.

* Convert command sending logic to class based pattern instead of using the event bus.

* Start not using bus for rflink event propagation to platforms.

* Do not use event bus for all entity types.

* Fire an event on the bus for every switch incoming rflink command.

* Resolve lint errors, remove some old code.

* Known devices no longer need to be registered separately.

* Log bus events.

* Event callback is a..... callback.

* Use full entity id for events.

* Move event sending to entity.

* Log incoming events.

* Make firing events optional inline with rfxtrx.

* Add foundation for signal repetition.

* Add signal repetition config and tests.

* Make plain switchable type explicitly configurable.

* Enable default entity settings for automatically added entities as well.

* Prevent default configuration leaking accross entities.

* Make sure device defaults don't get overwritten by defaults further down.

* Don't let fast state switching and repetitions turn your house into a disco.

* Make repetitions more responsive.

* Disable on/off fallback on dimmables as it currently doesn't play nice with repetitions.

* Use rflink that allows send_command_ack to be safely cancelled.

* Reduce duplication and make repeat work for non-ack.

* Implement reconnection logic.

* Improve reconnection logic.

* Also cancel repetitions when entity state is changed due to external command.

* Update requirements.

* Fix linting.

* Fix spelling.

* Don't lie.

* Fix lint.

* Support for automatically creating protocol translation (fixes spaces in device names).

* Returned support for dimmable and on/off entity.

* Duplicate code to fix linting issues with inheritance.

* Allow overriding unit of measurement from config.
@lmolent

This comment has been minimized.

Copy link

lmolent commented Feb 13, 2017

Hi @aequitas, sorry for delay, these motion sensors are based on chip EV1527, as You can see, only ON command was sent:

DEBUG:rflink.protocol:received data: 20;06;EV1527;ID=045a42;SWITCH=06
DEBUG:rflink.protocol:received data: ;CMD=ON;
DEBUG:rflink.protocol:got packet: 20;06;EV1527;ID=045a42;SWITCH=06;CMD=ON;
DEBUG:rflink.protocol:decoded packet: {'switch': '06', 'id': '045a42', 'command': 'on', 'node': 'gateway', 'protocol': 'ev1527'}
DEBUG:rflink.protocol:got event: {'id': 'ev1527_045a42_06', 'command': 'on'}
ev1527_045a42_06 on
DEBUG:rflink.protocol:received data: 20;07;EV1527;ID=045a42;SWITCH=06
DEBUG:rflink.protocol:received data: ;CMD=ON;
DEBUG:rflink.protocol:got packet: 20;07;EV1527;ID=045a42;SWITCH=06;CMD=ON;
DEBUG:rflink.protocol:decoded packet: {'switch': '06', 'id': '045a42', 'command': 'on', 'node': 'gateway', 'protocol': 'ev1527'}
DEBUG:rflink.protocol:got event: {'id': 'ev1527_045a42_06', 'command': 'on'}
ev1527_045a42_06 on

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Feb 13, 2017

@Lampy09 I will start working on group support.

Sensor type is mandatory for sensors from configuration. I documented this wrong.

Do you only receive the unpack exception on restart/startup? This is a known issue that the initial data is incomplete and can be ignored. I will try to suppress that error.

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Feb 13, 2017

@lmolent no problem. The rflink -vv dumps all data received by the Rflink device. If it does not send any data for 'off' there is not much we can do :(. Maybe the rflink device does not properly decode the 'off' commands? Connecting to the rflink manually and turning on debug mode (http://www.nemcon.nl/blog2/development) should give some information on this. You can try the rflink forum/maintainer to have this resolved: http://www.nemcon.nl/blog2/contact

@aequitas aequitas referenced this pull request Feb 13, 2017

Closed

Rflink features/bugs #5965

4 of 5 tasks complete
@lmolent

This comment has been minimized.

Copy link

lmolent commented Feb 22, 2017

Hi, @aequitas "fire_event: true" in "device_defaults:" section e.g:

switch:
  platform: rflink
  device_defaults:
    signal_repetitions: 2
    fire_event: true
  devices:
    ev1527_045a42_06:
      name: test1
    ev1527_074842_06:
      name: test2

probably doesn't works. It must be configured in every device section e.g:

switch:
  platform: rflink
  device_defaults:
    signal_repetitions: 2
  devices:
    ev1527_045a42_06:
      name: test1
      fire_event: true
    ev1527_074842_06:
      name: test2
      fire_event: true

Tested with rflink.light and rflink.switch and homeassistant==0.38.4. No button_pressed event is fired.

Thank You.

@MacDennis76

This comment has been minimized.

Copy link

MacDennis76 commented May 6, 2017

@aequitas : really nice work so far!
I have a RFLink and various KaKu devices and I can help you test/debug if needed.

Tested working for now:
AMT-606
AWMD-250
AWST-8802
And also various Cresta, Auriol & Alecto temperature sensors.
Still need to test motion sensor and various wall plugs.

I also own the ACDB-7000AC doorbell. I had some struggles getting it to work but I found a workaround.

Some debug data:

17-05-06 22:46:24 DEBUG (MainThread) [rflink.protocol] received data: 20;07;NewKaku;ID=00c021ca;SWITCH
17-05-06 22:46:24 DEBUG (MainThread) [rflink.protocol] received data: =1;CMD=ALLON;
17-05-06 22:46:24 DEBUG (MainThread) [rflink.protocol] got packet: 20;07;NewKaku;ID=00c021ca;SWITCH=1;CMD=ALLON;
17-05-06 22:46:24 DEBUG (MainThread) [rflink.protocol] decoded packet: {'protocol': 'newkaku', 'switch': '1', 'id': '00c021ca', 'node': 'gateway', 'command': 'allon'}
17-05-06 22:46:24 DEBUG (MainThread) [rflink.protocol] got event: {'command': 'allon', 'id': 'newkaku_00c021ca_1'}
17-05-06 22:46:24 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'command': 'allon', 'id': 'newkaku_00c021ca_1'}

It sends the 'allon' command but this is a group command. Looking at the RFLink source code group commands only seems to be supported yet in the Light component and not in the Switch component.

I added the following in my lights configuration:

platform: rflink
automatic_add: false
device_defaults:
  devices:
  newkaku_00c021ca_1:
    name: Doorbell
    type: toggle
    fire_event: true

And I used this automation rule:

alias: Doorbell pressed rule
initial_state: 'on'
trigger:
  platform: event
  event_type: button_pressed
  event_data: {'entity_id': 'light.Doorbell', 'state': 'allon'}
action:
  service: logbook.log
  data:
    name: 'Doorbell'
    message: 'was pressed

When the doorbell is pressed the automation rule is triggered and I see an entry in the logbook.

Any idea when full support for a doorbell (as a switch) will be implemented?

Thank you!

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented May 7, 2017

@MacDennis76 hi, thanks for providing the feedback. I don't have a doorbell so I'm not able to test it myself. Nice to see how Kaku implements this.

I think the doorbell implementation you wrote is as close as it can get. However I would not use the device_defaults but just create a switch device. Switches support the group commands as well (https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/rflink.py#L390).

There is not really a 'doorbell' concept in HA that i'm aware of (I can't find any other than the Ring component). So I would't not what else to implement. If you have a use case example I can work with I can have a look or if you have a implementation idea feel free to create a PR.
Also does the doorbell send a alloff when it is released? Because otherwise the state of the doorbell switch would be constantly on.

I think for now subscribing to the event is the best solution to implement a doorbell and further logic.

@MacDennis76

This comment has been minimized.

Copy link

MacDennis76 commented May 8, 2017

@aequitas , thanks for the quick reply!

The doorbell does not send an 'alloff' command.
How would I add the doorbell as a swich? Because I have been unsuccessful so far. Simply moving it from my lights config to my switch config does not work:

  newkaku_00c021ca_1:
    name: Doorbell
    fire_event: true

I am new to HASS & Python (background is C#) but looking at this line 'allon' will be handled as a group command/event:
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/rflink.py#L134

But the rflink switch component has no logic which initializes the DATA_ENTITY_GROUP_LOOKUP collection, the rflink light component does have this logic and by default a light is part of a group.

When using rflink switch this line is called in the end:
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/rflink.py#L145

Is my conclusion correct that group support is still to be implemented in the rflink switch component?

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented May 8, 2017

@MacDennis76 ah yes, sorry, forgot about that. There is no reason a switch cannot be part of a group. I think I forgot it in the implementation. The event handling is to be overhauled anyways (#6767) so I will include it with that change.

For the short term you can keep using light as functionally it is not really different from a switch for what matters here I think.

@genestealer

This comment has been minimized.

Copy link

genestealer commented May 8, 2017

@MacDennis76
Would suggest you try:

Create the switch, which will fire an event when the doorbell is pressed.

switch:
  platform: rflink
    device_defaults:
      fire_event: true
    devices:
      newkaku_00c021ca_1:
        name: Doorbell

Create the automation to react to the event and also set the switch back to the OFF State ready for the next button press.

automation:
  alias: "Door Bell Pressed"
  trigger:
    platform: state
    entity_id: switch.doorbell
    state: 'on'
  action:
    - service: logbook.log
       data:
         name: 'Doorbell'
         message: 'was pressed 
    - service: notify.google_cloud_notify
      data_template:
        title: 'Doorbell'
        message: 'Someone is at the door!'
    - service: switch.turn_off
       entity_id: switch.doorbell

Change the actions to whatever you would like.

@MacDennis76

This comment has been minimized.

Copy link

MacDennis76 commented May 8, 2017

@genestealer Thanks, but if I understand @aequitas last comment correctly a doorbell can not be used as a switch yet. The current code does not call the handle_event method and thus does not fire an event when the doorbell is configured as a switch.

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented May 8, 2017

@MacDennis76 correct, but if you replace switch in @genestealer example with light it should work. Much like the example you provided.

@MacDennis76

This comment has been minimized.

Copy link

MacDennis76 commented May 8, 2017

@genestealer @aequitas Yes, I can confirm that automation script does work for a doorbell when used as a light. Looking forward to #6767 . If you need help testing any devices just let me know.

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented May 8, 2017

@MacDennis76 I will keep progress in that issue (and the subsequent pullrequest). If you subscribe (notifications) to the issue you will be notified when there are changes.

@genestealer

This comment has been minimized.

Copy link

genestealer commented May 8, 2017

As an alternative you could learn the doorbell has a custom RF switch within the Arduino memory which would overcome your issue.

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 22, 2017

guys - experimenting with RFLink now. I am a little familiar with HA (did some development myself) but do not get how this RFLINK component is meant to work. I see in the logs lots of 'device_id not known, adding new device'. Afaik nothing is happening afterwards. What is supposed to happen? I do not see my devices show up in the UI nor do I see anything happening in the configuration.yaml...

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 23, 2017

@aequitas any idea in working with two rflinks connected to the same HA? I have the 433 one but want to add the 867 as well. Not sure how that will work with HA...

@genestealer

This comment has been minimized.

Copy link

genestealer commented Jul 23, 2017

@jeroenterheerdt Have you tried putting both the 433Mhz and 868Mhz transmitters in parallel on the Arduino Mega? You may need to parallel up two level shifters if you have problems but I cannot see why having them in parallel wouldn't work.

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Jul 23, 2017

@jeroenterheerdt devices should appear on the homepage when detected. If not it might be your configuration hides them by default.

Alternatively add the device id's manually to the config as described in the documentation and see if that works.

I have not worked on supporting double receivers. The current implementation of python-rflink supports only one device at a time. I don't know if HA allows you to configure a component twice, never tried this.

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 23, 2017

@genestealer, how would putting a parallel work? @aequitas, I am pretty certain that HA will not allow double activation of the same component.

@genestealer

This comment has been minimized.

Copy link

genestealer commented Jul 23, 2017

@jeroenterheerdt, connect both transmitter Tx pins to MEGA tx3/Pin 14 (TX Data). then the data should be transmitted by both transmitters.

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 23, 2017

@genestealer do you have a sample of a double transmitter / receiver?

@genestealer

This comment has been minimized.

Copy link

genestealer commented Jul 23, 2017

@jeroenterheerdt No sorry, I would suggest you give it a go and see.

If not, back in Aug 2016 the Stuntteam did say "RFlink will be able to use both frequencies in an upcoming version."

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 24, 2017

@genestealer I have talked to the Nodoship guys and they told me it cannot be done this way. So, maybe we just need to solve this software side. Is there any way we could make your lib able to handle two rflinks?

@genestealer

This comment has been minimized.

Copy link

genestealer commented Jul 24, 2017

I wouldn't necessarily believe that. Do you have both transmitters to try?

@aequitas

This comment has been minimized.

Copy link
Contributor

aequitas commented Jul 24, 2017

This could be implemented in either https://github.com/aequitas/python-rflink or the HA component. Currently all connection logic is handled in the HA component (https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/rflink.py#L179). So that means either moving all that logic to python-rflink and simplifying the HA component or extend the HA component to allow creating and handling multiple connections. Both are pretty big tasks which I'm unable to put on my roadmap atm, but if you want to give a shot at implementing it yourself I can assist if needed.

@jeroenterheerdt

This comment has been minimized.

Copy link
Contributor

jeroenterheerdt commented Jul 24, 2017

@genestealer, no I do not and I also do not have the other components you mentioned. I had a look at the support forum for rflink and that give me not a lot of hope. The same question is answered there with a firm 'cannot be done'.

@home-assistant home-assistant locked and limited conversation to collaborators Dec 11, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.