Using UltraMon3 on my network. Everything works well with one exception. I have a Foscam IP Camera (1 of 4) that is returning an offline status. I can ping the IP fine using command prompt, and the camera is working properly. The last ping result inside UltraMon says "TimedOut". Any ideas?
Announcement
Collapse
No announcement yet.
Status Offline - Incorrect
Collapse
X
-
Originally posted by bearben25 View PostUsing UltraMon3 on my network. Everything works well with one exception. I have a Foscam IP Camera (1 of 4) that is returning an offline status. I can ping the IP fine using command prompt, and the camera is working properly. The last ping result inside UltraMon says "TimedOut". Any ideas?
I have just enabled logging to Informational & will report any messages when it next happens.
Any ideas?
Cheers
Scott
-
Originally posted by bearben25 View PostUsing UltraMon3 on my network. Everything works well with one exception. I have a Foscam IP Camera (1 of 4) that is returning an offline status. I can ping the IP fine using command prompt, and the camera is working properly. The last ping result inside UltraMon says "TimedOut". Any ideas?Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR
Comment
-
Originally posted by ScottRennie View PostI'm getting something similar - difference is that the entry in HSPI completely dissapears and the IP entry is shown as unknown. The device still exists, but the value doesn't change so always shows the value at the time the device falls out of HSPI, so any events based on a change of value fail to trigger. The HSPI tab in the device is blank when the problem exists.
I have just enabled logging to Informational & will report any messages when it next happens.
Any ideas?
Cheers
ScottPlug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR
Comment
-
Originally posted by Ultrajones View PostHave you tried to delete and recreate the HS3 device?
It's been fine for about two or three days now, so looks like a odd glitch.
Cheers
Scott
Comment
Comment