Open BlurrySasquatch opened 1 month ago
Some more information after troubleshooting again.
We have two SleepNumber beds:
C2 Twin 360 I7 Queen 360 FlexFit 2
It seems that the error is only thrown for the C2 Twin. I confirmed the bed is online in Sleep Number app and it is detecting occupancy correctly.
Putting the occupancy sensors from the twin on the ignore list makes the errors go away, but would prefer they worked for all beds
Correction: putting the twin occupancy sensors on the ignore list makes the occupancy sensors errors go away, but the last error still appears and crashes homebridge
I haven't worked with a twin bed before, I bet there is some difference in the API since it doesn't have both sides present.
If you feel comfortable in doing so, I would love to see the API requests for controlling the bed. you would need to set up something like Charles proxy on your phone and set it up to do MITM https proxying to get the requests and responses for the *.sleepiq.* domain.
Describe The Bug: The plugin starts but almost immediately throws these errors
This then leads to the following error
Then homebridge restarts To Reproduce:
Enable the bed control plugin
Expected behavior: Occupancy sensor to work without causing a crash loop
Logs:
Plugin Config:
Screenshots:
Environment: