| Recurring |
unknown |
The article does not provide information about the software failure incident happening again at the same organization or with its products and services (a). Additionally, there is no mention of the software failure incident occurring at multiple organizations or with their products and services (b). Therefore, the information to answer this question is 'unknown'. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase is evident in the article. The Soliom Video Doorbell faced issues with its app, particularly in the latest software version. The reviewer mentioned that every time they tried to enable motion detection, the app changed the setting back to "disabled." Additionally, when toggling between the microSD card option and cloud storage, the app randomly switched back to cloud storage. These issues point towards failures introduced during the system development or updates, affecting the functionality of the product [Article 76563].
(b) The software failure incident related to the operation phase is also highlighted in the article. The reviewer faced difficulties in getting the settings to work correctly on the Soliom Video Doorbell app. For instance, when selecting "enabled" on the motion sensor option, the app reverted to "disabled" multiple times. Despite enabling notifications and cloud motion events, the camera did not successfully send notifications or record events. These operational issues indicate failures introduced during the operation or misuse of the system, impacting its functionality and user experience [Article 76563]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the Soliom Video Doorbell is within the system. The article mentions that the app, in its latest software version, is very glitchy. Users experienced issues such as the app changing settings back to "disabled" when trying to enable motion detection, and difficulties with the microSD card option toggling back to cloud storage randomly. These issues indicate that the failure is primarily due to problems originating from within the software system itself [Article 76563]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the Soliom Video Doorbell was primarily due to non-human actions, specifically related to glitches in the app and issues with settings toggling back and forth without human intervention. The article mentions that the app, in its latest software version, was very glitchy, with settings like motion detection toggling back to "disabled" on their own. Additionally, the PIR motion detection randomly switched between "enabled" and "disabled" without human input [Article 76563]. These issues indicate that the failure was primarily caused by software glitches rather than human actions. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident occurring due to hardware:
- The Soliom Video Doorbell experienced software glitches such as the app changing settings back to "disabled" when trying to enable motion detection, and toggling between microSD card and cloud storage options randomly, indicating issues that could be related to hardware components like sensors or memory storage [Article 76563].
(b) The software failure incident occurring due to software:
- The Soliom Video Doorbell faced software glitches in its app, with difficulties in getting settings to work correctly, such as the motion sensor option reverting to "disabled" and the camera not sending notifications or recording cloud motion events despite being enabled, suggesting software-related issues [Article 76563]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The articles do not mention any malicious intent or actions related to the software failure incident. [76563]
(b) The software failure incident described in the articles is categorized as non-malicious. The failure is attributed to glitches in the app, specifically related to enabling motion detection and selecting storage options, which caused the product to not function as intended. The reviewer highlighted issues with the app settings not working correctly, such as the app randomly toggling between microSD card and cloud storage options, and the motion sensor option switching between "enabled" and "disabled" multiple times without successful notifications or recordings. The overall assessment is that the Soliom Video Doorbell is not ready for real-world use due to these software-related issues. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident related to the Soliom Video Doorbell can be attributed to poor decisions. The article mentions that the app in its latest software version is very glitchy, with issues such as the app changing settings back to "disabled" when trying to enable motion detection, and difficulties in getting the settings to work correctly even after inserting a microSD card. The reviewer also highlights that the doorbell feels like it's still in beta mode, doesn't work with any smart home partners, and has various usability issues, indicating poor decisions in the development and release of the product [Article 76563]. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident in the Soliom Video Doorbell is related to development incompetence. The article mentions that the app in its latest software version is very glitchy, with settings not working correctly despite multiple attempts to enable them. For example, toggling between microSD card and cloud storage options, as well as enabling the motion sensor, resulted in the app reverting back to disabled settings multiple times [Article 76563]. This indicates a lack of professional competence in the development of the software, leading to these glitches and malfunctions. |
| Duration |
temporary |
The software failure incident related to the Soliom Video Doorbell mentioned in Article 76563 seems to be temporary rather than permanent. The article highlights various glitches and issues with the app, such as the app changing settings back to disabled, difficulty in getting settings to work correctly, motion detection toggling between enabled and disabled, and the camera not successfully sending notifications or recording cloud motion events despite being enabled. The reviewer mentions that the doorbell feels like it's still in beta mode and expresses hope that some of the glitches will be worked out in the coming months, indicating that the issues are not permanent but may be resolved with future updates or improvements. |
| Behaviour |
other |
(a) crash: The software failure incident described in the article is not specifically related to a crash where the system loses state and does not perform any of its intended functions. The issue mentioned is more about the app being glitchy and not functioning correctly, rather than a complete system crash [Article 76563].
(b) omission: The software failure incident does not directly relate to the system omitting to perform its intended functions at an instance(s). Instead, the focus is on the app's glitchy behavior, such as not being able to enable motion detection or settings reverting back to disabled [Article 76563].
(c) timing: The software failure incident is not about the system performing its intended functions too late or too early. The main issue highlighted is the app's erratic behavior and difficulty in getting settings to work correctly, rather than a timing-related failure [Article 76563].
(d) value: The software failure incident does not involve the system performing its intended functions incorrectly in terms of providing incorrect outputs or results. The primary concern is the app's glitchy behavior and the difficulty in getting settings to work as expected [Article 76563].
(e) byzantine: The software failure incident does not exhibit the system behaving erroneously with inconsistent responses and interactions, as described in a byzantine failure. The main issue is the app's glitchy behavior and the challenges in getting settings to function correctly [Article 76563].
(f) other: The behavior of the software failure incident in this case can be categorized as a glitchy performance of the app, where settings do not work as expected, motion detection toggles back to disabled, and the camera fails to send notifications or record cloud motion events despite being enabled. The system is described as not being ready for real-world use due to these issues [Article 76563]. |