![]() |
|
New Comfort2MQTT for Home Assistant - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html) +--- Forum: Comfort with Home Assistant (https://www.comfortforums.com/forum-143.html) +--- Thread: New Comfort2MQTT for Home Assistant (/thread-5511.html) |
- Ingo - 09-02-2024 Hi All, I decided to take the great work done by @koochyrat and others and update the scripts to integrate a bit more with Home Assistant. https://github.com/djagerif/comfort2mqtt A quick disclaimer: I am not a programmer, I tinker a lot, so please don\'t be too critical of this HA Addon. I do have a day job so time, and skill, to figure things out and trying to make it work is limited. Feel free to test and comment and if there is something that is broken, and I am able to fix it, then I will give it my best shot. Development was done on an old CM9000-ULT with a Cbus integration. Anything else is a best-effort bonus that I can\'t test or develop for. The documentation is extensive, I tried to put EVERYTHING in there so if you don\'t understand something, please read the docs again, it should be in there somewhere. You will need to configure your own flags, sensors, counters, zones etc. I only programmed a few system objects as a start. Ingo - Ingo - 09-03-2024 Thanks Chiu. Unfortunately my images are not hosted anywhere as they are local to my PC so can\'t be posted by a quick paste. I will add them as files. - Ingo - 09-03-2024 Image. - Ingo - 09-03-2024 Image - Ingo - 09-03-2024 Image ![]() - Howser - 09-04-2024 Looks interesting. I have gone UcmPi (in NodeRed) to MQTT (home assistant) and SHAC to MQTT (home assistant) with two way control. - clivesanders - 10-22-2024 Hi @Ingo Great piece of work! I have Just loaded this on my system and it works great I get only one error pop up have copied below I dont think it is my config but may be. I have been using the Koochyrat implementation on a seperate server fom HA for many years and have always wanted to fully integrate with HA but did not have the abilities you do! Was looking at the @posixx version yesterday and fell foul of the paho-mqtt v2.0.0 incompatibility issues. By chance saw your work and reconfiguered my MQTT sensors and all is good. THANK YOU!!Rgds Clive Traceback (most recent call last): File \"/comfort2/comfort2.py\", line 2877, in <module> mqttc.run() File \"/comfort2/comfort2.py\", line 2443, in run self.publish(ALARMSTATUSTOPIC, SMsg.modename,qos=2,retain=True) # Idle, Alert etc. ^^^^^^^^^^^^^ AttributeError: \'ComfortS_SecurityModeReport\' object has no attribute \'modename\'[/code] - Ingo - 10-22-2024 Hi Clive. I think it is receiving some output of \"S?\" that is not expected. Please send me the output of the S? command and also what model and firmware you are using. Set the logging to debug as this will log all command values, especially the ones just before it throws an exception. The documentation states only 00 - 03 as return values. Ingo - clivesanders - 10-22-2024 Hi Ingo, appreciate you getting back to me. Here is the log file rgds Clive 2024-10-23 00:07:11 DEBUG r?00F00F000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:27 DEBUG ER00 2024-10-23 00:08:27 INFO Ready To Arm... 2024-10-23 00:08:27 DEBUG SM000140 2024-10-23 00:08:27 DEBUG EX0205 2024-10-23 00:08:27 DEBUG SM000140 2024-10-23 00:08:31 DEBUG PS00 2024-10-23 00:08:31 DEBUG SM000040 2024-10-23 00:08:31 DEBUG SM000140 2024-10-23 00:08:32 DEBUG MD0203 2024-10-23 00:08:32 INFO Armed Night Mode 2024-10-23 00:08:32 DEBUG AM0903 2024-10-23 00:08:32 DEBUG KL01000000 2024-10-23 00:08:32 DEBUG S?13 Traceback (most recent call last): File \"/comfort2/comfort2.py\", line 2877, in <module> mqttc.run() File \"/comfort2/comfort2.py\", line 2443, in run self.publish(ALARMSTATUSTOPIC, SMsg.modename,qos=2,retain=True) # Idle, Alert etc. ^^^^^^^^^^^^^ AttributeError: \'ComfortS_SecurityModeReport\' object has no attribute \'modename\' [23:08:32] WARNING: Halt add-on with exit code 1 s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun comfort2mqtt (no readiness notification) s6-rc: info: service legacy-services successfully started [00:08:36] WARNING: TLS encryption option disabled. [00:08:36] INFO: Starting Comfort to MQTT... 2024-10-23 00:08:36 DEBUG Starting new HTTP connection (1): supervisor:80 2024-10-23 00:08:36 DEBUG http://supervisor:80 \"GET /addons/self/info HTTP/11\" 200 9727 2024-10-23 00:08:36 INFO Importing the add-on configuration options 2024-10-23 00:08:36 INFO Completed importing addon configuration options 2024-10-23 00:08:36 DEBUG The following variable values were passed through via the Home Assistant 2024-10-23 00:08:36 DEBUG MQTT_USER = mqttbroker 2024-10-23 00:08:36 DEBUG MQTT_PASSWORD = ****** 2024-10-23 00:08:36 DEBUG MQTT_SERVER = 172.30.33.9 2024-10-23 00:08:36 DEBUG MQTT_PROTOCOL = TCP/1883 (Unsecure) 2024-10-23 00:08:36 DEBUG COMFORT_ADDRESS = 192.168.1.77 2024-10-23 00:08:36 DEBUG COMFORT_PORT = 1001 2024-10-23 00:08:36 DEBUG COMFORT_LOGIN_ID = ****** 2024-10-23 00:08:36 DEBUG COMFORT_CCLX_FILE = 13MeadowCt_2018_v1.3_DRdis_DSdis.cclx 2024-10-23 00:08:36 DEBUG MQTT_CA_CERT = ca.crt 2024-10-23 00:08:36 DEBUG MQTT_CLIENT_CERT = client.crt 2024-10-23 00:08:36 DEBUG MQTT_CLIENT_KEY = client.key 2024-10-23 00:08:36 DEBUG MQTT_LOG_LEVEL = DEBUG 2024-10-23 00:08:36 DEBUG COMFORT_TIME= False 2024-10-23 00:08:36 WARNING MQTT Transport Layer Security disabled. 2024-10-23 00:08:36 INFO Comfigurator (CCLX) File detected, 236514 Bytes 2024-10-23 00:08:36 INFO Connecting to Comfort (192.168.1.77) on port 1001 2024-10-23 00:08:36 INFO MQTT Broker Connection Success 2024-10-23 00:08:36 DEBUG Subscribed to 16 Zone Outputs 2024-10-23 00:08:36 DEBUG Subscribed to 32 Zone Inputs 2024-10-23 00:08:36 DEBUG Subscribed to 0 RIO Outputs 2024-10-23 00:08:36 DEBUG Subscribed to 254 Flags 2024-10-23 00:08:36 DEBUG Subscribed to 32 Sensors 2024-10-23 00:08:36 DEBUG LU03 2024-10-23 00:08:36 INFO Comfort Login Ok - User 3 2024-10-23 00:08:36 DEBUG Subscribed to 255 Counters 2024-10-23 00:08:36 DEBUG Subscribed to 0 Responses 2024-10-23 00:08:36 DEBUG Synchronizing Comfort Data... 2024-10-23 00:08:36 DEBUG Synchronization Done. 2024-10-23 00:08:41 DEBUG b?00000000000000000000000000 2024-10-23 00:08:41 DEBUG Zones Bypassed: 0 2024-10-23 00:08:41 DEBUG V?FE078C22400100 2024-10-23 00:08:42 INFO Comfort II ULTRA detected (Firmware 7.140) 2024-10-23 00:08:42 DEBUG EL1111FFFFFFFF 2024-10-23 00:08:42 DEBUG 1 Installed SEM(s) detected 2024-10-23 00:08:42 DEBUG Hardware Model CM9000-ULT 2024-10-23 00:08:43 DEBUG DL7FF9045C172F00E2 2024-10-23 00:08:43 DEBUG SN015C172F00 2024-10-23 00:08:43 INFO Refresh Key: 5C172F00 2024-10-23 00:08:43 INFO Serial Number: C086172 2024-10-23 00:08:45 DEBUG M?0203 2024-10-23 00:08:45 INFO Armed Night Mode 2024-10-23 00:08:45 DEBUG Z?00000000 2024-10-23 00:08:45 DEBUG Max. Reported Zones/Inputs: 32 2024-10-23 00:08:45 DEBUG z?000000000000000000000000000000 2024-10-23 00:08:46 DEBUG Max. Reported SCS/RIO Inputs: 120 2024-10-23 00:08:46 DEBUG Y?0E010000 2024-10-23 00:08:46 DEBUG Max. Reported Outputs: 32 2024-10-23 00:08:46 DEBUG y?000000000000000000000000000000 2024-10-23 00:08:48 DEBUG Max. Reported SCS/RIO Outputs: 120 2024-10-23 00:08:48 DEBUG f?00F9FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 2024-10-23 00:08:50 DEBUG S?00 2024-10-23 00:08:50 DEBUG a?130000000000000000 2024-10-23 00:08:50 DEBUG r?0100100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?0110100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?000010FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?0010100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?0020100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?0030100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:51 DEBUG r?0040100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?0050100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?0060100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?0070100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?0080100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?0090100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:52 DEBUG r?00A0100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:53 DEBUG r?00B0100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:53 DEBUG r?00C0100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:53 DEBUG r?00D0100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:53 DEBUG r?00E0100000000000000000000000000000000000000000000000000000000000000000 2024-10-23 00:08:53 DEBUG r?00F00F000000000000000000000000000000000000000000000000000000000000 - Ingo - 10-23-2024 Yes, this is the culprit, I\'ll have to investigate this as it\'s undocumented. 2024-10-23 00:08:32 DEBUG S?13 I do however notice that you are running a firmware version that is quite old and not tested. I suggest upgrading the firmware to either the latest, or to at least one that has been tested against this Add-on. The minimum is 7.201 if I remember correctly but I personally run the latest 8.013 released earlier this week. |