HC3 - FGBS222 inputs not working

[RubberDucky 0]

Hello,

 

I'm currently running into a strange problem.

Running HC3 latest stable firmware 5.170.16

 

Besides other devices, I also have 2x Smart Implants on which I'm using the inputs. 

 

SI - ID40 works fine, inputs are very responsive

SI - ID54 inputs do not change

 

Both are connected to the same 24Vdc power supply next to each other.

The inputs are just reed switches pulling IN1/IN2 to GND.

Both running latest firmware v5.2

Both look identical, same security level S2A, Z-wave type 3 and SDK version 6.2, other params are identical.

Both 'Input configuration = Monostable'

 

Steps taken:

Removed and re-added the device, no luck

Replaced the FGBS-222 with a new one, the same behavior.

Swapped the wire connector 40<>54, wiring is OK the SI-ID54 does not detect inputs

 

 

There is one major difference: the working device was added months ago (I do not remember the exact FW version of HC3 at that moment), and the non-working device was added just recently.

It seems that adding Smart Implants is not longer working for me.. Other devices like 'The Button' that I recently added are working straight away.

The non-working SI also pop-up to the HC3 with a different icon set > see attached screenshot.

 

Any ideas anyone?

Please login or register to see this attachment.

Edited December 23, 2024 by RubberDucky

[Whswede 7]

I think I may experience something similar and I have done extensive troubleshooting 
 

Subject: Issue with IN1 not updating value or lastBreached for Smart Implant FGBS-222 on HC3 (v5.171.15)

Description:

I am experiencing an issue with the Smart Implant (FGBS-222) on Fibaro HC3 (firmware v5.171.15). The issue concerns the IN1 input (and also tested on 2), connected to a float switch. While the IN1 input can trigger Button 1 events when Parameter 40 is set to 1, the "value" and "lastBreached" fields for IN1 in the device JSON do not update as expected. These fields remain static, making it impossible to use IN1 as a binary sensor.

---

Detailed Behavior:

1. Expected Behavior:

   • IN1 should act as a binary sensor, updating its "value" field (true or false) and "lastBreached" timestamp whenever the float switch is toggled. These updates should also appear in the Fibaro history tab.

2. Observed Behavior:

   • "value" field for IN1 remains static ("value": false) in the device JSON, even when the float switch is toggled.
   • "lastBreached" field does not update, staying at 0 in the JSON, despite manual toggling of the float switch.
   • Fibaro history tab does not register any changes for IN1.

3. Access Protection Impact:

   • Enabling Access Protection on OUT1 causes IN1 to stop reporting any state changes or triggering Button 1 events. This seems unrelated to OUT1’s protection and limits IN1's functionality further.

---

Tests Conducted:

1. Parameter 40 (Scene Activation):

   • Setting Parameter 40 to 1 allows IN1 to successfully trigger Button 1 events when the float switch changes state.
   • However, IN1’s "value" and "lastBreached" fields remain unchanged, making it unusable as a binary sensor.

2. Parameter 47 and 49 (Association values):

   • Adjusting these parameters did not influence the behavior of IN1 or resolve the lack of updates in the "value" or "lastBreached" fields.

3. Access Protection Behavior:

   • Enabling Access Protection on OUT1 causes IN1 to stop functioning entirely. This behavior is unexpected, as protection should only limit local control of OUT1.

---

Objective:

The goal is to use IN1 as a binary sensor, where:

• The "value" field reliably updates based on the float switch state.
• The "lastBreached" timestamp reflects the last time IN1 was triggered.
• These changes are visible in the Fibaro history tab and accessible for automation.

---

Environment Details:

• HC3 Firmware Version: v5.171.15
• Device Model: Smart Implant (FGBS-222), Firmware v5.2
• Use Case: Monitoring a float switch connected to IN1 and using its state changes for automation.

---

Steps to Reproduce:

1. Connect a float switch to IN1 of the Smart Implant.
2. Toggle the float switch manually (open/close).
3. Monitor the device JSON (/devices/<id> endpoint) or the Fibaro history tab for updates to the "value" or "lastBreached" fields for IN1.

---

Request:

Could you please clarify:

1. Why does IN1 fail to update its "value" and "lastBreached" fields in binary sensor mode?
2. Are there specific configuration steps or parameter adjustments required to enable these updates?
3. Why does enabling Access Protection on OUT1 disrupt the functionality of IN1?

If additional information or logs are required, I am happy to provide them.

Thank you for your support.

[RubberDucky 0]

On 1/7/2025 at 9:09 PM, Whswede said:

[..]

Tests Conducted:

1. Parameter 40 (Scene Activation):

   • Setting Parameter 40 to 1 allows IN1 to successfully trigger Button 1 events when the float switch changes state.
   • However, IN1’s "value" and "lastBreached" fields remain unchanged, making it unusable as a binary sensor.

2. Parameter 47 and 49 (Association values):

   • Adjusting these parameters did not influence the behavior of IN1 or resolve the lack of updates in the "value" or "lastBreached" fields.

3. Access Protection Behavior:

   • Enabling Access Protection on OUT1 causes IN1 to stop functioning entirely. This behavior is unexpected, as protection should only limit local control of OUT1.

[..]

 

Setting parameters 40/41 (input1/2) did the trick for my application! I would think that if you create a scene from the 'remote control' device of the SI that at least the necessary parameters were checked..

 

Thank you for the great response!

Edited January 9, 2025 by RubberDucky

[Whswede 7]

9 hours ago, RubberDucky said:

 

Setting parameters 40/41 (input1/2) did the trick for my application! I would think that if you create a scene from the 'remote control' device of the SI that at least the necessary parameters were checked..

 

Thank you for the great response!

This is a work around but main issue persist as using IN1 and/or IN2 as binary sensors reporting "breached" is not possible. Scene activation (param 40/41) is my work around too for now but not my intended way when getting a few Smart Implants for various tasks. I have sent this as a support ticket to Fibaro also and will report back here if the provide any answers. 

[Martin_N 154]

@Whswede @RubberDucky

Hi.

I once found that he sometimes "behaves strange" and does not respect the setting if one plays with him.

Check out this train. Try to imitate this settings and please let it know if it helped.

At that time it was an old FW HC3, I think some 5.040.