Skip to content
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

No device config options #6

Open
ulihuber opened this issue Sep 22, 2023 · 5 comments
Open

No device config options #6

ulihuber opened this issue Sep 22, 2023 · 5 comments

Comments

@ulihuber
Copy link

Hi
thanks for your work :-)
I was able to install(copied the folder maxcul in custom_components and added integration). My gateway is a converted Cube.
Network and serial connections seem to come up without problems.
But I cannot find any configuration options for pairing with a thermostat. There is only the option to add a new gateway.
There is a config button attached to the gateway entries, but ther is not much happning, just an input field with a numer '1193046'.
Can you give me some advice?

Thanks
Uli

@powerpaul17
Copy link
Owner

Hello, pairing is enabled by calling the enable_pairing service of HA. The input field you are seeing is - if I remember correctly - some kind of cube device id. I built this integration to keep my cube alive for a few more seasons but I have only finished basic functionality (not very user friendly). This is also the reason it is not registered in HACS or such.. 😉

@ulihuber
Copy link
Author

ulihuber commented Sep 23, 2023

Thanks again for answering here :-)
I had success in pairing to a thermostat using full qualified path (telnet://myCubeNetworkAddress:2323) as Device Path. :-)
Now I see the climate entity.
It looks however like there is no reliable update on the values. Neither HA->thermostate no vice versa.
For example I expect to get a valve position when I go into boost mode at the thermostat. but nothing happens.
Did I miss anything? How is the update of values triggered? Do I have to do it manually in some way?
In further testing I found this repeating error msg:
2023-09-23 19:49:46.959 ERROR (Thread-4) [maxcul._io] Error reading from serial device <>. Try reopening it.
My config has only LAN/Telnet. So I guess that telnet is seen as serial device. But no idea why there is a communication problem. Could also be a problem of the quite old Cube...
I still did not manage pairing over CUL/USB. No idea what Device Path should be used to make it work. Tested with /dev/ttyACM0 as it is preset for the integration path and several variations. But no success.

@knutmk
Copy link

knutmk commented Oct 18, 2023

Did you managed to get connection over USB?
I experienced same problems with value updates.. im hoping to get more reliable informations running over USB...

@powerpaul17
Copy link
Owner

Editing device config options is not implemented. Please see my answer above: #6 (comment) I do not know if it works with USB, but it should, you have to find out the device path and use it instead of the telnet://[ip-address]:[port]

@knutmk
Copy link

knutmk commented Oct 19, 2023

Hello Paul, first of all great work. I was trying to get my CUL running for a few days and thanks to you it is now.

what I meant with my comment was that I can’t figure out a device path for USB. Telnet is working but seem not 100% reliable. So I wanted to try usb instead.

do you have any idea how the USB device path should look like? Simply using „/dev/ttyACM0“ is not doing the trick.

Also I’ve noticed two devices poping up in /dev one is the above and one is /dev/serial no luck with that either.

Thanks so much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants