Converting a sketch from 1.5.x to 2.0.x

[mfalkvidd]

@Maurizio-Collu the examples for 2.0 are included in the library. They can be opened directly fromthe Examples menu in the Arduino IDE. It is also possible to fetch the examples from github, see https://github.com/mysensors/MySensors/tree/development/examples/RelayActuator For the relay example.

[Boots33]

@Maurizio-Collu

You have a few mistakes in your sketch, Download the V2 sketch that @mfalkvidd has pointed you to and compare the two side by side. you will soon see where you have gone wrong. don't forget you will need to update your gateway to V2 as well, a version 1.5 gateway will not connect with a version 2 node.

[Maurizio Collu]

@mfalkvidd @Boots33

Thanks a lot, I knew I was missing something basic. For the newbies like me, it would be good to mention this somewhere (if you have not done so already and I missed it).

In the Home Assistant website it is mentioned that they only support 1.4 and 1.5. I'm trying with 2.0.

Thanks Again

[martinhjelmare]

@Maurizio-Collu

2.0 should work with home assistant, but all new features of 2.0 are not supported yet. WIP.

[rchamp]

I'm trying to upgrade my gateway to 2.0, but every time I go to upload, I get a 'error' not in sync.

I'm using just a standard nano w/ NRF24.

Note, my hardware profile is set properly to nano, 328p and proper com.

I restart app, and switched to my APM hardware profile and loaded my new 2.0 sensor code into my new APM node (DHT11 + motion) and was able to upload no problem.

Is there something i'm missing for the gateway?

Idon'tunderstandwhatwouldcauseittostopbeingabletocommunicate,

[hek]

Are you able to upload some other sketch to the nano?
Or has something bad happen to the FTDI chip on your nano perhaps?

[moskovskiy82]

Just for clarification. V2.0 gateway (MQTT client esp8266) - will it work with the 1.5/1.6 sensors? Or everything needs to be flashed as soon as possible?

[rchamp]

@hek it's actually a close nano with an FTDI board connected via serial inputs. I had this directly connected to my Vera, and communication with my old sensors was working just fine.

EDIT: Fixed. All in all, it was user error. I was trying to connect through FTDI adapter. I unplugged FTDI board, connected USB directly to nano clone, and upload worked fine.

Do I need to update mysensors plugin as well on Vera UI5?

[hek]

@rchamp said:

Do I need to update mysensors plugin as well on Vera UI5?

No, shouldn't be necessary.

[hek]

@moskovskiy82 said:

Just for clarification. V2.0 gateway (MQTT client esp8266) - will it work with the 1.5/1.6 sensors?

You could try, but the recommendation is to update the nodes as well.

[Maurizio Collu]

@martinhjelmare
Thanks Martin.

I uploaded the GatewaySerial to the arduino working as gateway, but if I upload the sketch and I open the monitor, I obtain this error:

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)
0;255;3;0;9;TSM:INIT
0;255;3;0;9;!TSM:RADIO:FAIL
0;255;3;0;9;!TSM:FAILURE
0;255;3;0;9;TSM:PDT

What does it mean?

[Maurizio Collu]

@martinhjelmare
Plus, when starting home assistant, I get this error

16-07-26 23:03:44 homeassistant.bootstrap: Error during setup of component mysensors
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/mysensors.py", line 62, in setup_gateway
socket.inet_aton(device)
OSError: illegal IP address string passed to inet_aton

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/homeassistant/bootstrap.py", line 150, in _setup_component
if not component.setup(hass, config):
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/mysensors.py", line 109, in setup
device, persistence_file, baud_rate, tcp_port)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/mysensors.py", line 73, in setup_gateway
baud=baud_rate)
File "/home/pi/.homeassistant/deps/mysensors/mysensors.py", line 326, in init
persistence_file, protocol_version)
File "/home/pi/.homeassistant/deps/mysensors/mysensors.py", line 40, in init
self.const = _const
UnboundLocalError: local variable '_const' referenced before assignment

[martinhjelmare]

@Maurizio-Collu

Regarding the error in home assistant, that's a bug, due to specifying mysensors version other than 1.4 or 1.5. Use 1.5 and you should be fine. The bug is fixed in the dev branch of pymysensors and will be fixed in home assistant when real mysensors 2.0 support is merged. WIP.

Please post home assistant topics in the home assistant category under controllers. This is off topic in this thread.

[martinhjelmare]

@Maurizio-Collu said:

@martinhjelmare
Thanks Martin.

I uploaded the GatewaySerial to the arduino working as gateway, but if I upload the sketch and I open the monitor, I obtain this error:

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)
0;255;3;0;9;TSM:INIT
0;255;3;0;9;!TSM:RADIO:FAIL
0;255;3;0;9;!TSM:FAILURE
0;255;3;0;9;TSM:PDT

What does it mean?

@tekka knows this best, and he wrote a post explaining some of those messages here:
https://forum.mysensors.org/topic/4347/can-t-get-sensors-talking/3

[Maurizio Collu]

@martinhjelmare Thanks a ot.
Is there any guide/manual where all these messages are explained?

Plus, is there anywhere written what all these terms mean?

TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

Kind Regards

[mfalkvidd]

@Maurizio-Collu do you mean except the link martinhjelmare provided?

[Maurizio Collu]

@mfalkvidd Yes, basically this part (I'm sure it is explained somewhere, but I can't find where)

255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

SOrry for my newbieness...

[tekka]

@Maurizio-Collu Yes, the doc is in preparation, the meaning of these messages is described here (this is a PR that harmonizes the log message and will be pushed to 2.0.1).

In brief:

TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

TSP:MSG:SEND refers to message sending function in the transport state machine

255-255-0-0 is the routing information, i.e. sender-last-next-destination

s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

• s=sensor ID (255 = internal)
• c=command (3 = C_INTERNAL)
• t=type (3 = I_ID_REQUEST)
• pt=payload type (0 = P_STRING)
• l=message length (0)
• sg=signature flag (0 = not signed)
• ft=failed transmission counter (0 = no failed uplink transmission at this* oint)
• st=send status (OK)
• : actual message (empty)

=> Your node has no assigned ID (=255) and is requesting a new ID from the controller.

Please refer to the serial protocol or API for additional information.

Good luck!

[pndgt0]

Hi,
I was trying to implement the irrigation controller but realized that was not migrated to MySensors 2.0.
I followed the instructions provided in the first post and arrived to a version that compiles with no errors. Nonetheless, as I am newbie, I would appreciate if someone could review some changes that I am not sure about. Those changes are related with the original sketch which has direct calls to process() in several while statements. First I tried to change the process() with _process() but several errors appeared, so finally I removed all the calls to process() but am not sure. I have the modified code here IrrigationController.ino in which I commented the lines added / deleted / modified. Any help / direction would be greatly appreciated.

[Boots33]

@pndgt0

The sketches that require external libraries are not included in the V2 install anymore but they are available here in the new V2 format. You will find the irrigation sketch there.