I am currently playing around with a couple of 5753PEIRL's relating to their broadcasting of light levels to the network. Changing the event levels on a telnet session show that with events set to e0s0c1 (i.e. to only show config change events) the 5753PEIRL is very "chatty" Pretty much every second it issues a sync followed by an OK command as below: #c# //JYOUNG/253/p/217 #State=sync #OID=dcb0df40-a227-1038-991f-d086c011aa3c #c# //JYOUNG/253/p/217 #State=ok #OID=dcb0df40-a227-1038-991f-d086c011aa3c #c# //JYOUNG/253/p/217 #State=sync #OID=dcb0df40-a227-1038-991f-d086c011aa3c #c# //JYOUNG/253/p/217 #State=ok #OID=dcb0df40-a227-1038-991f-d086c011aa3c The device is set to broadcast its light level every 30 seconds via a lighting GA which gives the lux value divided by 10 as the value. (I will write a homebridge-cbus Light Level Sensor with this information) If I crank events to e9s0c0 I get the following (plus or minus a couple of lines): #e# 20200708-171038 734 //JYOUNG/253 42f217f0-998c-1038-9589-d086c011aa3c response: 86FD0401D98816513A00FF4604012C accepted by command: \46D9002116k #e# 20200708-171038 766 cmd79 - Response: [136447] 202 Done: //JYOUNG/253/p/217 #e# 20200708-171038 761 cmd79 - Command: &4[136448] get 253/p/217 LightLevel #e# 20200708-171038 766 cmd79 - Response: [136448] 300 //JYOUNG/253/p/217: LightLevel=320 #e# 20200708-171038 761 cmd29 - Command: &4[906887] noop #e# 20200708-171038 761 cmd29 - Command: &4[906888] noop #e# 20200708-171038 766 cmd29 - Response: [906887] 200 OK. #e# 20200708-171038 766 cmd29 - Response: [906888] 200 OK. #e# 20200708-171038 761 cmd79 - Command: &4[136449] do 253/p/217 psync This seems a lot of traffic. Can these devices be set to broadcast at a longer interval like the "Measurement Application" devices e.g. Temperature sensors (say around 30 seconds) In the Toolkit Config for the 5753PEIRL there is a "Status report" option in the "Global" tab which is set to 3 seconds. Setting this to 30 seconds didn't help. Telling it to be a little "quieter" and stop talking so much would be nice. Cheers and thanks for any ideas Jason
On the light level tab, under light level broadcasting, click on the 3 dots to the right of the block and set whatever value you want.
Thanks Ashley. I had set this to 30 seconds (to be the same as my temperature/current sensors as per the measurement application). The Lighting GA defined in the block then sets itself to 1/10th of the Raw Lux level (from the sensor) and adjusts & broadcasts its level as its supposed to every 30 seconds. Toolkit Log Snippet: DateTime= 8/07/2020 16:30:27.061 App= 056 Lighting Group= 250 LightLevelTest Unit= 217 SENPILL/NEWUNIT Event= Group ramped to 032 ( 13%) over 0 seconds DateTime= 8/07/2020 16:30:57.126 App= 056 Lighting Group= 250 LightLevelTest Unit= 217 SENPILL/NEWUNIT Event= Group ramped to 032 ( 13%) over 0 seconds It's the "sync" broadcast as per the above Config & Event logs every second (approximately) that I am scratching my head over... I appreciate your advice and happy to double check every and any option. The network seems happy and I wouldn't know that the messages were there unless I was looking for them. The questions is, is it happening by design and is it "settable" Thanks again Jason
I looked at the c-bus diagnostic utility. Everything seems kosher. I had to span my network bridge but the traffic analyser and reliability test seemed ok. Quite a lot of CAL messages. Traffic between the CNI and bridge as expected, about 10 messages per second with no errors and from the reliability testing all “perfect” and “good” summaries for the units. So maybe I’m reading into it too much. It just seems strange that this little device is pumping out so many sync messages with the logging level of events set at at “events e0s0c1”. I will run up another one of them with the same config and see what I get. Thanks again Jason
Well, after some playing, it seems that the numerous config change events from the 5753PEIRL are the result of having the "Refresh" check box selected under the "Light Level / Ambient Light / Last Measurement" section in Toolkit. I thought that this may be due to the "Global / Timing Parameters / Status Report" setting option, but changing this from the default level of 3 sec did not make any difference to the message frequency. So problem solved. Interestingly, this is not constant between units. One 5753PEIRL send these messages more than once per second, another one about every three seconds. Thanks for your input Ashley. Cheers Jason
