search

ridiekel / jeletask

An open source java API for Teletask domotics (https://www.teletask.be/).
https://github.com/ridiekel/jeletask
GNU General Public License v3.0
5 stars 4 forks source link

home assistant auto discovery #1

Closed bertca closed 2 years ago

bertca commented 2 years ago

Hi, First of all a big thank you for making it possible to implement Teletask in Home Assistant. I'm figuring out on how to implement your jeletask package on my environment. I have a Raspberry Pi with Home Assistant OS (and my MQTT broker) on it. So I can't install your docker package on this one. But my NAS helped me out to get docker and your package up and running. Step by step I managed to get things working (not bad for a newby). I'm now in the phase of adding Teletask stuff as MQTT devices to my Home Assistant. Autodiscovery does not seem to work (or I'm doing something wrong here). But I managed to add my lights manually with a MQTT publish command (via a HA script - see below). So far so good... Now I'm trying to add my dimmer-lights via the same way. But this is not working. I can add them as a light, but without dimming function. As you stated that autodiscovery for dimmers should be working, I was wondering if you could help me with the correct publish command to get them as a device in HA.

Once my dimmers are done, I would like to proceed to the next groups. I suppose that motors will be the similar as dimmers? And for flags, locmoods, ... I can use a switch?

Thanks for your help, but even more for this nice package...

Bert

create_light: alias: 'create light' sequence: service: mqtt.publish data: topic: "teletask2mqtt/light/tt/relay_1/config" retain: true payload: > { "device": { "identifiers": [ "Teletask" ], "manufacturer": "Teletask", "name": "Teletask", "model": "Micros Plus" }, "~": "teletask2mqtt/tt/relay/1", "state_topic": "~/state", "unique_id": "tt-relay-1", "name": "Licht Kelder", "command_topic": "~/set" }

claesmathias commented 2 years ago

Hi, try to restart the jeletask container when the mqqt plugin is installed and running on home assistant. Autodiscovery will do it’s magic 🙂

From: bertca @.> Sent: Wednesday, March 16, 2022 10:27:02 AM To: ridiekel/jeletask @.> Cc: Subscribed @.***> Subject: [ridiekel/jeletask] home assistant auto discovery (Issue #1)

Hi, First of all a big thank you for making it possible to implement Teletask in Home Assistant. I'm figuring out on how to implement your jeletask package on my environment. I have a Raspberry Pi with Home Assistant OS (and my MQTT broker) on it. So I can't install your docker package on this one. But my NAS helped me out to get docker and your package up and running. Step by step I managed to get things working (not bad for a newby). I'm now in the phase of adding Teletask stuff as MQTT devices to my Home Assistant. Autodiscovery does not seem to work (or I'm doing something wrong here). But I managed to add my lights manually with a MQTT publish command (via a HA script - see below). So far so good... Now I'm trying to add my dimmer-lights via the same way. But this is not working. I can add them as a light, but without dimming function. As you stated that autodiscovery for dimmers should be working, I was wondering if you could help me with the correct publish command to get them as a device in HA.

Once my dimmers are done, I would like to proceed to the next groups. I suppose that motors will be the similar as dimmers? And for flags, locmoods, ... I can use a switch?

Thanks for your help, but even more for this nice package...

Bert

create_light: alias: 'create light' sequence: service: mqtt.publish data: topic: "teletask2mqtt/light/tt/relay_1/config" retain: true payload: > { "device": { "identifiers": [ "Teletask" ], "manufacturer": "Teletask", "name": "Teletask", "model": "Micros Plus" }, "": "teletask2mqtt/tt/relay/1", "state_topic": "/state", "unique_id": "tt-relay-1", "name": "Licht Kelder", "command_topic": "~/set" }

— Reply to this email directly, view it on GitHubhttps://github.com/ridiekel/jeletask/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIXARCJH7FN7FNJXN6EYCTVAGSONANCNFSM5Q3IEKFQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.Message ID: @.***>

bertca commented 2 years ago

Mathias, Done that (several times) - no luck. That's why I'm asking for a mqtt.publish command...

Bert

ridiekel commented 2 years ago

The auto discovery should do it's work when starting the application. HA needs to be online when starting the container.

You can enable additional loggin by adding and setting these environment variables to true: TELETASK_LOG_HACONFIG_ENABLED and TELETASK_LOG_TOPIC_ENABLED

Can you send your logs after setting these variables? Also, please send a screenshot (or list) of your env variables of the teletask2mqtt docker (or docker-compose file if you have used docker-compose) and the mqtt config of your HA mqtt integration. Remove passwords if you have those :-)

bertca commented 2 years ago

Hi Ridiekel, See some attachments with my settings/log... Just to clear things out: my docker is running on a NAS, my HA on a raspberry Pi.

  1. docker settings
  2. configuration.yaml
  3. docker logfile

docker_settings configuration_yaml dockerlog1 dockerlog2 dockerlog3

bertca commented 2 years ago

I'm also looking to the mqtt traffic on my PC via MQQT Explorer. I can see the teletask2mqtt messages, but there is nothing about homeassistant messages - which i expect to be the 'config' messages.

bertca commented 2 years ago

As we say in Flanders: 'Ik kan onder de grond kruipen van schaamte'. My apologies to all of you. I found what was going wrong... Apparently I did not have the latest version of the package - don't ask me why. Shame on me. The only thing covering me is that I'm still not familiar with all this docker/mqtt/... stuff. Newby, but learning.

As I see now how easy things work... it would really be nice if there was some autodiscovery for the motors too (and sensors, and ...) But I'm already happy with this...

Thanks, thanks, thanks...

VNDCK commented 2 years ago

As we say in Flanders: 'Ik kan onder de grond kruipen van schaamte'. My apologies to all of you. I found what was going wrong... Apparently I did not have the latest version of the package - don't ask me why. Shame on me. The only thing covering me is that I'm still not familiar with all this docker/mqtt/... stuff. Newby, but learning.

As I see now how easy things work... it would really be nice if there was some autodiscovery for the motors too (and sensors, and ...) But I'm already happy with this...

Thanks, thanks, thanks...

Do you know if it's possible to get the temperature from a TDS Touch?

SanderM2 commented 2 years ago

Does the TDS Touch have a temperature sensor? If it does, it should be visible under Diagnostics>Analog Inputs in Prosoft

SanderM2 commented 2 years ago

@VNDCK : if it has an integrated temperature sensor you can configure it in your config.json under SENSORS and set type to "TEMPERATURE"

@ridiekel : I think all issues addresses here are already fixed in the last release. This issue can probably closed now.

ridiekel commented 2 years ago

Fixed since 4.1.1

bertca commented 2 years ago

Hi Ridiekel,

Many, many, many thanks for the effort you did. As my Raspberry Pi (or at least the SD card) shows some hickups, I’m starting to move to my installation to an old NUC. As soon as I get that up and running, I will be able to test/use you new version.

Bert

From: ridiekel @.> Sent: maandag 10 oktober 2022 9:13 To: ridiekel/jeletask @.> Cc: bertca @.>; Author @.> Subject: Re: [ridiekel/jeletask] home assistant auto discovery (Issue #1)

Fixed since 4.1.1

— Reply to this email directly, view it on GitHub https://github.com/ridiekel/jeletask/issues/1#issuecomment-1272872231 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATBYHW7YCM6KIJLUFETYBFLWCO6WLANCNFSM5Q3IEKFQ . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ATBYHW4FACHEJLDJMACWRMTWCO6WLA5CNFSM5Q3IEKF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJPPH2JY.gif Message ID: @. @.> >

ridiekel commented 2 years ago

@bertca Credit where credit is due, these changes have all been done by @SanderM2. Without his work it would have taken a lot longer!

I just think it's great to see this project having more users and contributers now!