-
Notifications
You must be signed in to change notification settings - Fork 680
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
[Device Support Request] Add support for ptvo.info - ptvo.switch #416
Comments
I asked the developer of that firmware already. Unfortunately, he not accepted all of that wishes.
answer was:
Comment about "See #2" he meant the ability to have more then one sensor on one bus, but with different addresses, but our problem - it is about many values for the one endpoint. Sadly, i not sure, is it possible to make the quirk for that firmware - it not have any "signature". All components, what can be used for identification - all is variables. There are only one posibility - to introduce some selection the quirk by the hands (from GUI or YAML). |
We will be able to do this in a quirk without an issue. The value that is reported has enough info to split this up correctly. I’ll get something together when I have a moment. |
I mean not the quirk itself, i mean the detection of apllyment of that quirk. That is not a device with the fixed endpoints and manufacturer. They are may be any combinations. So - how to detect the need of the quirk? |
Interesting, what is this then? Do you have a link to the product? |
@dmulcahey Of course, the link |
Interesting, is there a way to change the manufacturer and the model? If so, users would need to add their own custom quirks locally. |
Yes, it is easy - some fields in the "Expert" configuration tab. There are some defaults, but it can be changed easy. As the varyant, they are may be fixed in the requirements to use of this device with Home Assistant |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions. |
Does anyone has come up with some example or stub of a quirk for ptvo? |
Is your feature request related to a problem? Please describe.
Moved from HA core repo:
No objects for bmp280 Data Clusters.
Can't read value from temperature, humidity, pressure.
In logs DATA exists.
Only switch and binary sensor is is created.
Describe the solution you'd like
Translate the 3 readings on the analog input cluster into the appropriate ZCL clusters for temperature, humidity and pressure
Here are the logs
Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.
Device signature
Additional context
home-assistant/core#37845
The text was updated successfully, but these errors were encountered: