-
Notifications
You must be signed in to change notification settings - Fork 3
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
auto create parameter.json #11
Comments
Hmm, I think that should be fairly easy to implement. Is there an ism7config binary somewhere, so I can do a quick test? |
Never mind, found everything I need. Worked well for me. I'll leave the option to override it from the addon-settings, in case people only want to query specific values. EDIT: Are you interested in the log-output for generating the parameters.json for my CGW-2-20 for an additional data point? |
Thanks for your fast response. That sounds really good and I'll let you know here, when it's released. I would suggest to only generate the file if it's missing and store it in a permanent location, so anyone can remove unwanted parameters (I did this for at least 5 duplicates) or manually adjust the config. PS: |
I used this one I think: On creating, there was quite elaborate logging, and it did print some stuff that looked like errors, not sure if normal. Stuff that looked suspicious:
Can I assume that the ism7config binary will be part of your docker image? That would certainly simplify things for me a lot, because the Add-on builds on that one. And yes, the parameters.json will be stored in a user-accessible location to be modified, and only auto-generated if it doesn't exist. |
I've enabled trace logging for the smartset binaries in the ism7config tool, just in case something goes wrong. There may be some errors like yours, but as far as I can tell, this is normal since it's trying to detect the installed components and some may not be present. I will update the docker image to also contain the ism7config binary. It would be great if you can also test, but I think it's much easier after I've updated the docker image. |
I've updated the docker image (currently only the master tag to not break someones setup) to also contain the ism7config tool. |
Feel free to push it as a version/latest. The current add-on version explicitly references v0.0.12, so it shouldn't break anything for this add-on. Regarding the parameter file creation: I prepared everything to switch to v0.0.13 once it's on dockerhub. It will create the parameters.json in shared storage if it doesn't exist already, so the user can edit it if desired. |
Oops, something is strange with that version though. Seems to be the same schema for all sensors. |
sadly yes - the ids changed during the migration from the desktop to the mobile app - that's why v0.0.13 is also a breaking change in ism7mqtt |
What happens if you omit this? |
Unfortunately, migration is not really an option with the way mqtt discovery is implemented. |
It errors out with some XML parsing error stack trace.. didn't save it unfortunately, I can send it tomorrow if desired |
This is what I get if I run it without the mentioned environment variable:
|
I'll take care of the XML parsing - maybe it's already fixed in another branch... |
I've pushed a new docker image, which already contains the env variable |
perfect. Let me know once a consistent tag is on dockerhub, then I'll release the new add-on version. |
Hi! I'm using the new version @zivillian provided yesterday to create the parameter.json - in HA I get the following error: Starting ism7mqtt --hass-id=WolfLinkPro --interval=60 -t /parameter.json -d XXXXXXXX < WolfLinkXXXXXXXX2023-06-27T18:40:57300.10.1.300.300.13.0WOLFLink < Any ideas? |
The current version in the addon is still the previous version v0.0.12, with a different parameters file format. That's what we're working on right now to geht the new version in the add-on. |
Let me know if I can help in any way. I got a rare setup with a CHA-10 supported by a TGB-2. |
@b3nn0 I've pushed the v0.0.13 tag to docker |
Alright, bumped the addon version with v0.0.13, including automatic parameter.json generation. Let's see how it works out. |
@sniesen it would be great if you could test and confirm, that it actually works for your setup |
@b3nn0 I have a few comments and didn't know where to leave them. This shouldn't be needed anymore: hassio-addon-ism7mqtt/ism7mqtt/run.sh Line 14 in ef57467
Feel free to link directly to https://github.com/zivillian/ism7mqtt/issues/new: hassio-addon-ism7mqtt/ism7mqtt/run.sh Line 26 in ef57467
|
Ah, makes sense, yes. I wasn't sure if the v0.0.13 tag on dockerhub references yesterdays v0.0.13 tag on github, and would therefore still have the issue or not, so thought "better safe than sorry". But I just noticed that you re-wrote the tag, so I guess that should be fine. |
@sniesen That's good news - thanks for your quick feedback. Can you please check if you are able to write values like |
After reversing the android app, ism7mqtt no longer requires the smartset pc app and database to create a valid parameter.json. Instead there is an ism7config binary which directly connects to the ism, reads the available devices and parameters and writes them to the paramter.json. This is currently still in beta, because I haven't found anyone to test the new implementation.
Do you have any idea how this might be implemented for this addon? I'm still not really using HA, so I don't know how this is done by other integrations, but maybe you have an idea.
The text was updated successfully, but these errors were encountered: