How a device in mesh of ble controlled by internet.
I tested light on/off of mesh and it works fine.
but how can I control it from internet.
like with wifi or ethernet modules connected with one of the device.
How a device in mesh of ble controlled by internet.
I tested light on/off of mesh and it works fine.
but how can I control it from internet.
like with wifi or ethernet modules connected with one of the device.
I tested light on/off of mesh and it works fine.
So you have the Mesh part working: You know what to do to turn the lights on & off - so all you need is to get your internet stuff to do that!
Yes Mesh is completed.
Want to create a model that took command from uart and send data to corresponding node.
Not sure that's within the scope of the Model ?
It's your application which needs to deal with the UART, recognise your "commands", and feed that into the Mesh
On Models:
https://devzone.nordicsemi.com/f/nordic-q-a/51801/why-there-is-models-in-mesh-communication-nrf52832
If i can't create models likes this, Then I think this BLE Mesh is useless, as today's world wants configurable and manageable system witch can be accessed from anywhere.
In zigbee protocol this thing is very simple to do, take uart data and send to any node.
When I comes to know about BLE mesh, then I think its mostly useful as system can be connected to mobile directly (this is also true I expreiments it and happy with it).
But when its comes to real life application Ble mesh doesn't seems to perform well.
Correct me if I am wrong.
Thank You
You're missing the point!
You don't need to create the model - that is done for you already.
In the Nordic Mesh SDK example, they use the buttons to make the 'On' and 'Off' work.
So all you have to do is to do whatever happens on those buttons - but do it in response to your UART messages instead.
Actually my requirement of model are as follow:
1) A node took data from uart, in uart data there is address of node, whom to send data and data of dimming level.
2) every node should have functionality like this. with address send data to any node.
3) can took status data from any node.
Uart implementation is not issue.
Issue is not to access any node individually. I can access to only a fixed configured node.
OK - none of that was clear from your original post.
As the name suggests, the on'off demo just does 'ON' and 'OFF' - not dimming - so you do need a different model for that.
Have you looked at the other examples to see if there's something closer to your requirements?
In terms of moving on from the examples, see:
OK - none of that was clear from your original post.
As the name suggests, the on'off demo just does 'ON' and 'OFF' - not dimming - so you do need a different model for that.
Have you looked at the other examples to see if there's something closer to your requirements?
In terms of moving on from the examples, see:
Thanks for reply, I see all the models including dimming model they are working as expected.
But the main problem is I can send this value to a fixed configured node.
I need this dimming value to be send to any node, not to a fixed configured node.
In simple, write node ID and dimming value and send it. other node with this ID will receive and set value according to it.
Hi Brevy,
You can change the publication address of a node by using the configuration client (the provisioner).
You can have a look at this video : https://www.youtube.com/watch?v=XthbU9NP0Yg
If you have some thingys you can try the demo yourself on the github link : https://github.com/NordicPlayground/thingy52-mesh-provisioning-demo
But you can do the same with the light switch example.
I know that by configuration client I can change publication address, and using till now.
But every time to change address I have to use mobile. And after some study , I found that we can change the address of publication inside the node by calling address_set() function. But it uses Flash to store data. I want to publish to any node without storing in flash.
Is it possible.
Yes it's possible. But it's not supported out of the box, you would need to modify the code to update the publication address without storing the dsm.
I think the easiest way to do this is that you access the transport layer directly and send the message in raw instead of using the access layer and model. You can have a look at packet_tx() function inside access.c . Inside that function we use nrf_mesh_packet_send() to send the message. You can do the same and modify the tx_params.dst as you wish.