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

Full Support for Salus SP600 Smart Plug #5600

Closed
incarvr6 opened this issue Dec 22, 2021 · 8 comments
Closed

Full Support for Salus SP600 Smart Plug #5600

incarvr6 opened this issue Dec 22, 2021 · 8 comments

Comments

@incarvr6
Copy link

incarvr6 commented Dec 22, 2021

As on this inclusion request
#812

My last post is ignored.

Multiplier is wrong for current and total consumption.
Current consumption is as attribute and should be as entity.

@incarvr6 incarvr6 changed the title Device nameSupport for Salus SP600 Smart Plug Full Support for Salus SP600 Smart Plug Dec 22, 2021
@incarvr6
Copy link
Author

Screenshot_2021-12-22-21-15-40-50_c3a231c25ed346e59462e84656a70e50

@Mimiix
Copy link
Collaborator

Mimiix commented Dec 22, 2021

Please fill the form instead of working around the template.

@Mimiix Mimiix closed this as completed Dec 22, 2021
@Mimiix Mimiix reopened this Dec 22, 2021
@close-issue-app
Copy link

Hi there.

Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed.
We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format.

In this regard, please take note that:
- read the template thoroughly
- all given header lines (starting with ###) must not be deleted
- everything enclosed by <!-- --> is intended to give you guidance and should be replaced by your input specific to the issue
- Listings regarding your environment must be filled out completely where applicable (bug reports and user questions).
- Not following the template or providing insufficient information can still implicate manual closure.
- Anything that is not clearly a bug can still implicate manual closure. For support we recommend the forum: https://forum.phoscon.de

So please, first help us a bit to help you!

@incarvr6
Copy link
Author

Why do same thing twice?
It is nearly impossible to do it on phone!!!

@Mimiix
Copy link
Collaborator

Mimiix commented Dec 22, 2021

We need the screenshots regardless because those show how the device presents them in the clusters. That issue is ages old and could have a way different firmware then you do.

Working around the template is not appreciated and feels very disrespectful.

@incarvr6
Copy link
Author

So tell me how I'm supposed to do screenshots on phone??!

@incarvr6
Copy link
Author

Screenshot_2021-12-22-21-26-48-57_c3a231c25ed346e59462e84656a70e50
Can you read something in here?? Well I can't...

@Mimiix
Copy link
Collaborator

Mimiix commented Dec 22, 2021

I can but it's not complete. But Frankly, it isn't our fault that you don't have access to a PC.

I'm locking this issue. Ether way, feel free to open another issue once you got access to a PC and the information.

@dresden-elektronik dresden-elektronik locked as too heated and limited conversation to collaborators Dec 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants