Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't get dimmable light to work #41

Open
tribbles3 opened this issue Jan 24, 2025 · 34 comments
Open

can't get dimmable light to work #41

tribbles3 opened this issue Jan 24, 2025 · 34 comments

Comments

@tribbles3
Copy link

Trying to get the dimmable light node to work with a flic twist "button". The flic twist sees the dimmable light as a matter device and I am able to select it but I'm not receiving anything when I dimming with the flic twist. I was able to setup on-off light and on-off socket nodes with the flic twist and they are functioning without issue. The flic twist supports dimmable lights via matter as it finds the device properly.

@tribbles3 tribbles3 changed the title can't dimmable light to work can't get dimmable light to work Jan 24, 2025
@sammachin
Copy link
Owner

@tribbles3 Thats strange I've just tested with a flic twist here and some dimmable light nodes, all seems to work fine, which version of the bridge are you running? There were some fixes to the dimmable light in the latest releases

@tribbles3
Copy link
Author

0.12.0

What is the firmware version of your flic hub (I'm running 4.3.8)?

@sammachin
Copy link
Owner

Yep 4.3.8 here,

Does dimming work from another matter controller like apple home or google home (if you have)

@tribbles3
Copy link
Author

I have an Apple TV but it is on a different network at the moment so I would have to change that to test it.

@tribbles3
Copy link
Author

tribbles3 commented Jan 24, 2025

I was able to connect the device to Apple Home (iPhone app) but I am unable to control it and it shows "No Response" under the item name (in the iPhone app).

@sammachin
Copy link
Owner

can you share the node config, ideally export it please as well as a screenshot

@sammachin
Copy link
Owner

Just tested with my dev setup so definitly 0.12 of the bridge and 4.3.8 on the Hub with the Flic Twist, works fine.
Also checked the dimmable light with Apple home just in case and again that works fine.

I think given that you are also having issues with Apple Home it mist be something in your Matter Bridge setup.

@tribbles3
Copy link
Author

Are you referring to this config?
Image

@sammachin
Copy link
Owner

sammachin commented Jan 24, 2025 via email

@tribbles3
Copy link
Author

tribbles3 commented Jan 24, 2025

I should also mentioned that I am running node-red 4.0.3

Image

@sammachin
Copy link
Owner

Hmm shouldn’t make a difference but set battery to none and pass through to true or false rather than not set.

If that doesn’t work then set the debug level on the bridge node to debug, restart node red and send me the console output

@tribbles3
Copy link
Author

"Hmm shouldn’t make a difference but set battery to none and pass through to true or false rather than not set."

Did that and now the dimmable light can be turned on and off but still not receiving anything when I change the brightness.

@sammachin
Copy link
Owner

sammachin commented Jan 24, 2025 via email

@tribbles3
Copy link
Author

Something squirrely is going for sure because I just lost the ability to control the On-Off Light

@sammachin
Copy link
Owner

How are you running node red? Is it in docker or something? It sounds like your fabric data isn’t persisting across restarts, it should be in ~/.matter by default

@tribbles3
Copy link
Author

tribbles3 commented Jan 24, 2025

Running node-red in docker. The matter directory location is ~/.matter

@sammachin
Copy link
Owner

Ah right, is your /root folder persisted between restarts of the container! The standard node red image only persists /data so you’d need to set that as the storage location in the bridge config. And then you’ll need to recommission the bridge to flic and apple home

@tribbles3
Copy link
Author

changed the changed it to /data/.matter and I can't get any matter nodes to work. The bridge is recognized and the device connects in the flic app but no data is passed to node-red. If I turn on the debug for the bridge, where/how can I see the debug info? I can get to the cli in the docker container but not sure how to see the node-red console.

@sammachin
Copy link
Owner

you should be able to use docker attach [CONTAINER NAME] to connect to the console, that won't show history but will show what happens from there on.

@sammachin
Copy link
Owner

also if you change the storage path you will need to recommission the bridge in the controllers

@tribbles3
Copy link
Author

tribbles3 commented Jan 25, 2025

2025-01-25 10:44:20.013 DEBUG InteractionServer Received invoke request from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995 with 1 commands: OnOffLight(0x2)/unknown(0x8)/0x4, suppressResponse=false

2025-01-25 10:44:20.014 DEBUG InteractionServer Invoke from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995: OnOffLight(0x2)/unknown(0x8)/0x4 unsupported path: Status=195

2025-01-25 10:44:20.016 DEBUG ExchangeManager Message » id: 46995/19427/77046349 type: 1/9 acked: 179221263 reqAck: true duplicate: false payload: 152800360115350137002400022401082402041835012400c31818181824ff0c18

This is what shows up in the node-red console when I send an "On" command from the flic twist to the On-Off Light node. The node does not generate an output.

@tribbles3
Copy link
Author

tribbles3 commented Jan 25, 2025

2025-01-25 10:54:43.611 DEBUG MessageExchange New exchange channel: udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995 protocol: 1 id: 19428 session: secure/46995 peerSessionId: 46995 active threshold ms: 4000 active interval ms: 300 idle interval ms: 300 maxTransmissions: 5 useMrp: true

2025-01-25 10:54:43.612 DEBUG MessageExchange Message « id: 46995/19428/179221276 type: 1/8 acked: undefined reqAck: true duplicate: false payload: 15280028013602153700240002250100032402061835012400002401cb24020024030124040118181824ff0b18

2025-01-25 10:54:43.615 DEBUG InteractionServer Received invoke request from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995 with 1 commands: OnOffLight(0x2)/unknown(0x300)/0x6, suppressResponse=false

2025-01-25 10:54:43.616 DEBUG InteractionServer Invoke from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995: OnOffLight(0x2)/unknown(0x300)/0x6 unsupported path: Status=195

2025-01-25 10:54:43.618 DEBUG ExchangeManager Message » id: 46995/19428/77046360 type: 1/9 acked: 179221276 reqAck: true duplicate: false payload: 15280036011535013700240002250100032402061835012400c31818181824ff0c18

2025-01-25 10:54:43.628 DEBUG MessageExchange New exchange channel: udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995 protocol: 1 id: 19429 session: secure/46995 peerSessionId: 46995 active threshold ms: 4000 active interval ms: 300 idle interval ms: 300 maxTransmissions: 5 useMrp: true

2025-01-25 10:54:43.630 DEBUG MessageExchange Message « id: 46995/19429/179221277 type: 1/8 acked: undefined reqAck: true duplicate: false payload: 152800280136021537002400022401082402041835012400e4340124020124030118181824ff0b18

2025-01-25 10:54:43.641 DEBUG InteractionServer Received invoke request from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995 with 1 commands: OnOffLight(0x2)/unknown(0x8)/0x4, suppressResponse=false

2025-01-25 10:54:43.642 DEBUG InteractionServer Invoke from udp://fe80::9b06:e5e6:8a8f:1110%enp0s3:40685 on session secure/46995: OnOffLight(0x2)/unknown(0x8)/0x4 unsupported path: Status=195

2025-01-25 10:54:43.644 DEBUG ExchangeManager Message » id: 46995/19429/77046361 type: 1/9 acked: 179221277 reqAck: true duplicate: false payload: 152800360115350137002400022401082402041835012400c31818181824ff0c18

2025-01-25 10:54:43.649 DEBUG MessageExchange Message « id: 46995/19428/179221278 type: 0/16 acked: 77046360 reqAck: false duplicate: false payload:

2025-01-25 10:54:43.651 DEBUG MessageExchange Message « id: 46995/19429/179221279 type: 0/16 acked: 77046361 reqAck: false duplicate: false payload:

I think I missed some lines in the previous post, this is everything that comes up when the command is sent.

@Apollon77
Copy link

Cluster 0x8 is Level control ... so seems the devcie is not correctly setup as a Dimmed Light

@tribbles3
Copy link
Author

Nothing is working at this point so I decided to just test the On-Off Light node (mentioned 3 posts up) as that one was working originally.

@sammachin
Copy link
Owner

@tribbles3 i’m fairly sure your issues are all relating to persistent file storage.

Can you try removing all configuration from node red and from the controller apps then starting over fresh. You need to ensure that the bridge node has a storage path configured that will persist across container restarts,

@tribbles3
Copy link
Author

I will give it a try.

@tribbles3
Copy link
Author

tribbles3 commented Jan 26, 2025

I have the matter setup in a persistent location. and I am now able to consistently use the on/off function with the On-Off Light node and the Dimmable Light node. The dimming function is still not working but it appears that the flic twist is not even attempting to communicate with the dimmable light node when I operate the twist for adjusting the brightness. It lets me select the proper device in the setup but nothing is showing up in the node-red console with the config in debug mode. The on/off commands show up but nothing else.

@sammachin
Copy link
Owner

does it work with a regular twist not a push & twist?

@tribbles3
Copy link
Author

Yes, I tested it using both. I am going to try it with Apple homekit.

@tribbles3
Copy link
Author

Apple recognizes it as a dimmable light but shows "No Response" when I try to use the device.

@sammachin
Copy link
Owner

sammachin commented Jan 27, 2025 via email

@tribbles3
Copy link
Author

tribbles3 commented Jan 27, 2025

[{"id":"222e53ee678f3dc1","type":"matteronoffsocket","z":"b2fd778c2cf643d9","name":"socket","bridge":"b1f70fc222305d24","passthrough":"false","bat":"false","topic":"","x":450,"y":1300,"wires":[["8a064ddea161bde1"]]},{"id":"8a064ddea161bde1","type":"debug","z":"b2fd778c2cf643d9","name":"debug 12","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":620,"y":1400,"wires":[]},{"id":"a5935ffa0343b426","type":"matteronofflight","z":"b2fd778c2cf643d9","name":"light","bridge":"b1f70fc222305d24","passthrough":"false","bat":"false","topic":"","x":450,"y":1360,"wires":[["8a064ddea161bde1"]]},{"id":"9ec8a6b001562149","type":"matterdimmablelight","z":"b2fd778c2cf643d9","name":"dlight","bridge":"b1f70fc222305d24","range":"254","passthrough":"false","levelstep":1,"bat":"false","topic":"","x":450,"y":1420,"wires":[["8a064ddea161bde1"]]},{"id":"b07a083bbbe11e55","type":"matterdimmablelight","z":"b2fd778c2cf643d9","name":"dimmablel","bridge":"37ba894834eb7c97","range":"254","passthrough":"false","levelstep":1,"bat":"false","topic":"","x":430,"y":1480,"wires":[["8a064ddea161bde1"]]},{"id":"b1f70fc222305d24","type":"matterbridge","name":"nr","vendorId":"0xFFF1","productId":"0x8000","vendorName":"Node-RED-Matter","productName":"Node-RED-Bridge","storageLocation":"/config/matter","networkInterface":"enp0s3","logLevel":"DEBUG"},{"id":"37ba894834eb7c97","type":"matterbridge","name":"noder","vendorId":"0xFFF1","productId":"0x8000","vendorName":"Node-RED-Matter","productName":"Node-RED-Bridge","storageLocation":"/config/matter","networkInterface":"enp0s3","logLevel":"ERROR"}]

I have two different bridges setup, one connected to the flic hub and the other to apple. The "socket" and "light" nodes work with flic doing on/off but the "dlite" node doesn't receive anything from flic when attempting to do dimming (using the debug bridge setting and looking at the node-red console). The "dimmablel" node is recognized by apple as a dimmable light but shows "No Response" on the apple side.

@sammachin
Copy link
Owner

Having 2 bridge nodes configured will likely cause issues unelss you disable one of them while using the other.
You can connect a bridge to more than one controller at a time though so you should only really ever need one.

@tribbles3
Copy link
Author

tribbles3 commented Jan 27, 2025

I only added the second bridge to do the apple test as I didn't see a way to generate a QR code for the apple connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants