Jump to content

0.9.70 available


Panda88

Recommended Posts

A new version is available

YoLink started to limit number of calls from nodeserver to their servers to 20 / min and 6 per device / min.   If you have many devices a Poll will violate this and some pof the devices may be temporary offline.  Changed poll to spread the query in time (4 seconds between each device).  Also updated Poll to every 5 min (300s) - Poll should not be needed ideally as all changes are reported by YoLink, but in case a packet is missed ithe state will be updated during Poll.   Note, if you have 75 or more devices (4 sec * 75 = 300s ) you should update shortPoll accordingly 

  • Like 3
Link to comment

It is YoLink making this limit - I think it does not need to cause issues - It is control or status update calls.  You do not need to keep querying the devices - they announce changes (which is not counted as a call) - so it is only if you change/control you devices often or you do a query update (should really be needed but there is always a chance to missing a packet being sent from device).

I am working to limit the calls automatically, but not as easy if you have multiple houses on different polisys (It is my case).    

  • Like 2
Link to comment
3 minutes ago, Panda88 said:

It is YoLink making this limit - I think it does not need to cause issues - It is control or status update calls.  You do not need to keep querying the devices - they announce changes (which is not counted as a call) - so it is only if you change/control you devices often or you do a query update (should really be needed but there is always a chance to missing a packet being sent from device).

I am working to limit the calls automatically, but not as easy if you have multiple houses on different polisys (It is my case).    

So if I am turning on a relay or announcing a message over the Speaker Hub, that counts. To play a message on the Speaker Hub I have a program that selects the message, waits 2 seconds and then plays message. Thats 2 calls, is there a better way?

Link to comment
1 minute ago, Panda88 said:

Correct

Selecting the message may be happening local (I believe so but I am not 100% sure) - if local it does not count - I think they play includes the selected message in one operation / call

I the program for Play you only get this

image.png.dfbe4e5573ab4b57b5be55ef54f1b491.png

 

That is why I am having to select the message, wait, then play:
image.png.b4aa043625404cc9ce1547f762851294.png

 

But if the select message is local, then it doesn't matter from a call count, other than the delay being there. Overall the Node seems to operate very well. Nice work!

Link to comment
31 minutes ago, Panda88 said:

Should be local - Any special reason for the delay?

Didn't seem to work without a delay in between the select and play, like the EISY/IoX sends the commands so fast the Speaker Hub doesn't select the message in time. But after reading the throttling YoLink is doing, it could have been that. I just took the wait out and it seems to be working ok now. 

Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...