use oldism7proxy possible?

[mr-gosh]

I have an ism7i with FW-Version: 1.70 so i can communicate with

./oldism7proxy -i 192.168.1.127 -d

and that activate the config tool via:

./ism7config -i 127.0.0.1 -p secretpassword

but can I use that in the addon ass well?

[mr-gosh]

i tried to copy the oldism7proxy in the arm and arm64 version over to my HASS-OS to execute it by hand - but that doesnt seem to work - but do you plan to integrate the proxy into the addon as well?

[b3nn0]

No plans right now, no. You could of course run it manually somewhere else, and then point the add-on to it, but that's it.

[mr-gosh]

Thanks for the hint - executing the oldism7proxy on another machine works - but executing it directly on the pi running Hassio doesn't seem to work. Would be awesome if this functionality would be integrated into the add-on :D

[Chris2834]

I have also an ism7i with FW-Version: 1.70.. and acutally I do have a lot of dropouts via smartset cloud so I found this add-on via link.

I would hope to get the oldism7proxy included into the AddOn as well. ;-)

[b3nn0]

If someone provides a pull request that properly implements support for that, I'm happy to merge it. I have no way to test it myself. In fact, I probably won't even have a Wolf heater any more by the end of the year..

[b3nn0]

FWIW, I just checked. ism7proxy and oldism7proxy are currently not part of the official Docker image. We'd either have to download them dynamically if needed, or adapter the Dockerfile to not be based on the official ism7mqtt docker image, but instead build it ourself (i.e. base it on the DotNet SDK). Then add a configuration variable so the user can enable it, and adjust the run.sh script to launch it if configured.

Or ask @zivillian to add *ism7proxy binaries to the official docker image, then it would be a bit simpler. Only need new config variable and run.sh adjustments.

[aimoehi]

push i am on an even older firmware (1.60) and would appreciate a solution. or is there any way to update the firmware on the ism7? :D as the smartset portal obiously now blocking Hassio due to many queries ;)

thanks!

[zivillian]

Or ask @zivillian to add *ism7proxy binaries to the official docker image

I came up with an even better idea I'm currently working on. By integrating the functionality of oldism7proxy into ism7mqtt I can automatically detect the firmware version during the ism7config run, save this in the parameter.json and use this in ism7mqtt. This will transparently support older devices without any change to the addon and nobody needs the oldism7proxy anymore.

It would be great if some people with older modules could test this before I create a new stable release.

zivillian/ism7mqtt/issues/80 zivillian/ism7mqtt/pull/120

[mr-gosh]

I would be happy to assist Tomorrow I can test something for you.

[zivillian]

I've pushed some updates to master. If you want to try this with an old firmware device you will need to create a new parameter.json - ism7config should automatically detect that the default port is unreachable and fallback to the old port. This will also be stored in the parameter.json (hence the need to create a new parameter.json). ism7mqtt will read the port on startup.

If I'm right, there's no need to update anything in the addon itself.

[mr-gosh]

I've pushed some updates to master. If I'm right, there's no need to update anything in the addon itself.

So - this really worked! After I renamed the old paramters .json and switched to the experimental addon - everything works now.

Do I need to deactivate the cloud integration and how? The tick here doens't make the Wolf App unusable - so this seems not to be the coeection config?