-
Notifications
You must be signed in to change notification settings - Fork 36
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
CTR-01 switches no longer come up in HA #205
Comments
The main change in 0.8 is that we register outputs rather than physical devices. Plejd devices without outputs configured will not show up, which should be consistent with the plejd app. If you get complete verbose or silly logs from the startup you will see everything that happens, what devices are configured/not and hopefully also why. |
SweVictor Everything is working fine in my plejd app. Forget about the ctr-01! I saw now that I have them also, but it´s always the same units that is found in HA??? 2021-06-15 19:59:48 WRN [device-registry] Trying to set state for null which is not in the list of known outputs. This you mean about in the log? |
5 times I deleted and reinstall the plugins without success |
Typical example would be REL-02 which is a Plejd device with two outputs. From 0.8 that physical device will show op as TWO devices in HA, each with one controllable switch entity. Plejd devices configured as "no load" will not show up at all.
If you turn on verbose logging you will see what led up to this, but typically this is an update sent by a device not known by the addon. I get this a bit for example for devices without loads. It could probably be improved code-wise and log-wise but it's not a real problem. The only thing we could do with these messages is log that "we got this message which does not affect any state in the system, discarding".
Sorry to hear that. It seems that some things are up and running so hopefully it is solvable. If you can, please export the full logs in verbose or silly mode, scrub sensitive information and paste a link to the file and I'll have a look at it. Please also include what you are missing specifically and what is included on the HA side. If you want to look into this yourself the first thing that happens is API request and parsing of all devices which is logged. You can also look into what the addon registers to mqtt using for example the tool Mqtt Explorer. |
Now I even tried to reinstall whole HA with the same result. These 16 units come in as they should, but 19 units are still missing and not showing up in HA. I´m running on RPI4 with SSD disk. I´m not able to look at api problems, just a regular user and it feels like this is something wrong. I used this plugin from when it was released, and I have never got any problems with the units. I upload two logging files. One from start of the addon, and one when it have running a little. |
Hmm... From the
Do you have any issues with the above devices? |
No, thats 10 of the 16 that is working in HA. |
And I can not find a common thread because there are various used devices that do not come in. Always the same 16 units that enter HA even after a reinstallation of HA. |
Well, I understand you have issues and no, I don't think reinstalling will help. I do however need more complete logs to be able to help. As an example, from restarting my own plejd addon and getting full logs I get this:
So, if you could follow the readme and extract full logs from the startup as well as identify what devices you are missing I can hopefully help out. Currently I don't see enough in the logs unfortunately. |
How will I get a complete logfile when the start disappears after click on update? |
Please refer to the https://github.com/icanos/hassio-plejd/tree/master/plejd#troubleshooting section for general troubleshooting (you could for example look at the mqtt messages coming to HA from Plejd) and the https://github.com/icanos/hassio-plejd/tree/master/plejd#logs section for extracting full logs. |
Here you get a new logfile[ |
Nice, thanks, that for sure IS a very complete log :-) I agree it's quite cumbersome to get logs, but I don't know how to fix that since Home Assistant sandboxes all addons in their own docker containers and only exposes a very limited log. Either way - the logs shows quite a lot of devices hidden, could these be the ones you're missing? If not, please specify a few devices you are missing. Relevant part of log
|
All the devies you named is not in my HA. But what you mean with hidden? Of 35 devices I have just one hidden in my plejd app, because it´s a stair coupling. |
Alright, so we have the reason then. This was discussed in #179 and in the end we (probably I) decided to hide both devices In MY installation @faanskit @vBrolin - since you were part of the discussing in #179 - any ideas on what |
@SweVictor |
I'd speculate that it stems from
That is in the Plejd app, if you select "Hide from room view" for a device - parameter will be true. I can find good arguments for both variants. And with that comes my sad conclusion: We need another configuration: BR, Marcus |
@faanskit |
@Mikro007 , ok. To quick to conclude then. :-) You have 17 devices that have One example is:
Can you tell if there are any special settings with that device since it is registered with Plejd as hiddenFromIntegrations. I think the resolution will almost be the almost the same; a new configuration: I'll poke around in the app and my testsystem, but if you can already point of what is different in the app it will be faster to reach a conclusion. |
Nothing special with that unit, just a regular ctr-01. And it's not hidden in my app, like the other 17 that's are missing. |
Ok, I know what it means now.
Configure->Gateway->Integrations->Settings for integrations Here you can decide how it shall be integrated:
The implementation in HA makes sense. This is a "kind of" integration and if you as a user has requested in the app to exclude it from integrations, it should not be integrated in HA either. Please confirm by enabling one of the problematic devices for integrations. If my hypothesis is correct; this is a feature not a bug ;-) |
Just tested with changing the exclude/light option in the plejd app and as expected the device shows up in HA when I set it to light. |
Thanks for confirming my hypothesis. We can thus conclude that this is a INABIAF.
I still consider the current behavior is the correct and expected one. However, I still honor the though of an alternative reality. My humble proposal to facilitate this feature request is to add two configuration options:
/Marcus |
This would be much appreciated. |
Interesting, and very nice finds eveyone. At least we know WHY this happens, good job everyone! Possibly the setting is a good way to solve this, a bit annoying to have too many settings though. Btw - after connecting Google Home to Home Assistant I suddenly got double all Plejd devices. So that will also be a thing for may people... |
I vote for @axlthorell solution. In my situation I will now need to by a new gateway because my old is broken. I can't reach this option in the plejd app. |
Yea, configuration options are bad. Both for usability and for maintainability. In this case dual behavior are reasonable and can motivate. I do have an idea of a variant, but not sure it is fully thought through. I'll collect my thoughts on that and revert back.
Yea, that is a drag and I honestly think the only way is to only have one integration to Google. But the option to exclude things from Google is available in Plejd as well as in Home Assistants Google Integration via the I think that the Plejd code will change in a not so distant future. As soon as their integration to HomeKit is released, with an assumption that they will allow parallel integrations to both Google and Apple; a single parameter is not enough.
@Mikro007, there is one more option for you if you are in a hurry. I hate to tell it to you with the amount of devices you have; but you could remove the problematic ones and add them again. |
Would it be better to have HA include all plejd devices as it did before? It is possible to hide devices in HA. |
Nope, did not work. I was thinking that we could set I have second thoughts about the proposed override configuration, especially with the roadmap towards HomeKit. The parameter is there to hide the integration from towards Google - not Home Assistant. The current implementation only limits the use of HA, and is against the "spirit" of HA. The user can hide those devices himself in HA if he does not want them there. It's not up to this integration to judge. And the user can hide it from Google both in Plejd and HA. Therefore: Remove the check. Get all devices in. Let them free. /// About hideFromRoom list. I do not know the current behavior. But; similar to above - ha-plejd should not be the judge. Let the devices in and let the user remove them from the Ui instead. |
If you mean Plejd gateway you should be able to get very similar functionality with HA + this addon without the Plejd Gateway if you want to save some money.
Well, conceptually I'd say it's a setting for all integrations (Google, Amazon, custom-hacked Plejd, ...), but sure, I see your point.
This is an interesting option I think. No-config adding of all things, up to user to hide stuff or include in custom dashboards. While I personally use hideFromRooms to remove things I don't want to/can't control (at all) and don't "need" them in HA I wouldn't have problem if they were shown in HA. What do you think guys, anyone against just adding everything? @icanos wanna veto such a change? 😄 |
I think he meant that he cannot use Plejd app to change the Hide From Integrations since he no longer has a Gateway. Without a gateway, you cannot even get to that part of the Ui.
I think that was the original intent, but current implementation differs. Check the app. You need to go all the way into the Google Integration to turn them on/off. So; Ux wise you do it per integration. Codewise, it's just one parameter.
You have my vote. Revert back to original behavior, unless that config option is desired. |
Alright, good. For the record I think we used the "hide from rooms" settings "originally". |
Can you create a PR and have the addon include all devices? Thanks! |
So - PR is up, finalized what I've been doing here #207 You can download feature branch files and manually install to test the changed functionality and report back if you have a possibility. |
Works perfectly! |
Great to hear, I'll close this and merge the PR to develop at least quite soon. Hold off with full release a while pending feedback on v0.8 |
After I made an upgrade of HA to the latest version 2021.06.04 and followed the guide in this app, I did not succeed.
Has uninstalled both plejd and mosquitto apps. Restarted HA and done as it says in the guide. But now when I start running the used app again, I only get 16 units out of 33. And from what I have seen, it seems to be CTR-01 units that are missing.
Any idea what I can do to make it work again?
The text was updated successfully, but these errors were encountered: