Closed chinfu closed 1 month ago
Dear @chinfu , we did test out the SmokeCOAlarm cluster, have added some of the functions in the following links
You will need the sTestEventTriggerEnableKey to be set to support this cluster. However, these implementation has not been added into the porting layer. You can give it a try, and do let me know if there is any problem.
And regarding the bridge issue in #104 , for now you can remove the Bridged Node device type and work with it. Once I have figured out the issue, I will update you!
Thank you
Dear @xshuqun , It is great to hear that. I'll try it.... Thank you.
BR, Vic
Dear @xshuqun , I am curious about the behavior of the SmokeCOAlarm device on the GoogleHomeApp. Do you have any experience on this ?
For trying SmokeCOAlarm:
Thank you ! BR, VIc
@chinfu I have never tried on this before. As this device is not officially supported by Google yet, i doubt that the functions are all working well. If this is urgent on your side, maybe you could approach Google Help Desk to ask for details?
Dear @xshuqun , Rogee that. I had tried to file this as an issue to Google. Thanks .
Br, Vic
Dear @xshuqun,
I was hoping you could assist with a few quick questions:
Using the bridge_dm example, how many bridged devices can be attached to this bridge? From my testing, it seems I can only attach around 11 devices.
Regarding the Google Home App (GHA), is there a method or path for the bridge to set or read the name and location of each bridged device within the GHA? Specifically, if a user changes a device's name or location in the GHA, is there a way for our private app/tool to sync with these updates?
Thank you!
BR, Vic
Dear, I am trying to hooking a non-matter/battery-powered SmokeCOAlarm device to the bridge_dm example. First, is there any reference for the normal "SmokeCOAlarm" device ?
Thank you !
BR, Vic