My concern with my last response to @garz got me a little nervous and so I wanted to put something may atleast help reduce the risk. I just published 1.0.11 which is basically just a driver update for devices that use the Appliance API.
Simply put the updated drivers will now put the status of the device attribute into a "Pending" state until hubitat gets confirmation that the call was successful from the Govee API. So now you should see a very brief appearance of Pending for the device status when you change it. If it doesn't go away fairly quickly then there is likely a API problem or you have consumed your rate limits. In the event the rate limit has been exceeded it will retry in 1 min. I will likely continue to enhance this as we see other possibilities for it failing.
Yeah, I figured I'd use my ST button for temp sensors. I used them with dumb heaters on kasa em smart plugs. Worked well enough. My shut-off rules are set to kill power after 40 mins or when temp reaches preset. In the smaller rooms, it reaches it usually within 20-30 mins and the ST button doesn't update temp often enough.
I also make separate rule to check if the switch is running for longer than an hour. I guess I'd have it check the heater's attribute to do the same and also notify me if it's in pending? Is that even possible....?
I was kind of hoping I'd have real thermostat controllability when purchasing this govee heater, not necessarily through hubitat only, we like to use voice control for adjustments where an app is needed to control something.
That is a great way to handle it beyond what i added. Fantastic.
I will continue to look at and see if i can figure out a good way to monitor for that pending state.
You may want to look at a different model if you want it to be controlled by a built in thermostat. The 7131 I have, and it looks like the 7132 can control by temp on the unit themselves and has a Auto mode. They also have a auto mode to fully turn off after 24 hours and they have the ability to run as just a fan.
It doesn't make sense to me why my model is more expensive than the H1732 has less functionality. Luckily it has the auto 24 option within the APP and thermostat mode, just not in habitat. Maybe it'll be updated down the line. Can't imagine it's not just a software limitation at the moment.
Edit:
Does your model actually populate in HE as a thermostat? Like you can adjust the temp up or down with commands?
Nope it does not. Just using the one internal to the space heater. It does remember the last setting though so if HE turns it on today and then again tomorrow in auto mode it will know it is set to 68 degrees without me fiddling with it. That is a shame you don't have the Auto mode being presented through the API.
I am updating the driver now with a seperate attribute for the cloud api instead of using the actual item being changed. Probably should of done that first anyways. This will make it allot easier for you to monitor the API status from RM or anything else.
I just published the new code. I expanded the retry functions to the rest of the drivers. If the cloud api call fails they will retry in 1 min
There is now a new attribute associated with the devices which is "cloudAPI". This can be used as a custom attribute in RM to monitor events. As of right now it has 3 potential sates: "Pending", "Success", or "Retry". If i add a option to turn of the retry functions then i will add "Failed" as well.
Welp. Ran into api rate limiting. That was too quick.
I've noticed that it's still controllable via voice and Alexa/GH. I may just need to control it via virtual switch in Alexa routine. Just to enable and disable it, as a workaround.
There are two rate limits to consider. Max of 10 calls per min and 100 per day
It isn't hard to overwhelm the rate limit, but it seems like it should be fairly hard to get over 100 on one the day. What is the variance you are using for the thermostat set point vs turning on/off.
Question about their model numbers. Is it one of those things where you drop the last 2 or 3 digits?? Looks like all the ones in your list are H then 3 or 4 numbers and maybe a letter. The lights I'm looking at are H61211a1. I see an H6121 in the list, are these be the same?
Yea.. the model numbers seem to be H#### of some combination. I am sure there is some logic to how they are done, but I honestly don't get it. The numbers following that probably refers to the Controller hardware. I wouldn't worry about those
The need for diffusers is really just a concern if the strip will be visible to the naked eye. The raw pixels of a led strip can be a little alarming to the eyes. The diffusers should make the individual pixels indistinguishable. If you can position the strips to where they reflect light off of a wall or something else then diffusers aren't really needed.
You can also use Govee's Neon Rope Lights as they have a built in diffuser and are very flexible. There will be a small curve in the corner.
This is probably as tight of a curve as it can make as you can see i am pushing down the end.
That error above means you have made to many calls to the API and have hit the rate limit. How many times did you go into the device selection screen? You can either make 10 per min or 100 per day for the V2 api the appliances use.
I was able to reproduce this exact error condition by inducing to many calls.
This integration should make 2 calls to each api (v1 for lights, ect and v2 for appliances) when setting up devices. One when you click on the device selection option and then a final one when you click on done and the integration adds all of the devices. It doesn't matter how many devices you add at one time. Did you go in and out of the device selection option multiple times. That is how recreated the error.
How many times did you go into the device selection screen?
A few, trying to re-add my humidifiers, when I found out that they weren't paired anymore.
I had 1 piston on Webcore that overwhelmed my hub (i thing it was the reason the Zigbee radio turned off a few times during the last week. But this "I think" comes from a person who is a beginner to this things). Can it be another reason?
How can I correct this error so I can re-add my humidifiers?
Thank you for your help
So there are two levels of rate limits for the appliance API
10 calls per device per min and 10 devices lists per min. If this is the rate limit you hit you just need to wait 60 seconds.
100 calls per day for all appliance API calls. Depending on how many devices you have this one can be hit easier. This means waiting 24 hours.
My first suggestion is just to wait 24 hours from your last attempt and then try to add all the devices at once. 100 calls is not allot if you have several devices. This as I said previously will limit the setup to just two calls to the cloud api and minimize the rate limit impact.
Just out of curiosity how many devices are we talking about for govee appliances?
