On Aug 7, 2024, at 6:44?PM, Brian Matson via groups.io <bmatson@...> wrote:

?

Chris,

?

I feel your pain!

It seems like a daily/weekly reboot is becoming more necessary instead of just being a temporary band-aid.

?

It's a sad day when you're threatening to buy a Windows based processor.

You'd hope that moving to the 4-series platform would have made everything better, faster, etc.

However, like every new ridiculously more powerful generation of mobile processors, nothing is ever really faster because of the added bloat.

?

I would just like Crestron to institute a simple "insecure" mode that strips everything away for those of us that understand the implications and have everything sitting behind a proper firewall implementation.

Most of our clients use a VPN tunnel to their homes anyways.

Leave the super security to the commercial and government projects.

?

I know you have your list of "crap" that automatically gets disabled with every processor roll-out.

?

I'm testing the waters with the VC series, and I wonder if they are having the same issues as Crestron branded hardware.

I don't have any long-term data yet ... anyone else?

?

Good luck,

Brian

On Aug 6, 2024, at 5:46?PM, Nicolas Hallynck via groups.io <nicolas.hallynck@...> wrote:

?

Personally, I use a Dahua intercom. I find them to be very good for a reasonable price. They have a better camera image quality than Doorbird.

I also really like the fact that they provide an SDK, so I can completely integrate it into my app and answer directly on it.

I use this model: VTO2201 F-P-S2.

?

Nico, Thorsten,

Based on Nico's writeup of the problem I have created a new version of the Sensibo Air Module for testing (v1.6).? The issue is this.? When you send a command to the Sensibo API based on a user selection the API doesn't respond back with information that tells you it has been accepted and implemented.? So, to keep the outputs of the module in synch with user selections I had sent a refresh command right afterwards.?

This doubles the number of calls and if, for example, multiple commands are sent in quick progression based on a? user favorite setting, then this can cause a lot of commands to be sent in quick sucession which could easily run afoul of the API police trying to manage API traffic.

I've added a new parameter named Manual_Refresh_Required.? When this is set to true a refresh command will not be sent after each other command.? Instead the code will have to manage when to refresh the outputs of the module manually.

I also included some additional notes on how to implement the user's ability to change the target temperature.? If, for example, this is implemented by the user triggering the up/down inputs on an analog increment, then the output of the ainc should be run into an abuf with the enable on the abuf tied to a "Set" button on a tp.? The user will then be able to use the abuf to change the temperature and only after pressing the set button will this new value be sent to the module.? This, again, minimizes the number of API calls.?

As I said, this is a test version.? It is currently just sitting on my OneDrive.? If you guys give it a thumbs up I'll send it to my GitHub

Thanks

Jay

You can download it here:

?

Thanks for writing this up Nico.? Great information.?

I will take a look at my module and see if there are things I can do to minimize the calls to the Sensibo Cloud.

I will let you know.

Thanks again

Jay

On 8/2/2024 11:22 AM, nicofreda via groups.io wrote:

Hi Jay/Thorsten

?

using sensibo too since 1 month.. I have a CH system and at first, I've tried with the cpllc driver.. with only 1 sensibo at the system, it worked perfectly with no issues.. control and feedback works good.??

then the client liked it and wanted two more units to be controlled, so I've added two new sensibo extensions. same license cost for unlimited units verified by CPLLC. This didn't work for more than just hours.. (same error "429, too many requests... " that we all know about);

talked to randy at CPLLC and told me that it is something on sensibo's side.. and talked to sensibo and they said that their server is receiving more than 10 requests in a 10 second window, and that is their limit.?

I did tried to use an API key for each sensibo, with no success.. when I left the system back with only 1 unit, it worked fine again.?

?

then, I've tried to make it all the way around using a simpl program and Jay's module. Using Bacnet thermostats in CH, and the hosted remoted device/objects in simpl I've created the control within CH using simpl windows control of the sensibo.. all great with the first sensibo. worked flawless and fine, but same issue after adding the second unit: control and feedback became not constant, and start loosing two way communication. I'm using a vc4 and a mc4-r; I will try to enable logging in the vc4 and see if it is the same 429 error -> too many requests, and talked again with sensibo support, as I am guessing that maybe something changed in the server credentials/access with the requests, because as Thorsten said, with just a few commands, even within the "sensibo 10 commands-10second window", more requests are entering sensibo cloud..?

?

just one question thorsten: did your project has more than 1 sensibo unit?

I will also try to separate my sensibos in different accounts, so maybe they reach sensibo's cloud in different channels. I will share the results

?

regards

nico

On Aug 6, 2024, at 2:34?PM, Brad Wykoff via groups.io <bradwykoff@...> wrote:

?

I've used the Doorbird in the past but was hoping for something a bit less expensive.