TheRealKillaruna / nano_pk

Home Assistant integration of Hargassner Nano-PK
Apache License 2.0
21 stars 17 forks source link

Question: Does/how will it work with Internet Gateway installed?! #10

Closed Spacey-Rat closed 10 months ago

Spacey-Rat commented 1 year ago

Hi! I've already got the Hargassner Internet Gateway installed and got my Nano PK in the Hargassner App. The internet gateway interface got an local IP address. Now I tried:

A) Connect a second network cable to the network socket next to the Hargassner touchscreen to my switch. Here this connection got a hardware link but doesn't get an IP address (DHCP of course active) AND my other internet gateway connection drops: I get a message from Hargassner that my device lost its internet connection.

B) Tried to enter/use the LAN IP from the internet gateway - but doing so doesn't give me any new sensors within HA so I guess this doesn't work.

Anyone any ideas here?

Thx!

PierrePetite commented 1 year ago

We have the same issue with a different Hargassner Device, which also connected with the gateway and not directly. I will keep you updated if I can figure something out.

TheRealKillaruna commented 1 year ago

As I don't have the Internet Gateway, I can't say anything about this. I have seen another integration somewhere that used the Gateway instead of the Hargassner device, this might be something you could try out.

iamthe1st commented 1 year ago

Hi, for me it works with the gateway like that: First connect the Control directly to your lan (no gatway), set your router to give always the same ip to this device. Note the IP-Adress, this is the one to use for your configuration. Get your Home-Assistent setup running - When you get it running, install the gateay in the middle between your Control and your LAN (like in the manual).

nopbop commented 1 year ago

Hi, for me it works with the gateway like that: First connect the Control directly to your lan (no gatway), set your router to give always the same ip to this device. Note the IP-Adress, this is the one to use for your configuration. Get your Home-Assistent setup running - When you get it running, install the gateay in the middle between your Control and your LAN (like in the manual).

This works for me. Thank you.

Spacey-Rat commented 11 months ago

Tried my luck again today - but nothing. To sum up:

KD=Hargassner KT=Nano.2(.3) 15 Plus SW=V14.0HAR.o3 HW=V1.2.0

I've got the internet gateway which is "normally" connected to my switch for having the Hargassner-App running. The gateway is somewhere inside of the whole Nano unit, at least the network cable comes out from the back. Then I've got the network port next to the touchscreen on the front (covered by that rubber thing, next to the SD-Card slot).

Now unplugged the "gateway" cable and tried to connect the port on the front to my switch: The whole Nano unit restarted! After that the network port on the switch shows some connection for about 30 seconds and then turns off. The unit get's no IP whatever I try (it is set to automatically in the nano touchscreen in the network config section - Once it'd get an IP dynamically I could set it to a fixed one in my DHCP.). Even my Unifi control software shows me no connection on that port.

Then I re-connect the "gateway" cable and the app is working again and the nano unit gets it's usual IP for the gateway. Trying just to use this IP within the HA plugin brings me just "unknown" states of the sensors in HA.

Any more suggestions what to do?! Sorry if I misunderstood smth.

Addition: I changed the msgformat="<DAQPRJ> ... </DAQPRJ>" to the one from my captured log into my config yaml - and now I get at least some temperature values when I check the nano sensors within HA.

Kk5519 commented 10 months ago

Hello, I have the same configuration (gateway). When I read the data at the gateway I get a record (approx. every 0.5 sec.) without a header (example: pm 1 1.2 7 64.1 0 64.3 36 5 62.6 0 0 67.3 66.8 43.3 85 49 0 2 0 67 0 0 30 100 30.5 30.5 0 86.4 83 3 0 49 0 2 13 0 0 0 0 81 0 0 2073 5015 4284 0.00 0.00 -4 50.4 24224 140.0 112.0 28 -20.0 -20.0 0.0 8.0 7.4 0 -20.0 0 20.0 20.0 0 1 50.2 49 22.6 23.4 1 1 16.3 0 16.1 9.9 3 2 -20.0 0 20.0 20.0 0 1 -20.0 0 68.9 0 0 -20.0 0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 406 1000 8 0 2007 0 0 0). What does the data stream look like directly at the boiler (or inside Home Assitant)? Is this always with a header? My HA log contains the error message: "HargassnerBridge.setMessageFormat(): Message template does not start with ''.". Thanks for all the information and the work already done.

iamthe1st commented 10 months ago

Hi, in the attachment you can find my working "custom_components\nano_pk" Folder and the relevant part of my working configuration.yaml

Please delete your "custom_components\nano_pk" Folder and replace it with the one from the ZIP. Then replace your "configuration.yaml" with the content of the "configuration_Working_04-01-2024.yaml" Also change the IP address in the line "host: 192.168.178.38" with the ip of the your Hargassner unit. nano_pk.zip

Then reboot Home Assistant - then you should get all the values/sensors.

Kk5519 commented 10 months ago

Thank you very much, that helped me a lot! I have used your files, but unfortunately my structure (Hargassner software) is slightly different. I have now first adapted the configuration.yaml (without touching your other files) by transferring my structure (after correcting special characters) from the memory card. There is already a lot of reasonable data, but I still have to reduce it. Maybe an integration of the current software version into the project makes sense. That's why I'm attaching the .DAQ file of the memory card and the configuration.yaml file that I changed.

configration kk.zip

iamthe1st commented 10 months ago

The easiest way is to get all the data and only view/use the ones you are interested in.

The data layout and names changes sometimes, so the easiest way is to get all data and just ignore the not interesting stuff.

TheRealKillaruna commented 10 months ago

Since more people are using the integration for more different devices with different firmware versions, it will be challenging to support all variants with an easy default solution. Indeed, what should always work is to use the message format from your own DAQ logfile with full parameter set (as you are successfully doing it now, it seems).