Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MeshMessages like GenericOnOffSet should not have to pass a node.
See original GitHub issueWhy do we want to pass the node when generating new messages like GenericOnOffSet(NODE,...,destinationAddress). When sending to groups we do not have a single node we can put there. Can we just remove this from all model messages, or why is it necessary?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Bluetooth Mesh Glossary of Terms
All Nodes have the ability to transmit and receive mesh Messages. ... the same semantics as the Generic OnOff Set Message except that...
Read more >Shell - Zephyr Project Documentation
The mesh node must be provisioned to become part of the network. ... Next, since the device has no application keys by default,...
Read more >Bluetooth Mesh Models
Models can have specified dependencies on other models. ... Models that do not extend other models are known as root models.
Read more >RX23W Group Bluetooth Mesh Stack - Renesas
A device joining a network is referred to as a Node. ... devices that does not have Network Key cannot trace them. ......
Read more >E104-BT12LSP User Manual
module (all copper laid and well grounded), we must go near the ... Low Power Node: Low power nodes that do not have...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@DomiR you have a very good point. The only reason is or rather was, almost everything was stored in the node object so I had to pass around the node object. However now after separating the mesh network properties and node properties don’t think we need to pass it around anymore. Currently I’m finishing up config relay set and I will look in to this and clean that up as well.
@DomiR Basically made a MINOR mess out of it 😉 I believe this should solve your issue 😃