I have two LANs A and B connected using Mikrotik. Communication is routed fine in both directions A->B and B->A. HA is in LAN A shelly is in LAN B. I set unicast communication on shelly and set IP to HA instance on A LAN.
When i turn on Shelly using for example mobile app state is propagated into HA immediately = unicast messaging works fine. But i cannot turn on/off shelly using HA. And i know why. In entity details on lovelace frontend i see:
Protocols CoAP-msg, IP-addr, poll
IP address - and here is NOT ip of shelly but IP of Mikrotik router.
At this point you may admit problem is on my LAN setting, maybe on Mikrotik's routing. BUT - when i go to HA integrations, Shelly, point to this shelly, look at "visit device" link there is right IP address from LAN B. So HA knows right IP some way.
Steps to Reproduce
Expected behavior
HA use right IP to communicate with shelly entity.
Screenshots
Traceback/Error logs
Additional context
My shelly is discovered using this part of config:
discover_by_ip:
- '<shelly-ip-on-LAN-B>'
I think someone from dev team should explain, why there are two different IPs on one shelly at two different places in HA.
Environment
Describe the bug
I have two LANs A and B connected using Mikrotik. Communication is routed fine in both directions A->B and B->A. HA is in LAN A shelly is in LAN B. I set unicast communication on shelly and set IP to HA instance on A LAN.
When i turn on Shelly using for example mobile app state is propagated into HA immediately = unicast messaging works fine. But i cannot turn on/off shelly using HA. And i know why. In entity details on lovelace frontend i see:
Protocols CoAP-msg, IP-addr, poll
IP address - and here is NOT ip of shelly but IP of Mikrotik router.
At this point you may admit problem is on my LAN setting, maybe on Mikrotik's routing. BUT - when i go to HA integrations, Shelly, point to this shelly, look at "visit device" link there is right IP address from LAN B. So HA knows right IP some way.
Steps to Reproduce
Expected behavior
HA use right IP to communicate with shelly entity.
Screenshots
Traceback/Error logs
Additional context
My shelly is discovered using this part of config:
I think someone from dev team should explain, why there are two different IPs on one shelly at two different places in HA.