quazzie / tellstick-plugin-mqtt-hass Goto Github PK

Plugin for tellstick, connect to homeassistant via mqtt with autodiscovery.

Python 100.00%

tellstick-znet home-assistant mqtt autodiscovery

tellstick-plugin-mqtt-hass's Introduction

TellStick mqtt-plugin for HomeAssistant

Plugin for TellStick Znet v2 to support MQTT push/subscribe, enables Home Assistant integration via mqtt autodiscovery.

Usage instruction

This plugin is intended to be installed on a TellStick Znet v2.

In order to have support for local plugins you must contact Telldus Support, via http://support.telldus.com.

Open a support request stating that you like an updated Firmware with support for local plugins and ask for the supported developer [email protected] with the pubic key below.

Once the support request is accepted log in to your TellStick Znet v2 (http://tellstick.local) using your Telldus Live credentials. When logged in go to Plugins (beta) and from that click Manual upload (:arrow_up:) and upload the downloaded package (from https://github.com/quazzie/tellstick-plugin-mqtt-hass/releases).

Reboot after install

Configure the plugin with your mqtt settings and if your Home Assistant is configured to support auto discovery via mqtt the devices connected to your TellStick will automatically show up in Home Assistant.

Support / thanks

Help support or thank me:

tellstick-plugin-mqtt-hass's People

Contributors

Stargazers

Watchers

Forkers

fcorin fredrike krille01 allotria henjoa crashmatt beredix

tellstick-plugin-mqtt-hass's Issues

State changes not published

Hi,

I've successfully installed your plugin (version 0.82) on my Telldus Znet Lite v2 after having Telldus install you GPG key.

I've set up the MQTT parameters and confirmed, by using mosquitto_sub, that the Znet does publish the list of devices connected to the Znet. The devices are even automagically discovered by Home Assistant. So far, so good.

However, the plugin does not publish state changes for the devices. If, for example, I push a button on a 433 MHz remote, the Znet registers this and I can see the change in an HA entity that fetches its state from the Telldus Live HA-integration, but a corresponding MQTT message is never published.

I might be doing something wrong or misunderstanding the plugin's use (wouldn't be the first time).

I'd appreciate it if you could give me a pointer to what I might have missed.

Best regards,

Unable to access tellstick.local

Hey, after Telldus changed everything this autumn, I seem to be unable to login locally.
I have contacted the devs with the public key, and got it added to my Telldus account.
But when trying to access tellstick.local, I get to the Telldus login page, but when entering my credentials I face the attached image.

Any ideas on how I can upload the plugin given this situation? Or do you need a premium account to do that?

Only sends on off basic commands not dimm to history

Don't send dimm commands please can't run automation based on manual on commands on dimmer.

#27
#10

Battery sensor entity not renamed

Hi,

Yesterday I renamed one of my sensors in Telldus Live.
This one repports Temperature/Humidity/Battery.

While temperature and humidity got renamed properly in Home Assistant, the battery sensor still has the old name/entity id.
Any idea how to solve that without renaming manually in Home Assistant?

Example old name in Telldus Live:
Vardagsrum
Gave following entities in Home Assistant:
sensor.vardagsrum_humidity
sensor.vardagsrum_temp_degc
sensor.vardagsrum_battery

After renaming and reboot of Tellstick and Home Assistant:
New name in Telldus Live:
Sovrum
Gave following entities in Home Assistant:
sensor.sovrum_humidity
sensor.sovrum_temp_degc
sensor.vardagsrum_battery

I'm using Pre-release: 0.86

Best regards

Z wave motion sensor is not shown

I have a z-wave motion/temp and light sensor, I see the binary temp and light sensors but the motion switch don't show.

FIBARO MOTION SENSOR
FGMS-001-EN-A-V1.02

Is it a topic issue?

Should not remove devices when mqtt is restarted

I'm having really strange behaviour and can't decide if it is on HA side or on the Tellstick side.

Basically it goes like this. I have a temp-device that I have renamed the ID on (which is fine as entities are stored in the entity-registry). But when my mqtt broker restarts this tellstick-plugin removes all devices and eventually (when the sensors publish their first value) adds them again.

According to the HA mqtt discovery doc:

An empty payload will cause a previously discovered device to be deleted.

And this is done way too frequent.

To be honest I think that devices only should be removed from HA (published with empty topic) if they are removed from the Telldus Live portal. In all other instances the device should stay.

One might argue that HA should keep devices in the registry (even if they are deleted) but that is apparently not the case (anymore, I think the registry never removed entities before but I've not taken the time to dig this up).

Anyway, it would be great if we could stop calling self.remove_discovery() except when a device actually is removed.

This is part of my log..

home/sensor/TellstickZnetLite/6_2_0/state {"lastUpdated": 1587451606, "value": "38"}                                                                                                                                                   
telldus/TellstickZnetLite/debug 06:49:58 - remove discovered device sensor,6,6_2_0 : home/sensor/TellstickZnetLite/6_2_0                                                                                                               
home/sensor/TellstickZnetLite/6_2_0/config (null)                                                                                                                                                                                      
home/sensor/TellstickZnetLite/6_2_0/state (null)                                                                                                                                                                                       
telldus/TellstickZnetLite/debug 06:50:01 - A wild sensor appeared! deviceId: 6, sensorId: 6_2_0                                                                                                                                        
home/sensor/TellstickZnetLite/6_2_0/config {"unit_of_measurement": "%", "device": {"model": "Temperaturehumidity", "identifiers": "207aacf7-092b-4afa-a092-068875893b99", "via_device": "ACCA5401B5EA", "name": "Vit Inne", "manufactur
er": "Mandolyn"}, "json_attributes_topic": "home/sensor/TellstickZnetLite/6_2_0/state", "name": "Vit Inne humidity - %", "device_class": "humidity", "state_topic": "home/sensor/TellstickZnetLite/6_2_0/state", "value_template": "{{ 
value_json.value }}", "availability_topic": "telldus/TellstickZnetLite/available", "unique_id": "ACCA5401B5EA_6_2_0"}                                                                                                                  
telldus/TellstickZnetLite/debug 06:50:01 - Updating config.devices_configured to : [('hub', 'hub', 'hub'), ('switch', '19', '19'), ('switch', '20', '20'), ('switch', '21', '21'), ('switch', '22', '22'), ('switch', '23', '23'), ('sw
itch', '24', '24'), ('switch', '25', '25'), ('sensor', '71', '71_1_0'), ('sensor', '71', '71_2_0'), ('switch', '103', '103'), ('sensor', '121', '121_1_0'), ('sensor', '121', '121_2_0'), ('sensor', '134', '134_1_0'), ('sensor', '134
', '134_2_0'), ('sensor', '178', '178_1_0'), ('sensor', '178', '178_2_0'), ('switch', '200', '200'), ('sensor', '201', '201_1_0'), ('sensor', '201', '201_2_0'), ('sensor', '11', '11_1_0'), ('light', '18', '18'), ('sensor', '1', '1_
256_2'), ('sensor', '1', '1_256_3'), ('sensor', '1', '1_256_0'), ('light', '1', '1'), ('sensor', '2', '2_256_2'), ('sensor', '2', '2_256_0'), ('sensor', '2', '2_256_6'), ('sensor', '2', '2_256_3'), ('light', '2', '2'), ('sensor', '
98', '98_1_0'), ('sensor', '98', '98_2_0'), ('sensor', '102', '102_1_0'), ('sensor', '6', '6_1_0'), ('sensor', '6', '6_2_0')]

Config messages are (re-) published on LAN/WAN being reestablished

I'm not sure this is a bug or even undesired, but I thought I'd put the question out there:

Yesterday, I first rebooted my internet modem and later in the evening my router.

On both occassions, I noticed that automations that trigger on state changes for MQTT entities (from the Telldus Znet Lite v2) triggered. I have a few Nexa 433 MHz remotes that I use to trigger automations (switching lights on and off), and I rely on the expire_after feature for that. I found that after LAN/WAN has been reestablished, all config messages are republished.

When the config messages are published, the MQTT entities in HA go from unavailable to whatever status the remote has in the Telldus hub (so if the last button push on the remote was OFF, the entity's state in HA goes from unavailable to OFF). Or maybe it goes from unavailable to the last available state in HA instead of the current state in the Telldus hub - but the two should be the same. Either way, going from unavailable to a state triggers the automation.

Furthermore, the entity's state in HA does not expire after going from unavailable to a state after a config message has been issued. This is a HA problem. I've raised HA issue #28634, but I have not got any response.

Anyway, back to the republishing of config messages: Is this a desired behavior?

No support for long term statistics in HA

Hi,

Is it possible to add long term statistics in HA?
https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

No updates frpn Telldus Lite V2

I've been using this fast plugin for some time, but it stopped working a couple of weeks ago. In Home Assistant all sensors, and lights and switches were "Unavailable". I tried to uninstall and install the newest plugin, but I only get a binarary sensor that is showing that it's offline. I get nothing from the devices and sensors that I have in Telldus. Do you have any suggestions?

Scan interval for MQTT polling against Tellstick?

Have tried the plugin for a few days and must say that it works really well.

What bothers me (and by me I mean my significant other) is the respons time. From switching of a single light theres a latency around 1-2 seconds. If toggling a group of multiple lights and switches there might be a delay up to 10 seconds before the interface changes state for the group icon.

This results in the user presses the switch/light/group toggle again before all lights/switches are off and unintentionally trigger the switch/light/group again.

Is there a way to make HA act as of the switch etc is of as soon as it is pressed or solve the problem above some other way?

Climate devices are stopped working again in the releases 0.84 to 0.86

Originally posted by @quazzie in #8 (comment)

Hi!

Thank you for all the great work with this plugin. I have been using the 0.83b14 beta version since February and it has been working very well with a single exception. That is a Heatit z‑trm2fx thermostat for the bathroom floor heating. The issue with this device is that it generates two subnodes for the z-wave device and one of them is the one which you need to control. Those subdevices are however not presented over MQTT using the plugin even though they are presented through the live.telldus.com interface. Do you think that it would be possible for you to look into adding the support for this? I would be happy to help troubleshoot and test it.

In my quest to solve this I did however discover that the thermostat control is broken in version 0.84 through 0.86. I updated to those versions in the hope that you had added the support for the subnodes. Then all climate devices stopped working. I downgraded to 0.83b14 and they were working again. It appears to be broken in all three published versions since 0.83b14.
Below is the debug output before and after the upgrade:

0.83b14

telldus/znet/debug 15:18:55 - discover devices
telldus/znet/debug 15:18:55 - {"methods": 2048, "battery": 86, "isSensor": true, "deviceId": 55, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601267698, "value": "20.4"}]}, "name": "Vardagsrummet", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {}}, "modes": ["heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}
telldus/znet/debug 15:18:55 - device 55 has battery
telldus/znet/debug 15:18:55 - device 55 is climate
telldus/znet/debug 15:18:55 - climateState 55, sensorValues: {1: [{'scale': 0, 'lastUpdated': 1601267698, 'value': u'20.4'}]}, thermovalues: {u'setpoint': {u'heat': 10.0}, u'mode': u'heat'}, setPoint: 10.0, mode: heat
telldus/znet/debug 15:18:55 - {"methods": 2048, "battery": 81, "isSensor": true, "deviceId": 56, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601260699, "value": "20.4"}]}, "name": "Sovrummet", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {}}, "modes": ["heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}
telldus/znet/debug 15:18:55 - device 56 has battery
telldus/znet/debug 15:18:55 - device 56 is climate
telldus/znet/debug 15:18:55 - climateState 56, sensorValues: {1: [{'scale': 0, 'lastUpdated': 1601260699, 'value': u'20.4'}]}, thermovalues: {u'setpoint': {u'heat': 15.0}, u'mode': u'heat'}, setPoint: 15.0, mode: heat
telldus/znet/debug 15:18:55 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 58, "sensors": {"256": [{"scale": 2, "lastUpdated": 1600510080, "value": "0.0"}]}, "name": "DIN_Matsal", "parameters": {"devicetype": "00000005-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:18:55 - device 58 has sensors
telldus/znet/debug 15:18:55 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1600510080, 'value': u'0.0'}]
telldus/znet/debug 15:18:55 - sensorState {'scale': 2, 'lastUpdated': 1600510080, 'value': u'0.0'}
telldus/znet/debug 15:18:55 - device 58 is a device
telldus/znet/debug 15:18:55 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/58/state", "command_topic": "homeassistant/light/znet/58/set", "schema": "json", "name": "DIN_Matsal", "brightness": true}, "deviceTopic": "homeassistant/light/znet/58", "deviceType": "light"}
telldus/znet/debug 15:18:55 - deviceState 58, state: 2, value: 
telldus/znet/debug 15:18:55 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 59, "sensors": {"256": [{"scale": 2, "lastUpdated": 1598561826, "value": "0.0"}]}, "name": "DIN_Sovrum", "parameters": {"devicetype": "00000005-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:18:55 - device 59 has sensors
telldus/znet/debug 15:18:55 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1598561826, 'value': u'0.0'}]
telldus/znet/debug 15:18:55 - sensorState {'scale': 2, 'lastUpdated': 1598561826, 'value': u'0.0'}
telldus/znet/debug 15:18:55 - device 59 is a device
telldus/znet/debug 15:18:55 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/59/state", "command_topic": "homeassistant/light/znet/59/set", "schema": "json", "name": "DIN_Sovrum", "brightness": true}, "deviceTopic": "homeassistant/light/znet/59", "deviceType": "light"}
telldus/znet/debug 15:18:55 - deviceState 59, state: 2, value: 
telldus/znet/debug 15:18:56 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 75, "sensors": {"256": [{"scale": 2, "lastUpdated": 1594450751, "value": "0.0"}]}, "name": "DIN_Vardagsrum", "parameters": {"devicetype": "00000005-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:18:56 - device 75 has sensors
telldus/znet/debug 15:18:56 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1594450751, 'value': u'0.0'}]
telldus/znet/debug 15:18:56 - sensorState {'scale': 2, 'lastUpdated': 1594450751, 'value': u'0.0'}
telldus/znet/debug 15:18:56 - device 75 is a device
telldus/znet/debug 15:18:56 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/75/state", "command_topic": "homeassistant/light/znet/75/set", "schema": "json", "name": "DIN_Vardagsrum", "brightness": true}, "deviceTopic": "homeassistant/light/znet/75", "deviceType": "light"}
telldus/znet/debug 15:18:56 - deviceState 75, state: 2, value: 
telldus/znet/debug 15:18:56 - {"methods": 2048, "battery": 88, "isSensor": true, "deviceId": 76, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601259748, "value": "20.4"}]}, "name": "Matsalen", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {}}, "modes": ["heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}
telldus/znet/debug 15:18:56 - device 76 has battery
telldus/znet/debug 15:18:56 - device 76 is climate
telldus/znet/debug 15:18:56 - climateState 76, sensorValues: {1: [{'scale': 0, 'lastUpdated': 1601259748, 'value': u'20.4'}]}, thermovalues: {u'setpoint': {u'heat': 14.0}, u'mode': u'heat'}, setPoint: 14.0, mode: heat
telldus/znet/debug 15:18:56 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 77, "sensors": {}, "name": "Brytare", "parameters": {"devicetype": "00000010-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:18:56 - device 77 is a device
telldus/znet/debug 15:18:56 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/77/state", "command_topic": "homeassistant/switch/znet/77/set", "name": "Brytare"}, "deviceTopic": "homeassistant/switch/znet/77", "deviceType": "switch"}
telldus/znet/debug 15:18:56 - deviceState 77, state: 2, value: 
telldus/znet/debug 15:18:56 - {"methods": 2050, "battery": null, "isSensor": true, "deviceId": 88, "sensors": {}, "name": "Golvv\u00e4rme normal", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {"max": 35.0, "min": 5.0}, "eco-heat": {"max": 35.0, "min": 5.0}, "cool": {"max": 35.0, "min": 5.0}}, "modes": ["off", "heat", "cool", "eco-heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}
telldus/znet/debug 15:18:56 - device 88 is climate
telldus/znet/debug 15:18:56 - discoverThermostat 1
telldus/znet/debug 15:18:56 - climateState exception 1
telldus/znet/debug 15:18:56 - {"methods": 2050, "battery": null, "isSensor": false, "deviceId": 89, "sensors": {}, "name": "Golvv\u00e4rme Badrum", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {}, "eco-heat": {}, "cool": {}}, "modes": ["off", "heat", "cool", "eco-heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}
telldus/znet/debug 15:18:56 - device 89 is climate
telldus/znet/debug 15:18:56 - climateState exception 1
telldus/znet/debug 15:18:56 - {"methods": 0, "battery": null, "isSensor": true, "deviceId": 90, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601305944, "value": "20.8"}]}, "name": "Golvv\u00e4rmen", "parameters": {"devicetype": "0000000D-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:18:56 - device 90 has sensors
telldus/znet/debug 15:18:56 - sensortype 1 has [{'scale': 0, 'lastUpdated': 1601305944, 'value': u'20.8'}]
telldus/znet/debug 15:18:56 - sensorState {'scale': 0, 'lastUpdated': 1601305944, 'value': u'20.8'}
telldus/znet/debug 15:18:56 - device 90 is a device
telldus/znet/debug 15:18:56 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/90/state", "name": "Golvv\u00e4rmen"}, "deviceTopic": "homeassistant/binary_sensor/znet/90", "deviceType": "binary_sensor"}
telldus/znet/debug 15:18:56 - deviceState 90, state: 2, value: 
telldus/znet/debug 15:18:56 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 91, "sensors": {}, "name": "Device 91", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:18:56 - device 91 is a device
telldus/znet/debug 15:18:56 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/91/state", "command_topic": "homeassistant/switch/znet/91/set", "name": "Device 91"}, "deviceTopic": "homeassistant/switch/znet/91", "deviceType": "switch"}
telldus/znet/debug 15:18:56 - deviceState 91, state: 1, value: 
telldus/znet/debug 15:18:56 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 92, "sensors": {"256": [{"scale": 0, "lastUpdated": 1601306003, "value": "295.8"}, {"scale": 2, "lastUpdated": 1601305943, "value": "0.0"}, {"scale": 4, "lastUpdated": 1601305944, "value": "233.7"}]}, "name": "Device 92", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:18:56 - device 92 is a device
telldus/znet/debug 15:18:56 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/92/state", "command_topic": "homeassistant/switch/znet/92/set", "name": "Device 92"}, "deviceTopic": "homeassistant/switch/znet/92", "deviceType": "switch"}
telldus/znet/debug 15:18:56 - deviceState 92, state: 2, value: 
telldus/znet/debug 15:18:56 - Updating config.devices_configured to : [('sensor', '55', 'ACCA54013CBC_55_battery'), ('climate', '55', '55'), ('sensor', '56', 'ACCA54013CBC_56_battery'), ('climate', '56', '56'), ('sensor', '58', '58_256_2'), ('light', '58', '58'), ('sensor', '59', '59_256_2'), ('light', '59', '59'), ('sensor', '75', '75_256_2'), ('light', '75', '75'), ('sensor', '76', 'ACCA54013CBC_76_battery'), ('climate', '76', '76'), ('switch', '77', '77'), ('climate', '89', '89'), ('sensor', '90', '90_1_0'), ('binary_sensor', '90', '90'), ('switch', '91', '91'), ('switch', '92', '92')]
telldus/znet/debug 15:18:56 - config updated devices_configured [('sensor', '55', 'ACCA54013CBC_55_battery'), ('climate', '55', '55'), ('sensor', '56', 'ACCA54013CBC_56_battery'), ('climate', '56', '56'), ('sensor', '58', '58_256_2'), ('light', '58', '58'), ('sensor', '59', '59_256_2'), ('light', '59', '59'), ('sensor', '75', '75_256_2'), ('light', '75', '75'), ('sensor', '76', 'ACCA54013CBC_76_battery'), ('climate', '76', '76'), ('switch', '77', '77'), ('climate', '89', '89'), ('sensor', '90', '90_1_0'), ('binary_sensor', '90', '90'), ('switch', '91', '91'), ('switch', '92', '92')]
telldus/znet/debug 15:18:56 - subscribing

0.86

telldus/znet/debug 15:25:21 - discover devices
telldus/znet/debug 15:25:21 - {"methods": 2048, "battery": null, "isSensor": true, "deviceId": 55, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601267698, "value": "20.4"}]}, "name": "Vardagsrummet", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:21 - device 55 has sensors
telldus/znet/debug 15:25:21 - sensortype 1 has [{'scale': 0, 'lastUpdated': 1601267698, 'value': u'20.4'}]
telldus/znet/debug 15:25:21 - sensorState {'scale': 0, 'lastUpdated': 1601267698, 'value': u'20.4'}
telldus/znet/debug 15:25:21 - device 55 is a device
telldus/znet/debug 15:25:21 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/55/state", "name": "Vardagsrummet"}, "deviceTopic": "homeassistant/binary_sensor/znet/55", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:21 - deviceState 55, state: 1, value: 
telldus/znet/debug 15:25:21 - {"methods": 2048, "battery": null, "isSensor": true, "deviceId": 56, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601260699, "value": "20.4"}]}, "name": "Sovrummet", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:21 - device 56 has sensors
telldus/znet/debug 15:25:21 - sensortype 1 has [{'scale': 0, 'lastUpdated': 1601260699, 'value': u'20.4'}]
telldus/znet/debug 15:25:21 - sensorState {'scale': 0, 'lastUpdated': 1601260699, 'value': u'20.4'}
telldus/znet/debug 15:25:21 - device 56 is a device
telldus/znet/debug 15:25:21 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/56/state", "name": "Sovrummet"}, "deviceTopic": "homeassistant/binary_sensor/znet/56", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:21 - deviceState 56, state: 1, value: 
telldus/znet/debug 15:25:21 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 58, "sensors": {"256": [{"scale": 2, "lastUpdated": 1600510080, "value": "0.0"}]}, "name": "DIN_Matsal", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:25:21 - device 58 has sensors
telldus/znet/debug 15:25:21 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1600510080, 'value': u'0.0'}]
telldus/znet/debug 15:25:21 - sensorState {'scale': 2, 'lastUpdated': 1600510080, 'value': u'0.0'}
telldus/znet/debug 15:25:21 - device 58 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/58/state", "command_topic": "homeassistant/light/znet/58/set", "schema": "json", "name": "DIN_Matsal", "brightness": true}, "deviceTopic": "homeassistant/light/znet/58", "deviceType": "light"}
telldus/znet/debug 15:25:22 - deviceState 58, state: 2, value: 
telldus/znet/debug 15:25:22 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 59, "sensors": {"256": [{"scale": 2, "lastUpdated": 1598561826, "value": "0.0"}]}, "name": "DIN_Sovrum", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:25:22 - device 59 has sensors
telldus/znet/debug 15:25:22 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1598561826, 'value': u'0.0'}]
telldus/znet/debug 15:25:22 - sensorState {'scale': 2, 'lastUpdated': 1598561826, 'value': u'0.0'}
telldus/znet/debug 15:25:22 - device 59 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/59/state", "command_topic": "homeassistant/light/znet/59/set", "schema": "json", "name": "DIN_Sovrum", "brightness": true}, "deviceTopic": "homeassistant/light/znet/59", "deviceType": "light"}
telldus/znet/debug 15:25:22 - deviceState 59, state: 2, value: 
telldus/znet/debug 15:25:22 - {"methods": 19, "battery": null, "isSensor": true, "deviceId": 75, "sensors": {"256": [{"scale": 2, "lastUpdated": 1594450751, "value": "0.0"}]}, "name": "DIN_Vardagsrum", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "light", "isDevice": true}
telldus/znet/debug 15:25:22 - device 75 has sensors
telldus/znet/debug 15:25:22 - sensortype 256 has [{'scale': 2, 'lastUpdated': 1594450751, 'value': u'0.0'}]
telldus/znet/debug 15:25:22 - sensorState {'scale': 2, 'lastUpdated': 1594450751, 'value': u'0.0'}
telldus/znet/debug 15:25:22 - device 75 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/light/znet/75/state", "command_topic": "homeassistant/light/znet/75/set", "schema": "json", "name": "DIN_Vardagsrum", "brightness": true}, "deviceTopic": "homeassistant/light/znet/75", "deviceType": "light"}
telldus/znet/debug 15:25:22 - deviceState 75, state: 2, value: 
telldus/znet/debug 15:25:22 - {"methods": 2048, "battery": null, "isSensor": true, "deviceId": 76, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601259748, "value": "20.4"}]}, "name": "Matsalen", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:22 - device 76 has sensors
telldus/znet/debug 15:25:22 - sensortype 1 has [{'scale': 0, 'lastUpdated': 1601259748, 'value': u'20.4'}]
telldus/znet/debug 15:25:22 - sensorState {'scale': 0, 'lastUpdated': 1601259748, 'value': u'20.4'}
telldus/znet/debug 15:25:22 - device 76 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/76/state", "name": "Matsalen"}, "deviceTopic": "homeassistant/binary_sensor/znet/76", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:22 - deviceState 76, state: 1, value: 
telldus/znet/debug 15:25:22 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 77, "sensors": {}, "name": "Brytare", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:25:22 - device 77 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/77/state", "command_topic": "homeassistant/switch/znet/77/set", "name": "Brytare"}, "deviceTopic": "homeassistant/switch/znet/77", "deviceType": "switch"}
telldus/znet/debug 15:25:22 - deviceState 77, state: 2, value: 
telldus/znet/debug 15:25:22 - {"methods": 2050, "battery": null, "isSensor": true, "deviceId": 88, "sensors": {}, "name": "Golvv\u00e4rme normal", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:22 - device 88 has sensors
telldus/znet/debug 15:25:22 - device 88 is a device
telldus/znet/debug 15:25:22 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/88/state", "name": "Golvv\u00e4rme normal"}, "deviceTopic": "homeassistant/binary_sensor/znet/88", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:23 - deviceState 88, state: 1, value: 
telldus/znet/debug 15:25:23 - {"methods": 2050, "battery": null, "isSensor": false, "deviceId": 89, "sensors": {}, "name": "Golvv\u00e4rme Badrum", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:23 - device 89 is a device
telldus/znet/debug 15:25:23 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/89/state", "name": "Golvv\u00e4rme Badrum"}, "deviceTopic": "homeassistant/binary_sensor/znet/89", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:23 - deviceState 89, state: 1, value: 
telldus/znet/debug 15:25:23 - {"methods": 0, "battery": null, "isSensor": true, "deviceId": 90, "sensors": {"1": [{"scale": 0, "lastUpdated": 1601306544, "value": "20.6"}]}, "name": "Golvv\u00e4rmen", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "binary_sensor", "isDevice": true}
telldus/znet/debug 15:25:23 - device 90 has sensors
telldus/znet/debug 15:25:23 - sensortype 1 has [{'scale': 0, 'lastUpdated': 1601306544, 'value': u'20.6'}]
telldus/znet/debug 15:25:23 - sensorState {'scale': 0, 'lastUpdated': 1601306544, 'value': u'20.6'}
telldus/znet/debug 15:25:23 - device 90 is a device
telldus/znet/debug 15:25:23 - device is device: {"deviceConfig": {"state_topic": "homeassistant/binary_sensor/znet/90/state", "name": "Golvv\u00e4rmen"}, "deviceTopic": "homeassistant/binary_sensor/znet/90", "deviceType": "binary_sensor"}
telldus/znet/debug 15:25:23 - deviceState 90, state: 2, value: 
telldus/znet/debug 15:25:23 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 91, "sensors": {}, "name": "Device 91", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [1, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:25:23 - device 91 is a device
telldus/znet/debug 15:25:23 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/91/state", "command_topic": "homeassistant/switch/znet/91/set", "name": "Device 91"}, "deviceTopic": "homeassistant/switch/znet/91", "deviceType": "switch"}
telldus/znet/debug 15:25:23 - deviceState 91, state: 1, value: 
telldus/znet/debug 15:25:23 - {"methods": 3, "battery": null, "isSensor": false, "deviceId": 92, "sensors": {"256": [{"scale": 0, "lastUpdated": 1601306603, "value": "295.8"}, {"scale": 2, "lastUpdated": 1601306543, "value": "0.03"}, {"scale": 4, "lastUpdated": 1601306544, "value": "234.5"}]}, "name": "Device 92", "parameters": {"devicetype": "00000000-0001-1000-2005-ACCA54000000"}, "state": [2, ""], "typeStr": "zwave", "type": "switch", "isDevice": true}
telldus/znet/debug 15:25:23 - device 92 is a device
telldus/znet/debug 15:25:23 - device is device: {"deviceConfig": {"state_topic": "homeassistant/switch/znet/92/state", "command_topic": "homeassistant/switch/znet/92/set", "name": "Device 92"}, "deviceTopic": "homeassistant/switch/znet/92", "deviceType": "switch"}
telldus/znet/debug 15:25:23 - deviceState 92, state: 2, value: 
telldus/znet/debug 15:25:23 - remove discovered device climate,89,89 : homeassistant/climate/znet/89
telldus/znet/debug 15:25:23 - remove discovered device climate,76,76 : homeassistant/climate/znet/76
telldus/znet/debug 15:25:23 - remove discovered device sensor,56,ACCA54013CBC_56_battery : homeassistant/sensor/znet/ACCA54013CBC_56_battery
telldus/znet/debug 15:25:23 - remove discovered device climate,56,56 : homeassistant/climate/znet/56
telldus/znet/debug 15:25:23 - remove discovered device sensor,76,ACCA54013CBC_76_battery : homeassistant/sensor/znet/ACCA54013CBC_76_battery
telldus/znet/debug 15:25:23 - remove discovered device sensor,55,ACCA54013CBC_55_battery : homeassistant/sensor/znet/ACCA54013CBC_55_battery
telldus/znet/debug 15:25:23 - remove discovered device climate,55,55 : homeassistant/climate/znet/55
telldus/znet/debug 15:25:23 - Updating config.devices_configured to : [('hub', 'hub', 'hub'), ('sensor', '55', '55_1_0'), ('binary_sensor', '55', '55'), ('sensor', '56', '56_1_0'), ('binary_sensor', '56', '56'), ('sensor', '58', '58_256_2'), ('light', '58', '58'), ('sensor', '59', '59_256_2'), ('light', '59', '59'), ('sensor', '75', '75_256_2'), ('light', '75', '75'), ('sensor', '76', '76_1_0'), ('binary_sensor', '76', '76'), ('switch', '77', '77'), ('binary_sensor', '88', '88'), ('binary_sensor', '89', '89'), ('sensor', '90', '90_1_0'), ('binary_sensor', '90', '90'), ('switch', '91', '91'), ('switch', '92', '92')]
telldus/znet/debug 15:25:23 - config updated devices_configured [('hub', 'hub', 'hub'), ('sensor', '55', '55_1_0'), ('binary_sensor', '55', '55'), ('sensor', '56', '56_1_0'), ('binary_sensor', '56', '56'), ('sensor', '58', '58_256_2'), ('light', '58', '58'), ('sensor', '59', '59_256_2'), ('light', '59', '59'), ('sensor', '75', '75_256_2'), ('light', '75', '75'), ('sensor', '76', '76_1_0'), ('binary_sensor', '76', '76'), ('switch', '77', '77'), ('binary_sensor', '88', '88'), ('binary_sensor', '89', '89'), ('sensor', '90', '90_1_0'), ('binary_sensor', '90', '90'), ('switch', '91', '91'), ('switch', '92', '92')]
telldus/znet/debug 15:25:24 - subscribing

Thank you again!

Cannot save config

Tried today to migrate to latest (rewritten) version of this plugin. Uninstalled old version. Rebooted. Installed latest. I guess the main problem is that I cannot save my configuration. After reboot it is always reverting to hatest topic with ztest device name. Also new "support" checkboxes are not saved.

I noticed that save button is only sending backend values that has been changed. So tried also "touching" all fields so I can verify from Chrome dev tools that all values are passed to save-endpoint. But no luck.

Edit: now it actually works if I don't restart the hub after saving the values. I will try the restart later and see if values have been saved.

Climate not working after rebooting Tellstick

I'm including a Heatit Z-TRM2fx floor thermostat in my network, and it works fine both from the Telldus app and from Home Assistant using the plugin on a Tellstick Znet Lite v2. However after rebooting the Tellstick it only works from the Telldus app.

The debug log of a working thermostat modification:

09:11:54 - climateState exception 1
09:11:54 - {"origin": "mqtt_hass", "stateValue": {"changeMode": 0, "temperature": 22.0, "mode": "heat"}, "state": 2048, "devicetype": "climate", "deviceId": 74, "type": "deviceStateChanged"}
09:11:54 - Command THERMOSTAT value: {'changeMode': False, 'mode': 'heat', 'temperature': 22.0}

Note DeviceId: 69 and 74 is the same device, I tried factory resetting a few times and IDs get increased.
After rebooting (not working) the debug topic says:

17:49:02 - climateState exception 1
17:49:02 - {"origin": "mqtt_hass", "stateValue": {"changeMode": 0, "temperature": 19.0, "mode": "heat"}, "state": 2048, "devicetype": "climate", "deviceId": 69, "type": "deviceStateChanged"}
17:49:02 - Command THERMOSTAT value: {'changeMode': False, 'mode': 'heat', 'temperature': 19.0}

To me it looks the same, apart from the temperature ofc.
Is there some way of easily debugging what causes the exception to be thrown?

Some lines from the boot logging: Device ID 73 is the main device, 74 is the thermostat subdevice.

09:23:29 - config updated devices_configured [('hub', 'hub', 'hub'), ('remote', '32', '32'), ('remote', '33', '33'), ('remote', '34', '34'), ('switch', '37', '37'), ('switch', '43', '43'), ('sensor', '44', '44_1_0'), ('switch', '46', '46'), ('sensor', '1', '1_1_0'), ('sensor', '2', '2_1_0'), ('sensor', '2', '2_2_0'), ('sensor', '3', '3_1_0'), ('switch', '4', '4'), ('switch', '16', '16'), ('switch', '18', '18'), ('switch', '20', '20'), ('remote', '27', '27'), ('remote', '28', '28'), ('remote', '29', '29'), ('remote', '30', '30'), ('remote', '31', '31'), ('climate', '74', '74'), ('sensor', '75', '75_1_0'), ('binary_sensor', '75', '75'), ('sensor', '76', '76_1_0'), ('binary_sensor', '76', '76'), ('sensor', '77', '77_256_0'), ('sensor', '77', '77_256_2'), ('sensor', '77', '77_256_4'), ('switch', '77', '77')]

09:23:29 - Updating config.devices_configured to : [('hub', 'hub', 'hub'), ('remote', '32', '32'), ('remote', '33', '33'), ('remote', '34', '34'), ('switch', '37', '37'), ('switch', '43', '43'), ('sensor', '44', '44_1_0'), ('switch', '46', '46'), ('sensor', '1', '1_1_0'), ('sensor', '2', '2_1_0'), ('sensor', '2', '2_2_0'), ('sensor', '3', '3_1_0'), ('switch', '4', '4'), ('switch', '16', '16'), ('switch', '18', '18'), ('switch', '20', '20'), ('remote', '27', '27'), ('remote', '28', '28'), ('remote', '29', '29'), ('remote', '30', '30'), ('remote', '31', '31'), ('climate', '74', '74'), ('sensor', '75', '75_1_0'), ('binary_sensor', '75', '75'), ('sensor', '76', '76_1_0'), ('binary_sensor', '76', '76'), ('sensor', '77', '77_256_0'), ('sensor', '77', '77_256_2'), ('sensor', '77', '77_256_4'), ('switch', '77', '77')]

09:23:29 - {"methods": 2050, "battery": null, "isSensor": false, "deviceId": 74, "sensors": {}, "name": "kabel termostat", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {}, "eco-heat": {}, "cool": {}}, "modes": ["off", "heat", "cool", "eco-heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}

09:23:29 - {"methods": 2050, "battery": null, "isSensor": true, "deviceId": 73, "sensors": {}, "name": "kabel", "parameters": {"devicetype": "00000011-0001-1000-2005-ACCA54000000", "thermostat": {"setpoints": {"heat": {"max": 35.0, "min": 5.0}, "eco-heat": {"max": 35.0, "min": 5.0}, "cool": {"max": 35.0, "min": 5.0}}, "modes": ["off", "heat", "cool", "eco-heat"]}}, "state": [1, ""], "typeStr": "zwave", "type": "climate", "isDevice": true}

I'm very thankful for help on this, as I would like to keep the Tellstick - but I need to be able to control the floor heating:
Winter is coming... :)

edit: I decided it was more cost effective to just run the z-wave network off an Aeotec Z-stick, instead. Leaving the issue open, in case anyone else runs into it. The plugin is still golden for all my 433MHz-devices 👍

Connection to MQTT @ Homeassistant - multiple issues

I have a setup with HASS and Mosquitto broker on dedicated VM. I have 2x Tellstick; one located in same subnet as the broker and HASS and on remote which is available over site2site-VPN.
Tellstick version: 1.3.2
Tellstick HASS MQTT-plugin: 0.90.4
Home Assistant 2022.8.5

The remote Tellstick to work fine,even if there WAN is not the best with some packetdrop and reconnect.

The local Tellstick is not able to connect to the broker in the same LAN. The logs from the mosquitto-broker reports:

1660885240: New client connected from %%LAN-IP%% as 880D7D93-B5DB-2FDF-743E-95466CB80E8A (p2, c1, k10).
1660885256: Client 880D7D93-B5DB-2FDF-743E-95466CB80E8A has exceeded timeout, disconnecting.
1660885262: New connection from %%LAN-IP%% on port 1883.

I have also tested with a Mosquitto broker on a VPS on internett with the same issue.

When I try to set up the embedded Mosquitto AddOn in HASS with use of username and password it seems like the tellstick-plugin is not sending the credentials?

The logs from the HASS Mosquittto-addon reports for both Tellsticks:
error: received null username or password for unpwd check

I am able to connect to the embedded broker when I use the same credential from MQTT Explorer

Anyone?

Any hints to debug?

Hi,
This is not a feature request or bug. It would be just nice to have some tips on the readme how to debug the setup. I have added the key through Telldus support and have successfully installed the plugin. However yet nothing on MQTT. How could I check what is wrong?
Br,
Henri

Add support for device-type cover

@henjoa have a Qubino flush shutter it would be great if we could integrate support for covers/shutters to the mqtt plugin.

Ref: home-assistant/core#34368

@henjoa, please paste related debug info here (from the telldus/TellstickZnetLite/debug topic) and we'll do our best to add support.

Config variables not saved

I've just added the plugin to my Tellstick Znet v2, but I don't seem to be able to save the config variables. Do I need to switch to the beta firmware in the Settings menu?

binary.sensor is not persistent

With releases from 0.82.2 and forward none of my binary.sensor -units is sent with the persistent flag.
(it think it has something to do with the changes in 0.82.2 ("The binary_sensor will turn ON or OFF when remote is pressed but after 1 sec it will be unknown/unavailable.") and that this is also happening on other binary sensors.
If i go back and use an older version than above none of my devices will show up as a device, only as an entity in home assistant.

Problem with PGP PUBLIC KEY BLOCK in README.md

The beginning of the key block has one less '-' at the end, gpg on a TellStick was not happy with this and refused to eat it.

diff key.pub pubkey.onREADME 
1c1
< -----BEGIN PGP PUBLIC KEY BLOCK-----
---
> -----BEGIN PGP PUBLIC KEY BLOCK----

Reset plugin autodiscovery

Hi.
The plugin is not sending the autodiscover messages.
The only thing sent is the homeassistant/binary_sensor/.../hub state = offline
It has sent the switch and sensor discovery messages before but not after i restored my Znet configuration via telldus support.
Is there a command i could send to reactivate the autodiscover commands to be sent?
Tried to uninstall and reinstall the plugin.
Tried several reboots.
Have another Znet in the same network which is working ok.

Does not update available status to online

For some reason the telldus publish telldus/telldus/available offline and don't seem to update to online.

My telldus is apparently available (as it publish data on MQTT)..

telldus/telldus/available offline
telldus/telldus/debug {"scale": 2, "battery": null, "valueType": 256, "value": 0.0, "deviceId": 2, "type": "sensorValueUpdated"}
telldus/telldus/debug sensorState {'scale': 2, 'lastUpdated': 1584094573, 'value': '0.0'}
telldus/telldus/debug {"scale": 2, "battery": null, "valueType": 256, "value": 0.0, "deviceId": 1, "type": "sensorValueUpdated"}
telldus/telldus/debug sensorState {'scale': 2, 'lastUpdated': 1584094574, 'value': '0.0'}
telldus/telldus/debug {"scale": 0, "battery": 254, "valueType": 1, "value": 6.5, "deviceId": 11, "type": "sensorValueUpdated"}
telldus/telldus/debug sensorState {'scale': 0, 'lastUpdated': 1584094577, 'value': '6.5'}
telldus/telldus/debug {"protocol": "fineoffset", "id": 255, "values": [{"scale": 0, "type": 1, "value": 6.5}], "model": "temperature", "data": 68455366565, "class": "sensor"}
telldus/telldus/debug {"scale": 0, "battery": 254, "valueType": 1, "value": 8.6999999999999993, "deviceId": 121, "type": "sensorValueUpdated"}
telldus/telldus/debug sensorState {'scale': 0, 'lastUpdated': 1584094578, 'value': '8.7'}
telldus/telldus/debug {"protocol": "fineoffset", "id": 199, "values": [{"scale": 0, "type": 1, "value": 8.6999999999999993}, {"scale": 0, "type": 2, "value": 66}], "model": "temperaturehumidity", "data": 328302281419, "class": "sensor"}

Originally posted by @fredrike in #9 (comment)

Importing of custom keys are not allowed

Försöker lägga till pluginet men får följande felbeskrivning:

Error importing plugin
Plugin could not be imported:

Importing of custom keys are not allowed

För det är zip-filen (MQTT_Homeassistant-0.86.zip) som skall laddas upp i Tellsticken?

Only subscribe to "new" input

In my use case (433-remote control) I am only interested in "new" incoming signals, not existing states.

Therefor I wonder if functions like @slot('deviceStateChanged') might be suitable to publish to two topics, one to self.publishState(haDev) and another to self.publishNewState(haDev) for subscribers only interested in changes to the value.

Do you find this reasonable? Is this functionality already in place and I have failed to to spot it?

Thank you for this plugin by the way!

Adhere to home assistant 2023.8 mqrr changes

Home assistant 2023.8 have started to complain about duplicate names, we need to fix that..

https://developers.home-assistant.io/blog/2023-057-21-change-naming-mqtt-entities/

https://www.hackster.io/news/home-assistant-2023-8-brings-new-mqtt-related-error-messages-but-don-t-worry-say-maintainers-bec84d16710e

I guess that we need to remove the device Name (Krypgrund in this example..

{
  "unit_of_measurement": "%",
  "device": {
    "suggested_area": "",
    "name": "Krypgrund",
    "identifiers": "90d03311-23c9-4f67-a937-b86d89d707e4",
    "via_device": "ACCA5401B5EA",
    "model": "Temperaturehumidity",
    "manufacturer": "Mandolyn"
  },
  "device_class": "humidity",
  "name": "Krypgrund humidity",
  "state_class": "measurement",
  "state_topic": "home/sensor/TellstickZnetLite/5_2_0/state",
  "value_template": "{{ value_json.value }}",
  "availability_topic": "home/binary_sensor/TellstickZnetLite/hub/state",
  "unique_id": "ACCA5401B5EA_5_2_0",
  "platform": "mqtt"
}

Add support to add multiple devices

The way Home-Assistant works with devices is the following:

A device can have multiple entities (where an entity is a sensor, a switch, a lamp etc.).
A device can be assigned to an area.
A device can be nested under another device (using the via_device property home-assistant/core#19454).

That means that in the Telldus environment each sensor should be its own device and this device should be nested under the Tellstick-device.

This is how the sensor "Vit Inne" in the Tellstick-live integration (Mjövik is the name of my Tellstick-Lite):

I therefore suggest that this plugin sends a binary_sensor that represents the Tellstick like this:

homeassistant/binary_sensor/telldus/ACCA5401B5EA/config

{"name": "Telldus", "payload_off": "offline", "payload_on": "online", "device": {"sw_version": "1.3.1", "name": "telldus", "identifiers": "ACCA5401B5EA", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "model": "tellstick-znet-lite-v2", "manufacturer": "Telldus Technologies"}, "device_class": "connectivity", "state_topic": "telldus/telldus/available", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_main"}

And that this entities (posted to homeassistant/sensor/telldus/6_1_0/config, homeassistant/sensor/telldus/6_2_0/config & homeassistant/sensor/telldus/ACCA5401B5EA_6_battery/config:

{"unit_of_measurement": "\u00b0C", "json_attributes_topic": "home/sensor/telldus/6_1_0/state", "name": "Vit Inne temp - \u00b0C", "value_template": "{{ value_json.value }}", "device": {"sw_version": "1.3.1", "name": "telldus", "identifiers": "ACCA5401B5EA", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "model": "tellstick-znet-lite-v2", "manufacturer": "Telldus Technologies"}, "device_class": "temperature", "state_topic": "home/sensor/telldus/6_1_0/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_6_1_0"}
{"unit_of_measurement": "%", "json_attributes_topic": "home/sensor/telldus/6_2_0/state", "name": "Vit Inne humidity - %", "value_template": "{{ value_json.value }}", "device": {"sw_version": "1.3.1", "name": "telldus", "identifiers": "ACCA5401B5EA", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "model": "tellstick-znet-lite-v2", "manufacturer": "Telldus Technologies"}, "device_class": "humidity", "state_topic": "home/sensor/telldus/6_2_0/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_6_2_0"}
{"unit_of_measurement": "%", "device": {"sw_version": "1.3.1", "name": "telldus", "identifiers": "ACCA5401B5EA", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "model": "tellstick-znet-lite-v2", "manufacturer": "Telldus Technologies"}, "name": "Vit Inne - Battery", "device_class": "battery", "state_topic": "home/sensor/telldus/ACCA5401B5EA_6_battery/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_ACCA5401B5EA_6_battery"}

Are changed to:

{"unit_of_measurement": "\u00b0C", "json_attributes_topic": "home/sensor/telldus/6_1_0/state", "name": "Vit Inne temp - \u00b0C", "value_template": "{{ value_json.value }}", "device": {"name": "Vit Inne", "identifiers": "ACCA5401B5EA-vit_inne", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "via_device": "ACCA5401B5EA"}, "device_class": "temperature", "state_topic": "home/sensor/telldus/6_1_0/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_6_1_0"}
{"unit_of_measurement": "%", "json_attributes_topic": "home/sensor/telldus/6_2_0/state", "name": "Vit Inne humidity - %", "value_template": "{{ value_json.value }}", "device": {"name": "Vit Inne", "identifiers": "ACCA5401B5EA-vit_inne", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "via_device": "ACCA5401B5EA"}, "device_class": "humidity", "state_topic": "home/sensor/telldus/6_2_0/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_6_2_0"}
{"unit_of_measurement": "%", "device": {"name": "Vit Inne", "identifiers": "ACCA5401B5EA-vit_inne", "connections": [["mac", "AC:CA:54:01:B5:EA"]], "via_device": "ACCA5401B5EA"}, "name": "Vit Inne - Battery", "device_class": "battery", "state_topic": "home/sensor/telldus/ACCA5401B5EA_6_battery/state", "availability_topic": "telldus/telldus/available", "unique_id": "ACCA5401B5EA_ACCA5401B5EA_6_battery"}

I don't know if "model" & "manufacturer" is available at the plugin level but perhaps "model" could represent the type of device.

Error importing plugin

Hi,

I tried to upload the zip to my TellStick ZNet Lite v2
I've been on contact with Telldus so they updated so I can install this plugin

But I just get:
Error importing plugin
Plugin could not be imported:
Malformed plugin. No manifest found.

Can you help me to solve it?

Better support for loosing connection to mqtt server

When the TellStick lose internet connection the plugin seems to hang and not reconnect to the mqtt-server. It would be great if the plugin would try to reconnect if it lose connection.

can not save

I can not change any setting every time I press save, it goes back to what it was before when I go in no one and check it has for some reason ended up wrong ip no and now I can not adjust it

This would be amazing if thermostats and SETPOINT_TYPE_HEATING were supported

Hi, Thank you for fantastic work with this plugin. It works really well. I have however one issue in my setup and this is that the setpoint temperature for Z-wave thermostats is not passed onto MQTT neither as status nor as set. I'm not sure if this is possible as I don't have any experience in developing plugins for the Tellstick devices, but I know that it is retrievable and possible via LUA scripting. Here is a link to a post where this has been done. https://forum.telldus.com/viewtopic.php?t=6587

It is unfortunately in Swedish, but the code is readable and is seen below. Can this be useful as a starting point to implement it in you plugin? I would be very happy to help out as much as I can in the development.

Thank you again for great work!

All the best

Tomas


- File: SetTempElementLevel1.lua
local deviceManager = require "telldus.DeviceManager"
local COMMAND_CLASS_THERMOSTAT_SETPOINT = 0x43
local SETPOINT_TYPE_HEATING = '1'

function onDeviceStateChanged(device, state, stateValue)
	if device:name() ~= "DummyLevel1" then
		return
	end

	if (device:state() == 1) then
		print("DummyLevel1:on")
		
		for index, device in python.enumerate(deviceManager:retrieveDevices()) do
			if (string.find(device:name(),"ElementLevel1") ~= nil) then
				print(device:name())
				setDanfossTemperature(device, 18)
				return
			end
		end		
		return

	else
		print("DummyLevel1:off")
		
		for index, device in python.enumerate(deviceManager:retrieveDevices()) do
			if (string.find(device:name(),"ElementLevel1") ~= nil) then
				print(device:name())
				setDanfossTemperature(device, 22)
				return
			end
		end		
		return
	end
end


function setDanfossTemperature(device, temperature)
	if (device:typeString() ~= 'zwave') then
		print("Device %s is not a Z-Wave device", device:name())
		return
	end
	-- Get the raw zwave node
	local zwaveNode = device:zwaveNode()
	-- Extract the thermostat setpoint command class
	local cmdClass = zwaveNode:cmdClass(COMMAND_CLASS_THERMOSTAT_SETPOINT)
	if (cmdClass == nil) then
		print("Device %s does not support THERMOSTAT_SETPOINT", device:name())
		return
	end
	-- Set new value to be sent the next time the device is awake
	cmdClass:setSetpoint(SETPOINT_TYPE_HEATING, temperature)
end

State messages not retained is desired

Hi again,

The plugin is working excellently - good job!

However, as I'm using 433 remotes, I soon ran into trouble: I use the state messages to trigger automations, and since the state messages are retained, my whole house is blinking for a while after restart of Home Assistant, since the MQTT client reads the retained messages again and triggers automations.

Even for remotely controlled switches, it is possible to think of a case in which it is not desirable that the state messages are retained, for example:

You open a garage cover and the plugin publish an "OPEN"/"ON" state message for the cover
The cover is closed manually
There is a temporary power failure or an intentional restart of Home Assistant
Upon restart, Home Assistant reads the retained state message and reopens the garage cover (which may not be desirable at this point)

A discussion can be found here: https://community.home-assistant.io/t/mqtt-how-to-remove-retained-messages/79029

Have you considered setting Retain to False for state messages. Or, if that is not what you desire, have you considered letting the user choose Retain or Not retain in the plugin configuration? I would certainly appreciate such an option.

Debug info

Hi,

I’ve had this plugin installed for about a year, but haven’t used it in a while. The plugin seems to have changed its behavior to posting messages with the topic telldus/znet/debug instead of …/binary_sensor. The content is e.g. “deviceState 119, state: 2, value: “.

Is this a setting? Am I missing something?

Thanks,
Ville

Can not change the MQTT hostname

pluging Version: 0.82.3
TellStick is currently running stable version 1.2.0

Trying to change the MQTT hostname from 10.10.10.100 to 10.10.20.100.
Hitting save will not set the new hostname.
Rebooting after hitting save will not set the new hostname.

Reinstalling the plugin will not fix the problem.

Does this also work for a tellstick net, not only tellstick znet?

ESIC WT450H sensors do not update their values

I have just managed to get this plugin up and running. it works mostly fine and is feeding my HA instance with devices and values. It seems as if even "Create sub devices/via_device (Missing in HA)" works fine now (HomeAssistant 2023.1.4)
I have a number of Temp and temp/humidity sensors, and I discovered that my four ESIC WT450H sensors (using the mandolyn protocol), only gets one value - the value when the mqtt plugin starts (and possibly one or two more), the values in tellduslive do vary, so it is not a case of the old sensors being sleepy. the other sensors (viking and telldus) are using fineoffset and they are ticking along nicely -as long as the link to the mqttbroker in HA is working.

@quazzie any idea what might be going on or how to trouble shoot?

Delete old device

Hello wonderful work

Can I delete old device? The device I delete from Telldus don't disappear in my mqtt broker

implicit state_topic is deprecated

Upgraded from 0.82.3 to 0.84, and got these messages in HA for all devices:

implicit state_topic is deprecated, add "state_topic":"elghaugen/sensor/znet/ACCA5401F795_1196_battery/state" to elghaugen/sensor/znet/ACCA5401F795_1196_battery/config discovery message

Upgrade was performed by uninstalling 0.82.3 and then installing 0.84.
Everything (else) seems to be working fine though.

Change binary sensor state

Background

I have lots of remotes around the house that are "directly" paired to switches. Thus they control the switches directly. These remotes are also registered in the tellstick znet v2 lite.

In Home Assistant (HA) , mqtt these remotes are registered as binary sensors and marked an unavailable.
When the remote is activated e.g. turned on or off its state is shortly shown in HA as on or off and then becomes unavailable again.

As the remote is unavailbe in HA I can't activate the switch by changeing the remote setting in HA.

If I use MQTT explorer I can change the state of the remote or switch in question, values show up in the broker, but the tellstick 2 does not send out the 433MHz command or atleast the right one and thus the switch newer change status.

It seems to be a difference between topic state and topic set depending on how a device is register in HA. or in the plugin.

Question:

Is there a way to get this to work inorder to not have to re-configure many switches and be indepent from the telldus company?

Does not re-connect when MQTT broker restarts

Broker connection is broken after a restart.

Tested reconnect by entering configuration, touching a field and then saving status.
Touch may not be required. This is not tested.
Reboot may make a reconnect. This is not tested.

'HaDeviceBattery' object has no attribute 'sensorType'

I don't know if this is an important error, but here is the log:

Fri Apr 21 09:49:05 2023 [INF] HaClient: Sensor value changed (11) type: 1 scale: 0 value: 16.3
Fri Apr 21 09:49:05 2023 [INF] HaClient: publish state for (11_1_0) /sensor//11_1_0/state : {"lastUpdated": 1682070545, "value": "16.3"}
Fri Apr 21 09:49:05 2023 [INF] HaClient: Sensor value changed (11) type: 2 scale: 0 value: 50
Fri Apr 21 09:49:06 2023 [INF] HaClient: publish state for (11_2_0) /sensor//11_2_0/state : {"lastUpdated": 1682070545, "value": "50"}
Fri Apr 21 09:49:24 2023 [INF] HaClient: Sensor value changed (12) type: 1 scale: 0 value: 14.4
Fri Apr 21 09:49:24 2023 [INF] HaClient: publish state for (12_1_0) /sensor//12_1_0/state : {"lastUpdated": 1682070563, "value": "14.4"}
Fri Apr 21 09:49:24 2023 [INF] HaClient: Sensor value changed (12) type: 2 scale: 0 value: 78
Fri Apr 21 09:49:24 2023 [INF] HaClient: publish state for (12_2_0) /sensor//12_2_0/state : {"lastUpdated": 1682070563, "value": "78"}
Fri Apr 21 09:49:25 2023 [INF] HaClient: Sensor value changed (23) type: 256 scale: 2 value: 63.05
Fri Apr 21 09:49:25 2023 [INF] HaClient: publish state for (23_256_2) /sensor//23_256_2/state : {"lastUpdated": 1682070565, "value": "63.05"}
Fri Apr 21 09:49:29 2023 [INF] HaClient: publish state for (live) /binary_sensor//live/state : online
Fri Apr 21 09:49:29 2023 [INF] HaClient: publish state for (ipaddr) /sensor//ipaddr/state : 192.168.*.*
Fri Apr 21 09:49:30 2023 [INF] HaClient: publish state for (cpu) /sensor//cpu/state : 7.0
Fri Apr 21 09:49:30 2023 [INF] HaClient: publish state for (ram_free) /sensor//ram_free/state : 28
Fri Apr 21 09:49:30 2023 [INF] HaClient: publish state for (net_recv) /sensor//net_recv/state : 345
Fri Apr 21 09:49:30 2023 [INF] HaClient: publish state for (net_sent) /sensor//net_sent/state : 15
Fri Apr 21 09:49:31 2023 [INF] HaClient: Sensor value changed (10) type: 1 scale: 0 value: 15.6
Fri Apr 21 09:49:31 2023 [INF] HaClient: publish state for (10_1_0) /sensor//10_1_0/state : {"lastUpdated": 1682070571, "value": "15.6"}
Fri Apr 21 09:49:35 2023 [INF] HaClient: Sensor value changed (17) type: 256 scale: 2 value: 3.071
Fri Apr 21 09:49:35 2023 [INF] HaClient: publish state for (17_256_2) /sensor//17_256_2/state : {"lastUpdated": 1682070575, "value": "3.071"}
Fri Apr 21 09:49:38 2023 [INF] HaClient: Sensor value changed (9) type: 1 scale: 0 value: 9.0
Fri Apr 21 09:49:38 2023 [INF] HaClient: publish state for (9_1_0) /sensor//9_1_0/state : {"lastUpdated": 1682070578, "value": "9.0"}
Fri Apr 21 09:49:38 2023 [INF] HaClient: Sensor value changed (9) type: 2 scale: 0 value: 73
Fri Apr 21 09:49:39 2023 [INF] HaClient: publish state for (9_2_0) /sensor//9_2_0/state : {"lastUpdated": 1682070578, "value": "73"}
Fri Apr 21 09:49:47 2023 [INF] HaClient: Sensor value changed (40) type: 1 scale: 0 value: 16.1
Fri Apr 21 09:49:47 2023 [ERR] 'HaDeviceBattery' object has no attribute 'sensorType'
Fri Apr 21 09:49:47 2023 [ERR] ('/usr/lib/python2.7/site-packages/base/Application.py', 163, 'run', None)
Fri Apr 21 09:49:47 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 356, 'onSensorValueUpdated', None)
Fri Apr 21 09:49:47 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 355, '<genexpr>', None)
Fri Apr 21 09:49:48 2023 [INF] HaClient: Sensor value changed (40) type: 2 scale: 0 value: 63.0
Fri Apr 21 09:49:48 2023 [ERR] 'HaDeviceBattery' object has no attribute 'sensorType'
Fri Apr 21 09:49:48 2023 [ERR] ('/usr/lib/python2.7/site-packages/base/Application.py', 163, 'run', None)
Fri Apr 21 09:49:48 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 356, 'onSensorValueUpdated', None)
Fri Apr 21 09:49:48 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 355, '<genexpr>', None)
Fri Apr 21 09:49:50 2023 [INF] HaClient: Sensor value changed (22) type: 256 scale: 2 value: 0.0
Fri Apr 21 09:49:50 2023 [INF] HaClient: publish state for (22_256_2) /sensor//22_256_2/state : {"lastUpdated": 1682070590, "value": "0.0"}
Fri Apr 21 09:49:52 2023 [INF] HaClient: Sensor value changed (40) type: 512 scale: 1 value: 4327.0
Fri Apr 21 09:49:52 2023 [ERR] 'HaDeviceBattery' object has no attribute 'sensorType'
Fri Apr 21 09:49:52 2023 [ERR] ('/usr/lib/python2.7/site-packages/base/Application.py', 163, 'run', None)
Fri Apr 21 09:49:52 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 356, 'onSensorValueUpdated', None)
Fri Apr 21 09:49:52 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 355, '<genexpr>', None)
Fri Apr 21 09:49:52 2023 [INF] HaClient: Sensor value changed (40) type: 128 scale: 0 value: 1.0
Fri Apr 21 09:49:52 2023 [ERR] 'HaDeviceBattery' object has no attribute 'sensorType'
Fri Apr 21 09:49:52 2023 [ERR] ('/usr/lib/python2.7/site-packages/base/Application.py', 163, 'run', None)
Fri Apr 21 09:49:52 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 356, 'onSensorValueUpdated', None)
Fri Apr 21 09:49:52 2023 [ERR] ('build/bdist.linux-x86_64/egg/hass_client/Client.py', 355, '<genexpr>', None)
Fri Apr 21 09:49:52 2023 [DBG] Send queue empty, set as sleeping
Fri Apr 21 09:49:53 2023 [INF] HaClient: Sensor value changed (11) type: 1 scale: 0 value: 16.3
Fri Apr 21 09:49:53 2023 [INF] HaClient: publish state for (11_1_0) /sensor//11_1_0/state : {"lastUpdated": 1682070593, "value": "16.3"}
Fri Apr 21 09:49:54 2023 [INF] HaClient: Sensor value changed (21) type: 256 scale: 2 value: 67.8

What is needed to build and release the plugin

Apart from creating and install pgp key. Where can I get the the necesarry pakages needed for building testing and releasing (Deployment):
I have searched pypi for the below but haven't found the packages below:

base, hass_client.utils, telldus and tellduslive.base
board, (netifaces on pypi isn't developed any more, susbstitue?)

Anything else that is needed to build, test and release would be appreciated.
I also get the impression that it is develoepd under python2, can this be confirmed?

Sluggify base_topic and device_name

Both base_topic and device_name should be slugified like this (not sure that it is allowed to add external libs):

http://code.activestate.com/recipes/577257-slugify-make-a-string-usable-in-a-url-or-filename/