Hello,
There is any specific forum to talk about pymysensors?
I have some doubts that I would like to clarify before proposing some changes on it.
For example: Is it possible to send internal messages to the gateway? like sending an I_VERSION request. I only saw the option to send regular messages to sensors with set_child_vale.
Thanks,
Alfredo.
If you want more information about this known issue, please follow this thread on the HA forum:
https://community.home-assistant.io/t/reconnect-mysensors-ethernet-gateway-when-it-is-back/3724
Hello,
I noticed that HA is not trying to reconnect the MySensors Ethernet gateway when it is temporary disconnected from the network.
Maybe this is not happening very often when using the Ethernet gateway. But with the new MySensors ESP8266 Wifi gateway it might happen from time to time. And it is a pity to have to restart HA to get it connected again.
Is this the normal behaviour or something is failing in my setup? I have to restart HA every time that the Gateway is temporary disconnected from the LAN.
Any suggestion? Can this be improved? Any Idea?
Thank you.
@mvader said:
I have the etekcity ZAP 433 remote & outlets. I just bought a 433 mhz transceiver off ebay and hooked it up to my raspberry pi2 and sniffed the codes.
Did you manage to turn on/off the etekcity outlets from the gateway?
I would like to do the same on my side... But I don't know too much about radio protocols.
Thanks!
@Yveaux , did you know that you are awesome?
There is an error on Pin labels!!! The print on the pcb is wrong. You are right!
I have two D2 and of course that I used the wrong one
Thank you so much!!!!
I didn't give up (yet...) I tried today to power the NRF from an external power supply. Same result. The esp8266 is rebooting after receiving some data as shown above. My conclusion is that the problem is on the esp8266 itself or in the power supply that I am using.
My last try will be to power the esp8266 from something different than the microUSB.
Just in case, this is the setup. Maybe I'm missing something very basic:
Regaards,
Alfredo.
@Yveaux ,
I tried with the esp mqtt client and I have similar issues. The node is reseting when receiving the radio signal.
This is the log:
ΕΎ Β‘9 C~0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0)
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSM:RADIO:OK
0;255;3;0;9;TSM:GW MODE
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 4
cnt
chg_B1:-40
0;255;3;0;9;TSM:READY
f r-40, scandone
.
connected with AFENO_DD, channel 6
dhcp client start...
..ip:192.168.1.82,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.82
0;255;3;0;9;No registration required
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
IP: 192.168.1.82
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;TSP:MSG:READ 6-6-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSP:MSG:BC
0;255;3;0;9;TSP:MSG:FPAR REQ (sender=6)
0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL)
0;255;3;0;9;TSP:MSG:GWL OK
Soft WDT reset
ctx: cont
sp: 3ffef6d0 end: 3ffefa50 offset: 01b0
>>>stack>>>
3ffef880: 00000000 3ffefc24 3ffefc24 40204d27
3ffef890: 40107050 00000000 3ffefc24 40204d27
3ffef8a0: 00000000 3ffefc24 00000000 40202336
3ffef8b0: 001e8480 3ffe0001 3ffefaaf 40202336
3ffef8c0: 00000000 0000000e 00000001 00000006
3ffef8d0: 00000000 00000000 00000006 00000006
3ffef8e0: 00000030 0000000e 00001928 402023d1
3ffef8f0: 00000001 3ffefaa8 00000006 402024ce
3ffef900: 00000008 00000006 3fff129c 00000027
3ffef910: 00000001 00000006 3ffefaa8 402035bc
3ffef920: 40107050 3ffef981 3ffefc24 00000061
3ffef930: 3ffef980 3ffefc24 3ffef980 40202336
3ffef940: 401054b2 000e937d 3ffefc24 3ffefc68
3ffef950: 4010556e 3ffee428 000e937d 00000000
3ffef960: 40105740 000e937d 3ffefc68 00000006
3ffef970: 000000ff 3ffefaa8 00000006 402026dd
3ffef980: 3ffefa06 00000006 40203bc8 00000006
3ffef990: 000000ff 3ffefaa8 00000006 402036fd
...
@Yveaux said:
last arduino core version and different power supply.
Hi, I'm using the version 2.3.0. I tried with different power supplies and all the same.
I will try the mqtt client just to see if it is working.
Thanks.
Sorry for my ignorance... But how can I measure the packets lost on individual links?
Do you mean to check the packets lost in a 1-way trip? Only from node1 to node2?
@Yveaux said:
please switch to the new 2.0.0 library, for your gateway, repeaters and sensors.
Esp support has been improved in there, and developer support will be faster.
Hello,
I switched to the new 2.0.0 and I still have the same problem:
connected with AFENO_DD, channel 6
dhcp client start...
0;255;3;0;9;TSM:READY
f r-40, scandone
.....ip:192.168.1.82,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.82
0;255;3;0;9;No registration required
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
0;255;3;0;9;TSP:MSG:READ 6-6-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSP:MSG:BC
0;255;3;0;9;TSP:MSG:FPAR REQ (sender=6)
0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL)
0;255;3;0;9;TSP:MSG:GWL OK
pm open,type:2 0
Soft WDT reset
ctx: cont
sp: 3ffef6b0 end: 3ffefa30 offset: 01b0
>>>stack>>>
3ffef860: 00000000 3ffefd08 3ffefd08 402048bb
3ffef870: 40107050 00000000 3ffefd08 402048bb
3ffef880: 00000000 3ffefd08 00000000 4020230f
3ffef890: 001e8480 3ffe0001 3ffefa8f 40202376
3ffef8a0: 00000000 0000000e 00000000 00000006
3ffef8b0: 00000000 00000000 00000006 00000006
...
What could be the reason for the reset?
Is it OK to power the NodeMCU from the microUSB?
Thank you!
@Yveaux said:
@Kosika please switch to the new 2.0.0 library
Ok. I will switch to 2.0.0 and let you know.
Thank you.
@Kosika said:
Problem now to figure out is how to connect a new sensor, as it restarts as soon as it's powered on.
Any ideas?
I have the same problem. I'm using the Esp8266Gateway sketch in the Lib v1.5 and have a NRF24 radio as described in the instructions.
Every time that I connect a new sensor, the MCU is restarting as you described. This is only happening when the Gateway is connected to a controller (Homeassistant or MYSController). If the gateway is not connected to any controller then it receive the data without any problem.
@Kosika, How did you solved the problem?
Hello,
I'm creating a "ping" sketch to measure the % of packet lost using the tmrh20 library. I will post it once it is finished but it is just a modification of the "GettingStarted" sketch.
It is very simple:
I'm measuring the number of packets lost and the turnaround time.
But doing some tests, I realised about something very strange that I don't understand...
Based on the sketch described above, both the node 1 and 2 are sending and receiving the same amount of data.
They both use the same commands to send and receive.
I have two hardware sensors/devices (let's call it A and B ) based on arduinos nano.
When I use A as Node 1 it gets 0.2% of packets lost. (B is used as Node 2)
When I use B as Node 1 it gets 15% of packets lost!! (A is used as Node 2)
Remember: Both nodes are sending and receiving the same amount of data.
I understand that the current, radio, noise, etc. might have an impact on the performance and range but why it is working fine on one way? And not in the other way? This is making me crazy. Both sensors are sending and receiving the same data. If one of them is not sending (or receiving) well, the performance still should be the same independent on who is acting as node 1 or 2.
What I am missing?
Thank you!
I'm wondering the same as @alexsh1 . How can I get 2.5-2.6V? There is an easy/cheap way to do it?
Hello,
What is the best way to measure the performance of one module at a given distance? I mean, how can I measure the number of packets lost?
Does anybody already created a "performace test sketch" to perofrm a better test?
@flopp said:
https://forum.mysensors.org/topic/666/debug-faq-and-how-ask-for-help
Sorry. I don't understand the answer. I'm looking for some information that I can't find on the web or Nordic's webpage and maybe someone in this form with enough experience already know the answer. I'm not looking for help or troubleshooting instructions.
I only would like to know the difference between the two chips. It is not clear for me from what I found on Nordics...
Thanks four your understanding.
Regards,
Alfredo.
Although most of the modules have the NRF24L01 or NRF24L01+ on it, I'm wondering what is the difference between the NRF24L01 and NRF2401.
Thank you!!!! I was getting crazy working only with the Serial monitor on both sides. I didn't know that the Controller is playing a key role on assigning the nodeID.
It is working now after connecting the gateway to HomeAssistant.
Thanks.
Regards.
Alfredo.
Thank you! It is working again 
Have a nice rest of the day.
Hello,
This feature request is related to a feature of the MySensors fortum webpage and not in the project itself.
I just wanted to report a bug on the Pushbullet subscription. When I try to associate my MySensor account with my Pushbullet Account I get the following error: The param 'redirect_uri' has an invalid value.
Thanks for your great support!
Regards,
afeno