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

TCP configuration not available #7

Closed
ChristopheHD opened this issue Nov 30, 2024 · 12 comments · Fixed by #9
Closed

TCP configuration not available #7

ChristopheHD opened this issue Nov 30, 2024 · 12 comments · Fixed by #9
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@ChristopheHD
Copy link
Owner

See mak-gitdev/HA_enoceanmqtt#158 (comment)

@madejackson
Copy link

Looking at the code I'd say you just type tcp:address instead of the serial port (like /dev/ttyUSB0) into enocean_port =

@ChristopheHD
Copy link
Owner Author

Yes, but HA addon configuration does not allow to put serial port and tcp address in the same configuration option. Therefore the 2 must be separated, currently:
image
And I think I must add a separate one for tcp configuration.
I was thinking to review the whole configuration page so I may do this change with additions to others.

@ChristopheHD ChristopheHD linked a pull request Dec 2, 2024 that will close this issue
@TTr0n
Copy link

TTr0n commented Dec 4, 2024

Let me know, if you want me to test.
However, I will need a little help setting up the configuration ;-)

@ChristopheHD
Copy link
Owner Author

ChristopheHD commented Dec 5, 2024

Tests are in progress, I have some issue with updating the configuration schema (HA seems not to handle dynamically change in the configuration schema). I keep you posted.
Can someone confirm to me that the valid configuration for TCP is tcp:ip_address:port ?

@TTr0n
Copy link

TTr0n commented Dec 15, 2024

Any news ?

@ChristopheHD
Copy link
Owner Author

A bug have been found in Supervisor preventing to make the serial configuration optional link to the issue.
While this bug is corrected, I will keep the serial configuration mandatory but you will have a new field to make the TCP configuration. Therefore you will have to set the serial configuration with an unused serial port in order to start the addon with a TCP configuration (I will document it and you will have hint in the addon configuration screen).
I make some tests with this behavior and keep you posted.

@ChristopheHD
Copy link
Owner Author

Release 0.1.33 shoud work with TCP configuration, can you test ?

@TTr0n
Copy link

TTr0n commented Dec 16, 2024

Looks like connection is working:

2024-12-16 15:54:09,916 INFO: TCPClientCommunicator started 2024-12-16 15:54:09,916 INFO: Auto Teach-in is disabled 2024-12-16 15:54:09,916 WARNING: Replacing Packet.optional with default value. 2024-12-16 15:54:09,917 INFO: Sending packet 2024-12-16 15:54:09,923 INFO: got response packet: OK 2024-12-16 15:54:39,970 WARNING: Replacing Packet.optional with default value. 2024-12-16 15:54:39,970 INFO: Sending packet 2024-12-16 15:54:39,975 INFO: got response packet: OK 2024-12-16 15:54:41,766 INFO: unknown sensor: 01:A6:F9:4F (RORG = 0xf6) 2024-12-16 15:54:44,146 INFO: unknown sensor: 01:A6:F9:4F (RORG = 0xf6) 2024-12-16 15:54:46,452 INFO: unknown sensor: 01:A6:F9:4F (RORG = 0xf6) 2024-12-16 15:55:09,990 WARNING: Replacing Packet.optional with default value.

The unknown sensor is a Hoppe Secu Signal window handle, EEP F61000
How to config it in .devices ?

@ChristopheHD
Copy link
Owner Author

Like that:

[fenetre_chambre_3]
address 		= 0x01A6F94F
rorg    		= 0xf6
func    		= 0x10
type    		= 0x00

@TTr0n
Copy link

TTr0n commented Dec 16, 2024

Ok, done ... no more unknown sensor, but no message from known sensor, ist it ok ?
Where do i find the sensors? There isnt anything .. !?

@ChristopheHD
Copy link
Owner Author

It's normal behavior to see no logs of known sensor.
You can find the sensor in the list of devices of Home Assistant.

@TTr0n
Copy link

TTr0n commented Dec 16, 2024

sorry
Wrong MQTT Port in config ...

Now it works, well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants