Unknown message type received

AlexanderTurnowsky commented 6 months ago

System Health details

System Information

version	core-2024.5.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.2
os_name	Linux
os_version	6.6.29-haos
arch	x86_64
timezone	Europe/Vienna
config_dir	/config

Home Assistant Community Store

Home Assistant Cloud

Home Assistant Supervisor

Dashboards

Recorder

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue

i see the following warning: 2024-05-27 11:34:59.815 WARNING (MainThread) [custom_components.deltadore_tydom] Unknown message type received 2024-05-27 11:43:15.281 WARNING (MainThread) [custom_components.deltadore_tydom] Unknown message type received {"mode": "STOP", "support": ["STOP", "HEATING"]} 2024-05-27 11:44:59.816 WARNING (MainThread) [custom_components.deltadore_tydom] Unknown message type received 2024-05-27 11:48:02.804 WARNING (MainThread) [custom_components.deltadore_tydom] Unknown message type received {"productName": "TYDOM HOME", "mac": "xxxxxxxxxxx", "config": "prod", "bddEmpty": false, "bddStatus": 0, "apiMode": true, "mainVersionSW": "03.16.14", "mainVersionHW": "00.00.01", "mainId": "6700116", "mainReference": "25170010", "keyVersionSW": "01.08.04", "zigbeeVersionSW": "01.01.00", "keyVersionHW": "00.00.01", "keyVersionStack": "04.02.06", "keyReference": "25170020", "zigbeeReference": "25170030", "oryxVersion": "2.1.8-10.02", "bootReference": "P25170011", "bootVersion": "01.00.10", "TYDOM.dat": 0, "config.json": 0, "mom.json": 0, "gateway.dat": 0, "bdd.json": 11, "collect.json": 32, "groups.json": 10, "mom_api.json": 0, "scenario.json": 0, "site.json": 46, "bdd_mig.json": 0, "info_mig.json": 0, "info_col.json": 1, "absence.json": 0, "anticip.json": 0, "trigger.json": 0, "bioclim.json": 0, "data_config.json": 2, "urlMediation": "mediation.tydom.com", "pltRegistered": true, "updateAvailable": false, "passwordEmpty": false, "maintenance": {"id": "ffffffffffffffffffffffffffffffff"}, "geoloc": {"longitude": 16583383, "latitude": 48181271}, "clock": {"clock": "2024-05-27T11:47:57+02:00", "source": "ntp", "timezone": 60, "summerOffset": "ON"}, "moments": {"suspend": {"to": 0}}, "local_claim": {"status": "CLOSE", "lastAccess": "2014-01-01T00:04:12Z"}, "weather": {"outTempSrc": {"devId": null, "epId": null}, "weatherSrc": {"devId": null, "epId": null}}, "protocols": [{"protocol": "X3D", "available": true, "installed": true, "ready": true, "status": "running", "installStatus": "idle"}, {"protocol": "ZIGBEE", "available": true, "installed": true, "ready": true, "status": "running", "installStatus": "idle"}, {"protocol": "X3DV", "available": false}, {"protocol": "PltService", "available": false}, {"protocol": "HTTP", "available": true, "installed": true, "ready": true, "status": "running", "installStatus": "idle"}]}

Reproduction steps

1.go to my Thermostat X3D 2.turn off heating 3.this warning is displayed

in the tydom home App the heating is turned off, but on HA the heating is still enabled and active

FYI: i deleted my macaddress in the log

Debug logs

Diagnostics dump

No response

CyrilP commented 6 months ago

Hello, the message {"mode": "STOP", "support": ["STOP", "HEATING"]} is probably an event message which is not handled by the integration because it wasn't needed yet but it can be improved.

for the heating status, can you please :

set the integration in debug mode
restart home assistant
turn off debug mode on the integration
get the logs and send them to me (redact username/password/macaddress if needed)

AlexanderTurnowsky commented 6 months ago

great, yes i will do it, with both start and stop heating, give 1-2 days to provide you with logs.

AlexanderTurnowsky commented 5 months ago

sorry it took longer but here is the debug log now. I strated heating via the X3D, turned it off afterwards and after a while also turned the heating off in HA (as it was not updated). home-assistant_deltadore_tydom_2024-06-06T08-10-57.186Z.log

If more logging is needed i can do more.

CyrilP commented 5 months ago

I've just published a new test release with a refresh of the values when an event is receives. can you give it a try ? the pre-release is called : v0.11-alpha

AlexanderTurnowsky commented 5 months ago

ok here is now the actual test with 0.11: 12: 57 turned the heating on --> with 25C --> all is in HA --> OK 12:58 changed the heating to 21C --> all is in HA --> OK 12:59 turned it off --> will not be updated in HA waited 2min still no update 13:01 turned it off via HA

attached to debug log home-assistant_deltadore_tydom_2024-06-10T11-01-25.320Z.log

CyrilP commented 5 months ago

I see why it doesn't show it off. the code expects hvacMode to be OFF but only thermicLevel is set to OFF. Climate entity is giving me headache with all the different hardware behaving differently. I'll try to fix that

CyrilP / hass-deltadore-tydom-component