I am trying to run the sleepyMesh scripts on a SYNAPSE RF300 module. Are there some compatibility concerns that I need to be aware of other than the differing pin layouts?
When I load the scripts it functions as intended ONCE and then never again seems to work. I followed the procedure outlined in the Sleepy Mesh application note [doc # 628-0003]. After running initSleepyMesh() on portal my node will report that it is online and sensor is False. After one sleep cycle, it will then report as being offline and in the portal log it will note that portal did not receive a response from the node. The log also gets filled up with nodes are asleep messages and portal is putting nodes to sleep early messages.
I have also populated a sleepyStub.py script with custom code that does only one operation (very simple code) and couldn't get that to work any differently.
There doesn't seem to be a good link between portal and the nodes. Once I start the script, I am not able to pause sleeping using the portal functions. The RPC calls to pause the nodes get queued and sometime sent out of the portal queue but the nodes never stop sleeping. This is a pain because then I can never change the running script on them either.
I am not putting my bridge node to sleep. Only the remote nodes sleep. The bridge node has no script loaded. Portal has sleepyMonitor.py loaded (with correct addresses updated into the polling function).
When I load the scripts it functions as intended ONCE and then never again seems to work. I followed the procedure outlined in the Sleepy Mesh application note [doc # 628-0003]. After running initSleepyMesh() on portal my node will report that it is online and sensor is False. After one sleep cycle, it will then report as being offline and in the portal log it will note that portal did not receive a response from the node. The log also gets filled up with nodes are asleep messages and portal is putting nodes to sleep early messages.
I have also populated a sleepyStub.py script with custom code that does only one operation (very simple code) and couldn't get that to work any differently.
There doesn't seem to be a good link between portal and the nodes. Once I start the script, I am not able to pause sleeping using the portal functions. The RPC calls to pause the nodes get queued and sometime sent out of the portal queue but the nodes never stop sleeping. This is a pain because then I can never change the running script on them either.
I am not putting my bridge node to sleep. Only the remote nodes sleep. The bridge node has no script loaded. Portal has sleepyMonitor.py loaded (with correct addresses updated into the polling function).
Comment