-
Notifications
You must be signed in to change notification settings - Fork 1
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
Installation unclear - HA beginners unclear #1
Comments
Hi, point 3 has nothing todo with HA, there are screenshot how you have to set the config in your IDM interface. |
In the IDM interface I know what to do. That is easy and already done. I refer to the last point here:
|
That's correct. Then you mean this step:
I can create a detailed description but I opened already a feature request here, because the developer here has already used my sources and put it into an HACS Repo / Integration. But at this moment he can only read data and not write the data. |
Correct I know this integration and use it ;-) And I miss the writing to PV values. |
I have copied and adapted your scripts just to have a writing to the pv values to the idm heat pump. This spams my log with unneeded values. It seems it is kept over from reading values, which I removed. However it still tries to read them? I don't understand the standard implementation of TCP modbus. Any idea to prevent these logs or not needed readings? |
Sorry, I have no idea why there is a modbus restart needed to establish a second write to this modbus register on the idm. I checked already something with the data type, but i think the data type is still correct... If you have any idea / someone who can give a hint, post it here 😉 |
I know there is an issue with the modbus implementation. I just wanted to know to prevent the logs. There are massive entries and I don't know to prevent them... |
Probably found the solution: logger: |
I really struggle with this point:
How should that be achived? HACS? Copying files? Sorry but I am not really familar with HA.
The text was updated successfully, but these errors were encountered: