[SOLVED] HestiaPi Touch US version


#8

Thank you for the quick and thorough response, I will give it a go.


#9

OK, looking this over again, I still need to connect the red (24VAC) to something so that the correct voltage can be applied to the heating (White) and the fan (green). There was an older post ([SOLVED] HestiaPi Touch United States Wiring) that included an instruction for cutting out a path on the back of the board and soldering the red line there (https://community.hestiapi.com/uploads/default/original/1X/2a6cb8dc5136b62a990fb7a92f727b75bda8a381.png). Is that what I need to do in this case, along with your instructions?


#10

You are absolutely right. I missed this important bit. Is your PCB the same as the post?


#11

I’ve ordered a US version, but since I waited until after you had started the fundraiser, I ordered it through there. Although I was happy to do that, I will not receive my new US version with air conditioning control until September/October, and it’s 90 degrees in Ohio now. I thought it would be as simple as switching the heating and cooling wires to the thermostat, and then also switching the pin assignments in the /etc/openhab2/items/default.items file, but that doesn’t seem to work. When I turn on"Cooling", it now turns on the AC compressor, but the blower never comes on. What am I missing?


#12

Show us a picture of the wiring changes you made and the changes in the files you’ve made to be able to comment on that please


#13

Sorry, was referencing all the way back to the beginning of this post.

The contact labelled for Hot water (pin 12) WAS connected to Heating wire (W - white), and is now connected to the cooling wire (Y - yellow).

Previous/working code for heating:
Switch HeatingPin “Heating” { gpio=“pin:12”, mqtt=">[mosquitto:hestia/local/heatingstate:command:ON:1],>[mosquitto:hestia/local/heatingstate:command:OFF:0],<[mosquitto:hestia/local/heatingstate:state:MAP(binary.map)]" }

Switch CoolingPin “Cooling” { gpio=“pin:18”, mqtt=">[mosquitto:hestia/local/coolingstate:command:ON:1],>[mosquitto:hestia/local/coolingstate:command:OFF:0],<[mosquitto:hestia/local/coolingstate:state:MAP(binary.map)]" }

Switch FanPin “Fan” { gpio=“pin:23”, mqtt=">[mosquitto:hestia/local/fanstate:command:ON:1],>[mosquitto:hestia/local/fanstate:command:OFF:0],<[mosquitto:hestia/local/fanstate:state:MAP(binary.map)]" }

Current, non-working code for cooling (condenser turns on, but not fan):
Switch HeatingPin “Heating” { gpio=“pin:18”, mqtt=">[mosquitto:hestia/local/heatingstate:command:ON:1],>[mosquitto:hestia/local/heatingstate:command:OFF:0],<[mosquitto:hestia/local/heatingstate:state:MAP(binary.map)]" }

Switch CoolingPin “Cooling” { gpio=“pin:12”, mqtt=">[mosquitto:hestia/local/coolingstate:command:ON:1],>[mosquitto:hestia/local/coolingstate:command:OFF:0],<[mosquitto:hestia/local/coolingstate:state:MAP(binary.map)]" }

Switch FanPin “Fan” { gpio=“pin:23”, mqtt=">[mosquitto:hestia/local/fanstate:command:ON:1],>[mosquitto:hestia/local/fanstate:command:OFF:0],<[mosquitto:hestia/local/fanstate:state:MAP(binary.map)]" }


#14

Please paste your rules file in a pastebin and send us the link. The above code changes are only the gpio pin swap and they should be enough.
Are you sure the same Fan wire is used both for heating and cooling?


#15

My original thermostat had only a single fan connection point, and there is only a single wire from the thermostat to the furnace for the fan. It’s hard to say, but I’m pretty sure I could hear both relays click on when the furnace ran, but I’m pretty sure I only hear the one click on now. I’ll paste the rules file now. Thanks.


#16

I’ve not used pastebin before - hopefully I did this right:
https://pastebin.com/V2bSDpS1


#17

Everything looks good.
Please enable debug mode over SSH by following the steps in “Start OpenHAB2 in debug mode”
https://hestiapi.com/faq/

And run through the scenarios where the fan should start while monitoring in real-time the debug log. Please report back here your findings


#18

==> /var/log/openhab2/events.log <==

2019-06-29 19:04:31.172 [vent.ItemStateChangedEvent] - MyHumi changed from 70.2 to 69.9

2019-06-29 19:04:31.484 [vent.ItemStateChangedEvent] - MyHumiProxy changed from 70.2 to 69.9

2019-06-29 19:04:52.111 [vent.ItemStateChangedEvent] - MyHumi changed from 69.9 to 70.0

2019-06-29 19:04:52.337 [vent.ItemStateChangedEvent] - MyHumiProxy changed from 69.9 to 70.0

2019-06-29 19:05:02.641 [vent.ItemStateChangedEvent] - MyHumi changed from 70.0 to 70.1

2019-06-29 19:05:02.871 [vent.ItemStateChangedEvent] - MyHumiProxy changed from 70.0 to 70.1

2019-06-29 19:05:07.151 [ome.event.ItemCommandEvent] - Item 'CoolingMode' received command ON

2019-06-29 19:05:07.314 [vent.ItemStateChangedEvent] - CoolingMode changed from OFF to ON

2019-06-29 19:05:07.788 [ome.event.ItemCommandEvent] - Item 'CoolingPin' received command ON

2019-06-29 19:05:08.224 [ome.event.ItemCommandEvent] - Item 'FanPin' received command ON

2019-06-29 19:05:08.512 [vent.ItemStateChangedEvent] - CoolingPin changed from OFF to ON

2019-06-29 19:05:08.568 [ome.event.ItemCommandEvent] - Item 'TempMaxSetpointChart' received command 72

2019-06-29 19:05:08.790 [ome.event.ItemCommandEvent] - Item 'MainSwitch' received command ON

2019-06-29 19:05:08.860 [ome.event.ItemCommandEvent] - Item 'HeatingMode' received command OFF

2019-06-29 19:05:09.162 [vent.ItemStateChangedEvent] - TempMaxSetpointChart changed from 0 to 72

2019-06-29 19:05:13.080 [vent.ItemStateChangedEvent] - MyHumi changed from 70.1 to 70.0

2019-06-29 19:05:13.308 [vent.ItemStateChangedEvent] - MyHumiProxy changed from 70.1 to 70.0

2019-06-29 19:05:23.611 [vent.ItemStateChangedEvent] - MyHumi changed from 70.0 to 70.1

2019-06-29 19:05:23.847 [vent.ItemStateChangedEvent] - MyHumiProxy changed from 70.0 to 70.1

2019-06-29 19:05:35.892 [ome.event.ItemCommandEvent] - Item 'CoolingMode' received command OFF

2019-06-29 19:05:36.093 [vent.ItemStateChangedEvent] - CoolingMode changed from ON to OFF

2019-06-29 19:05:36.320 [ome.event.ItemCommandEvent] - Item 'CoolingPin' received command OFF

2019-06-29 19:05:36.730 [ome.event.ItemCommandEvent] - Item 'TempMaxSetpointChart' received command 0

2019-06-29 19:05:36.811 [vent.ItemStateChangedEvent] - CoolingPin changed from ON to OFF

2019-06-29 19:05:36.941 [vent.ItemStateChangedEvent] - TempMaxSetpointChart changed from 72 to 0

#19

I turned it on, waited a few seconds (only heard one relay click), then turned it back off


#20

And got this too, not sure if it’s related (I assume not, but shouldn’t assume):

==> /var/log/openhab2/openhab.log <==

2019-06-29 19:07:15.687 [WARN ] [he.commons.httpclient.HttpMethodBase] - Cookie rejected: “$Version=0; __cfduid=db3de8f3f2c88cd530065699b2a5c7b721561849635; $Path=/; $Domain=.icanhazip.com”. Illegal domain attribute “.icanhazip.com”. Domain of origin: “icanhazip.com


#21

Ignore this. It is a service that gives us our public IP and I block any cookies from them.

Can you connect the wires for AC and Fan together on the AC terminal on HestiaPi?
I am not sure if your system has a delay or something for the Fan when it is on AC mode.
I assume the pin assignment on HestiaPi Touch US version is correct, pin 23 is actually connected to the relay where you connect the Fan. You could check with a multimeter if the output of each relay is active (24V AC) when triggered.
You can manually control the state of the 2 relays with this:
https://www.openhab.org/docs/administration/runtime.html
Could the fan relay have died somehow?


#22

The 2 relay clicks are 500msec apart (19:05:07.788 - 19:05:08.224) so not being able to tell them apart is possible


#23

I’m wondering if the fan relay died. I’d love to manually trigger it to test, but I can’t figure out how to do it from the link you sent, sorry. Very very unfamiliar with openhab. I’ll try wiring the cooling & fan pins together. I’ll try to get a tester on the relays, but I have to take off the display to get it off the wall to get to the actual relays, so I’d rather try other testing methods if I can. 500msec sounds right, when the furnace was running over the winter, I heard the double-click of the two, but swear I can only hear one now.

Is there anything to the fact that via the debug output, it shows “ItemCommandEvent” for CoolingPin received ON, and then the “ItemStateChangedEvent” for CoolingPin changed from OFF to ON - but after the “ItemCommandEvent” for FanPin received command ON, there was no subsequent “ItemStateChangedEvent” for FanPin from OFF to ON?


#24

So, I added the line “Switch item=FanMode mappings=[ “ON”=“ON”, “OFF”=“OFF”/, “Schedule”=“SCHEDULE”/]” to default.sitemap, and now I have a switch on the OpenHab BasicUI page. Assuming that’s all I have to do - when I click it on or off, the relay does not react. I get the following results in from the debugger, though:

2019-06-30 11:02:45.435 [ome.event.ItemCommandEvent] - Item ‘FanMode’ received command ON

2019-06-30 11:02:45.619 [vent.ItemStateChangedEvent] - FanMode changed from OFF to ON

2019-06-30 11:02:53.697 [ome.event.ItemCommandEvent] - Item ‘FanMode’ received command OFF

2019-06-30 11:02:53.855 [vent.ItemStateChangedEvent] - FanMode changed from ON to OFF

2019-06-30 11:02:55.454 [ome.event.ItemCommandEvent] - Item ‘FanMode’ received command ON

2019-06-30 11:02:55.602 [vent.ItemStateChangedEvent] - FanMode changed from OFF to ON

2019-06-30 11:03:24.520 [ome.event.ItemCommandEvent] - Item ‘FanMode’ received command OFF

2019-06-30 11:03:24.669 [vent.ItemStateChangedEvent] - FanMode changed from ON to OFF


#25

So, IF what I did should trigger the fan relay on and off, then I think there is something wrong with the relay. Am I correct in assuming it should not matter what pin I have what wire connected to (on the “furnace side” of the relay, not the raspberry pi side of the relay)? Sending the command to turn the fan relay on or off should trigger that on or off, regardless of what is connected to it.


#26

All logs look normal and a faulty relay sounds like the most possible cause.
The relay should trigger even with nothing connected. I am suspecting the relay during testing or something caused a shorting and fused the contacts together on the output side. Or it simply died a few thousand clicks before its time. If you shut HestiaPi down, one simple test is to remove the LCD and measure the voltage with a multimeter between Ground (GND) and the pin for the fan. It should go to 3.3V. If it does and the output of the relay is not 24V AC, then swap the relay with a new one. Its a fairly standard type and you won’t have a problem sorting. One of the reasons why we insist on using common components.


#27

I was thinking about the fact that I had tried rebooting it several times, but not shutting it all the way down. So I did a shutdown via SSH, and as it was shutting down I heard a “clack” of a relay. I booted it back up again, turned on the cooling system, and heard the “click-click” of the two relays turning on. I now have AC! Not sure why, but thought I’d post this in case it helps someone else.