Add bedjet as device instead of entity #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make manifest for my personal build
Adding missing new lines
Allow integration reloading without reboot, fix for "Dry" state, increase reconnect timer, standardize naming
Add support potentially for other bedjets - s-wachspress
Co-authored-by: cayZ <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have made a lot of changes to the general structure of registration of the bedjet device(s)
It is now possible to do automations through my changes now that it is registered as a device.
It currently is a bit wrong as it only registers 1 device and sets everything up as entities under 1 device, but that can be fixed later. It satisfies my requirements. Just wanted you to know what I had done so you can possibly take anything you like.