Any updates on the board? I really like the design. Where are you getting the casings for the PCB?

@jkandasa It seems to be stable now. Think that it was a one off issue. Ive now got both HomeAssistant and MyController working on the same MQTT in/out topics.

However, when a sensor calls back to the controller, both HomeAssistant and myController send out replies, and due to this, i think the messages clash, and the controllers endup sending it multiple times.

Have to think of a way to make only one respond to requests.

@jkandasa Not sure what the issue is, but the adapter seems to be working fine now. Ill leave it running for a day and see if the data issue reappears. I was trying to get HomeAssistant and myController to work off the same MQTT topics. maybe thats what cause the data issue.

@jkandasa The serial2MQTT adapter worked for a while, but then it started to fail. Looking at the logs, its not receiving the data from serial properly

2017-08-07 18:04:00,942 ERROR [Thread-1] [org.mycontroller.serial2mqtt.gateway.MessageMonitorThread:66] Exception on processing [RawMessage(gatewayId=null, data=%ﾍﾲￌￒ￲▒ￍﾞﾉ<*▒oﾰﾲￋﾛ￤▒0;255;3;0;9;TSF:MSG:READ,254-254-0,s=255,c=3,t=1,pt=0,l=0,sg=0:, subData=null, isTxMessage=false, networkType=MY_SENSORS, timestamp=1502125439421)],
java.lang.NumberFormatException: For input string: "%ﾍﾲￌￒ￲▒ￍﾞﾉ<*▒oﾰﾲￋﾛ￤▒0"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:569)
        at java.lang.Integer.valueOf(Integer.java:766)
        at org.mycontroller.serial2mqtt.gateway.MessageEngine.postOnMqtt(MessageEngine.java:53)
        at org.mycontroller.serial2mqtt.gateway.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:63)
        at org.mycontroller.serial2mqtt.gateway.MessageMonitorThread.run(MessageMonitorThread.java:85)
        at java.lang.Thread.run(Thread.java:745)

@jkandasa Thank you very much, will give it a go over the weekend.

Thanks Nca78.
I used the MY_PARENT_NODE_ID but didnt use the MY_PARENT_NODE_IS_STATIC option and it works!

The button node will be in sleep mode until it a button is pressed. So in that case, will it ever need to communicate to the GW?

@mfalkvidd I will try this out today and see if it helps. But this will just make the child node always communicate with the Repeater node. What im trying to do is : https://forum.mysensors.org/topic/6984/pairing-nodes-with-each-other

So on first boot, i want the child node to goto the GW and get a node-ID and register itself. Afterwards I want it to pair to a Repeater node.

If I have multiple repeater nodes, is there a way to force a child node to got to a repeater Node and not to the GW? I have tried to use the setDestination function but that still goes via GW.

Hi,

Ive been playing around with MySensors for a while now and I have become quite fond of having things which I can automate and control from my bed.

Since I am retro fitting conventional ceiling lamps and heaters, I have to bypass the wall switches and keep them in always ON mode (to provide mains power). The actual ON/OFF mechanism is controlled by the sensor nodes, which are placed near-by the bulb holder or end of the wire for other items. In this way, I have no physical switch with which I can control the actual bulb. I do prefer the good old and trusty wall switch and it’s a good to have when you have guests, whom do not have access to the controller.

Some of the “commercial” home automation products come with a separate remote control device which acts as a physical (but wireless) button which can be paired to the actual device.

I was wondering if there was a way that I can create a paring mechanism whereby I can join two senor nodes together (wireless), and not have the need to go through a GW. So basically, a sensor node which can be controlled by a controller software(HA/OpenHab) and multiple button nodes.

For example, consider the setup below:

Setup

• Controller - Some controller which can be accessed by phone (Web based) eg HomeAssistant, OpenHab.
• Serial GW - Connected to controller and manages the MySensors network.
• Control Node - Connected with the GW (as normal) and is always on. This node has sensors and actuators which we want to control eg Relays
• btnNode1 - This is a node with just a button. It is connected to Node1 (paired node), acting as a wireless button to control the main node.
• btnNode2 - Same as btnNode1, but placed in different part of room.

What I want to Do

1. Setup a node which is connected to the the GW and has a node-id. This is the node we want to control. Call this Control Node
2. Setup another node which will act as a Button Node and can connect to:

• The GW, to get node-id and for pairing session.
• The Control Node, to toggle the relay, switch, etc.

Button Node

• Normal Operation

1. When a button is pressed, the node wakes up.
2. Send a toggle command to the Control node with the secret-key.

• Pairing Operation

1. When the button is pushed for more than 3 secs, the node goes switches into paring mode.
2. Connects to the GW and obtains a node-id (if it is a brand new node)
3. Obtains a secret-key/network key from the GW (Security mechanism, something like a two-factor thing)
4. Puts itself into receive mode.
5. When it receives a pairing request it responds back to the pairing node with its node-id and the secret-key/network id.
6. On confirmation, it stores the network-id and pairing nodes’s node-id to EEPROM.

Control Node

• Pairing Operation

1. When a button is pressed for 3 secs, the node changes its state to pairing mode
2. Sends a network wide request to locate the Button Node
3. When the button node
4. When it receives a request for pairing, it stores the Control node's Id into EEPROM

Has anyone done anything like this? What options do I have in creating functionality for this using mySensors.

Any help and advice will be greatly appreciated.

@jkandasa has the independent service been created? I would really love to see this feature. Im using Home Assistant for overall home automation. But I want to manage MySensors with MyController due to the better features to handle MySensor Nodes.