search

sarnau / MMMMobileAlerts

Documentation about the protocols of ELV Mobile Alerts sensors plus a node MQTT gateway and an Arduino UDP gateway
46 stars 27 forks source link

data from msg did not match #45

Closed Flip76 closed 2 years ago

Flip76 commented 2 years ago

Since the latest commit I get the following output when starting the maserver:

Mobile-Alert Gateway : 001d8xxxxxxx
Name                 : MOBILEALERTS-Gateway
Use DHCP             : false
DHCP IP              : 192.168.100.8
Fixed IP             : 192.168.100.8
DHCP Netmask         : 255.255.254.0
Fixed DNS            : 192.168.100.100
Fixed Gateway        : 192.168.100.1
Use Proxy            : true
Proxy Address        : 192.168.100.3
Proxy Port           : 8070
Data Gateway         : www.data199.com

**data from msg did not match...**

Mobile-Alert Gateway : 001d8xxxxxxx
Name                 : MOBILEALERTS-Gateway
Use DHCP             : false
DHCP IP              : 192.168.100.8
Fixed IP             : 192.168.100.8
DHCP Netmask         : 255.255.254.0
Fixed DNS            : 192.168.100.100
Fixed Gateway        : 192.168.100.1
Use Proxy            : true
Proxy Address        : 192.168.100.3
Proxy Port           : 8070
Data Gateway         : www.data199.com

**data from msg did not match...**

end udp socket config

dict: {"ip":"192.168.100.3","port":8070,"log":"./MobileAlerts.log","cloudForward":true}

callback 1 reached
found following gateways:
0:
MAGateway :  001d8xxxxxxx
Name :  MOBILEALERTS-Gateway
DHCP :  false
DHCP_IP :  192.168.100.8
Fixed_IP :  192.168.100.8
DHCP_NMask :  255.255.254.0
Fixed_DNS :  192.168.100.100
Fixed_GW :  192.168.100.1
Proxy :  true
Proxy_Addr :  192.168.100.3
Proxy_Port :  8070
Data_GW :  www.data199.com
1:
MAGateway :  001d8xxxxxxx
Name :  MOBILEALERTS-Gateway
DHCP :  false
DHCP_IP :  192.168.100.8
Fixed_IP :  192.168.100.8
DHCP_NMask :  255.255.254.0
Fixed_DNS :  192.168.100.100
Fixed_GW :  192.168.100.1
Proxy :  true
Proxy_Addr :  192.168.100.3
Proxy_Port :  8070
Data_GW :  www.data199.com
starting proxy server...

In the config I set the

"localIPv4Address": "192.168.100.3"

as the server has multiple addresses and I want to listen on this specific interface.

GreatSUN commented 2 years ago

@Flip76 it does not look wrong from my perspective. We could probably add a check that if two requests come back from the same device, that we don't add/send out the info. But I would not say that this is an important thing to fix. The MA-Server is listening on the Proxy-Address and the listed MA-Gateway is your device that is communicating with it. So configuration wise everything is fine from my point of view and everything should work as expected. The message "data from msg did not match..." is meant for possible future debugging perspective (if MA-Gateways might communicate different), so that we see, that still some response comes back and we can then dig into it deeper.

Flip76 commented 2 years ago

@GreatSUN - thanks for the explaination! I was thinking that it might have an impact on the overall functionality. Will close this issue! Thanks