Thank you John. Understood. Initially was testing here just with the set up page and not running the script with the network option.
The devices being tested are WiFi devices updated with Tasmota or Espurna firmware talking MQTT.
Right after booting up or a reboot I could always ping the devices. An hour or two later I could not ping the devices.
Goofing around a bit ssh'd over to the Mosquitto RPi broker device and saw that I could alway ping the WiFi devices.
I moved the Mosquitto broker over to the Homeseer 3 server and that seemed to fix the issue with the ping responses for a short time.
I have been concurrently watching the arp cache. The devices are currently static IP configured. I can change them to using a DHCP assigned IP per mac address and click a check box to alway put the devices in the arp cache.
Changing over to using ARP and moving the Mosquitto broker over to the HS3 server has been working fine and now allowing pings from any box on the network.
pete@ICS-IBMNBK0:~$ ping 192.168.244.221
PING 192.168.244.221 (192.168.244.221) 56(84) bytes of data.
64 bytes from 192.168.244.221: icmp_seq=1 ttl=128 time=3.62 ms
64 bytes from 192.168.244.221: icmp_seq=2 ttl=128 time=5.46 ms
64 bytes from 192.168.244.221: icmp_seq=3 ttl=128 time=1.58 ms
^C
--- 192.168.244.221 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 1.580/3.554/5.464/1.586 ms
pete@ICS-IBMNBK0:~$ arp 192.168.244.221
Address HWtype HWaddress Flags Mask Iface
192.168.244.221 ether 2c:3a:e8:44:ad:c3 C enp0s25
pete@ICS-IBMNBK0:~$
and clicking on the link always takes me to the WiFi updated firmware html interface which wasn't working before.
All is well now monitoring these devices from the Ubuntu 18.04 HS3 box.
MQTT is a bit like using xAP / xPL from way long time ago. The 1-wire stuff is using one WiFi firmware updated device as sort of a hub.
xxx
The devices being tested are WiFi devices updated with Tasmota or Espurna firmware talking MQTT.
Right after booting up or a reboot I could always ping the devices. An hour or two later I could not ping the devices.
Goofing around a bit ssh'd over to the Mosquitto RPi broker device and saw that I could alway ping the WiFi devices.
I moved the Mosquitto broker over to the Homeseer 3 server and that seemed to fix the issue with the ping responses for a short time.
I have been concurrently watching the arp cache. The devices are currently static IP configured. I can change them to using a DHCP assigned IP per mac address and click a check box to alway put the devices in the arp cache.
Changing over to using ARP and moving the Mosquitto broker over to the HS3 server has been working fine and now allowing pings from any box on the network.
pete@ICS-IBMNBK0:~$ ping 192.168.244.221
PING 192.168.244.221 (192.168.244.221) 56(84) bytes of data.
64 bytes from 192.168.244.221: icmp_seq=1 ttl=128 time=3.62 ms
64 bytes from 192.168.244.221: icmp_seq=2 ttl=128 time=5.46 ms
64 bytes from 192.168.244.221: icmp_seq=3 ttl=128 time=1.58 ms
^C
--- 192.168.244.221 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 1.580/3.554/5.464/1.586 ms
pete@ICS-IBMNBK0:~$ arp 192.168.244.221
Address HWtype HWaddress Flags Mask Iface
192.168.244.221 ether 2c:3a:e8:44:ad:c3 C enp0s25
pete@ICS-IBMNBK0:~$
and clicking on the link always takes me to the WiFi updated firmware html interface which wasn't working before.
All is well now monitoring these devices from the Ubuntu 18.04 HS3 box.
MQTT is a bit like using xAP / xPL from way long time ago. The 1-wire stuff is using one WiFi firmware updated device as sort of a hub.
xxx
Comment