Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sinric Pro did not connect #408

Open
icebear74 opened this issue Dec 5, 2024 · 19 comments
Open

Sinric Pro did not connect #408

icebear74 opened this issue Dec 5, 2024 · 19 comments
Labels
stale Issue that may be closed soon due to the original author not responding any more.

Comments

@icebear74
Copy link

This is my first project, i try to include sinric, but it wont connect ..
in debuglog this is the only i see : [SinricPro:Websocket]: disconnected

The Key / secret are correct ..
Is there a Problem with your Server ?
Greeting
Holger

@kakopappa
Copy link
Contributor

kakopappa commented Dec 5, 2024 via email

@icebear74
Copy link
Author

it was the SSL thing ... D1 Mini seems to have not enough memory to do ssl ...
Disabled and now it works ..
Thank you ..

@icebear74
Copy link
Author

icebear74 commented Dec 5, 2024

How i can report back the actual state ? I have this in my callback function ..
bool onPowerState(const String &deviceId, bool &state) {
powerState = state;
if (state) {
firstStart = true;
} else {
Serial.println("Dunkel");
dunkel();
pixels.show();
}
i want to initialy (on device start) report the state of the device ..

@kakopappa
Copy link
Contributor

kakopappa commented Dec 5, 2024 via email

@icebear74
Copy link
Author

hmm but how to report the state back to google ? eg when i switch manualy ?

@sivar2311
Copy link
Collaborator

sivar2311 commented Dec 5, 2024

Every device has a sendxxxEvent function.
See documentation

and switch example

@icebear74
Copy link
Author

thanx .. works fine .. but .. it seems there is a bug in brightness control ..
when i say google it should make the light darker i get a onBrightness Event with brightness 0 (not a little bit darker) .. before was set brightness 30..
any suggestions ?

@sivar2311
Copy link
Collaborator

sivar2311 commented Dec 5, 2024

"Make the light darker" should result in a call to onAdjustBrightness instead to onBrigtness !?

@icebear74
Copy link
Author

it calls onBrightness with value 0 .. :(

@kakopappa
Copy link
Contributor

SinricPro just pass the values back from GH or Alexa to modules. try setting it to 100 and gradually lowering to find out the adjustments

@icebear74
Copy link
Author

but why is called onBrightness and not onAdjustBrightness ?!

@kakopappa
Copy link
Contributor

kakopappa commented Dec 5, 2024

Google Home always sends the new percentage value not the adjusted value

Behavior Boris described is how Alexa works.

@icebear74
Copy link
Author

Well .. Than brightness control is useless for me, when it send 0% for "Darker" ...

@sivar2311
Copy link
Collaborator

That's how GH interprets.
Did you try something like "increase brightness" / "decrease brightness" ?

@icebear74
Copy link
Author

Google answer correct .. with other lights it works fine .. (Google answers, thats it makes the light darker) .. in german for sure :)

@icebear74
Copy link
Author

when i figure out right, there is a flag to set in the trait to interpret it correct .. perhaps you take a look ?
action.devices.commands.BrightnessRelative must be true to get relative brightness ?!
here https://developers.home.google.com/cloud-to-cloud/traits/brightness

@icebear74
Copy link
Author

perhaps also this commandOnlyBrightness ....

@kakopappa
Copy link
Contributor

You can still calculate the adjusted value based on current brightness - new brightness.

Harmonizing GH, Alexa and SmartThings needs to handled in a separate issue.

Copy link

This issue has gone quiet. Spooky quiet. We currently close issues after 14 days of inactivity. It’s been at least 7 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. As a friendly reminder, the best way to fix this or any other problem is to provide a detailed error description including a serial log. Thanks for being a part of the SinricPro community!

@github-actions github-actions bot added the stale Issue that may be closed soon due to the original author not responding any more. label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue that may be closed soon due to the original author not responding any more.
Projects
None yet
Development

No branches or pull requests

3 participants