-
Notifications
You must be signed in to change notification settings - Fork 18
6 Issues and Error Processing
David Gutheinz edited this page Mar 2, 2020
·
2 revisions
- Static IP Not Set. Failure to set static ip addresses can cause the device to fail because it is unreachable. Device driver corrective action described in communications failure below.
- HS300 devices. A persistant communications failure is usually caused by the return message from the device exceeding the Hubitat limit. Corrective action: Shorten the name of the devices (the strip and each individual plug) to reduce the message size.
The Driver and Application are designed to automatically correct two communications errors:
- A multi-plug is busy completing a command to another plug and the sent command is ignored.
- The device's static IP has changed due to a reboot of the user's router and the use not setting the Static IP for the device.
The following has been implemented:
- When the communications do not complete, a retry is completed and if successful, the device continues normally. This usually handles the multi-plug issue.
- The above is repeated a second time if it does not work.
- If the second try fails, the application will attempt to poll the device IP addresses to update a changed address.
- The program checks to see if a poll has been run within the last hour. If not"
- The program polls for all devices and as the devices are encountered, child device IP addresses are automatically updated.
- A forth try is completed. If that fails, no more tries are completed.
- Subsequent command will NOT undergo automatic error processing.
- If a command is successful, then the error processing is reset.
- If the automatic correction does not fix the problem, the user will have to troubleshoot why the device is not present. Running the application and listing or installing the devices will update the device IP after the problem is resolved.