https://sourceforge.net/p/max-home-automation/tickets/2022-01-29T18:26:22.993000ZRecent changes to tickets2022-01-29T18:26:22.993000Z2022-01-29T18:26:22.993000Zdmitry-kazakovhttps://sourceforge.net/u/dmitry-kazakov/https://sourceforge.net70763a92016e0472acb1dbd3c1748b6acfdfcf8a

<div class="markdown_content"><p>Let me know if you find any problems.</p></div>

2022-01-29T17:41:55.714000Z2022-01-29T17:41:55.714000ZL.W.https://sourceforge.net/u/lrswss/https://sourceforge.net26b74d164727f830366c7afe83700e7b7e6aac3d

<div class="markdown_content"><p>MQTT is working fine (with 4.0): I can see all thermostats with MQTT-Explorer. I also managed to include the themostats as climate entities into Home Assistant. I guess you can close the ticket. Thanks for your help!</p> <p>max_home_automation is now running headless on a Raspi2 with xvfb and x11vnc. I'll try to update to 4.1. soon. Next step is to control the thermostats with HA automations...</p></div>

2022-01-29T13:44:17.480000Z2022-01-29T13:44:17.480000Zdmitry-kazakovhttps://sourceforge.net/u/dmitry-kazakov/https://sourceforge.netf9695eb3aca0b74ceefd059a6f6b064c918272ac

<div class="markdown_content"><ul> <li><strong>labels</strong>: --&gt; 4.1</li> </ul></div>

2022-01-29T13:43:33.192000Z2022-01-29T13:43:33.192000Zdmitry-kazakovhttps://sourceforge.net/u/dmitry-kazakov/https://sourceforge.netada8b43799837c9ab8b38aecf40fb3fd1c096988

<div class="markdown_content"><ul> <li><strong>labels</strong>: --&gt; 4.1</li> <li><strong>status</strong>: open --&gt; closed</li> </ul></div>

2022-01-28T18:04:39.079000Z2022-01-28T18:04:39.079000Zdmitry-kazakovhttps://sourceforge.net/u/dmitry-kazakov/https://sourceforge.net2ac73abc94c070b167ae974cbc81282bc89a7e60

<div class="markdown_content"><p>When nothing changes then nothing gets published. You can change, for example, the thermostat's mode from automatic to manual. And see the change. As a rule a radiator thermostats never sends the actual temperature unless the valve position is changed. So there is little to publish.</p> <p>BTW, MQTT Explorer is much more comfortable to use than mosquitto. You can browse the available topics interactively etc.</p> <p>If you enable MQTT tracing you will see full exchange with the client in the trace. Trace into a file, it is easier to analyze then.</p></div>

2022-01-28T17:32:56.703000Z2022-01-28T17:32:56.703000ZL.W.https://sourceforge.net/u/lrswss/https://sourceforge.net4fb7389e7cf1bef3e4f44a9446d752ee6bd2e2c6

<div class="markdown_content"><p>It's not a matter of publishing to topics. Currently I'm just trying to subscribe to a (themostat) topic to see its status data. And no matter what topic I'm trying mosquitto_sub just stays quiet. Is there a specific topic that should publish a message within let's say every 2-3 min?</p></div>

2022-01-28T10:29:45.556000Z2022-01-28T10:29:45.556000Zdmitry-kazakovhttps://sourceforge.net/u/dmitry-kazakov/https://sourceforge.netc672d416e31eb3a7d57d5c3c18ce7bfb4c09b62d

<div class="markdown_content"><ol> <li>If you want to publish on the server you must enable MQTT publishing on the settings tab. You can furthermore specify the list of topics allowed for external publishing.</li> <li>Regarding wildcard topic subscriptions, that is a bug fixed in the incoming version 4.1.</li> </ol></div>

2022-01-28T00:13:30.458000Z2022-01-28T00:13:30.458000ZL.W.https://sourceforge.net/u/lrswss/https://sourceforge.net3c192c79b475d8562f38f7c7f2b6a6abe2c05244

<div class="markdown_content"><p>Hi Dmitry,</p> <p>Originally looking for a MQTT to eQ3 bridge I came across your wonderful peace of software. Finally I can rid of the original, buggy and no longer maintained software from eQ3 and switch all configuration tasks to Linux!</p> <p>I just installed v4.0 on a Raspberry Pi running Debian Bullseye for testing. I can connect to my cube and list all devices and modify their settings. However the build in MQTT server doesn't seem to publish any data. I can subscribe to the wildcard topic '#', but don't see any status data. I also tried using the cube address as prefix '180BCC/#' or specific topics listed in the documentation, to no avail. Looking a the trace tab I noticed the repeating error message "Processing sent notification fault: raised CONSTRAINT_ERROR : object-handle-generic_set.adb:309 explicit raise" as soon as I connect to port 1883 with "mosquitto_sub -t '#' -v". Am I doing something wrong?</p> <p>Regards<br/> Lars</p></div>

2022-01-28T00:13:30.458000Z2022-01-28T00:13:30.458000ZL.W.https://sourceforge.net/u/lrswss/https://sourceforge.netedbe834d7febfec3b6e48ddf272f4ffa88979663

<div class="markdown_content"><p>Ticket 2 has been modified: MQTT not working<br/> Edited By: dmitry-kazakov (dmitry-kazakov)</p></div>

2022-01-28T00:13:30.458000Z2022-01-28T00:13:30.458000ZL.W.https://sourceforge.net/u/lrswss/https://sourceforge.netce98e70af7439f142b9e70d9c9a82f4dab771e7e

<div class="markdown_content"><p>Ticket 2 has been modified: MQTT not working<br/> Edited By: dmitry-kazakov (dmitry-kazakov)<br/> Status updated: 'open' =&gt; 'closed'</p></div>