Like i have for example a rfxcom device,
it shows up as a normal sensor, but it needs to be a switch..

how can i change it in homeassistant ?

Hello there. I'm new to home assistant and thought I'd give this plugin a try. I was able to add this integration but am getting the error below.

It seems odd that the JSON API seems to be working as it was able to show in my devices/events, but for some reason the ASCII interface isn't working? I'm sure I'm doing something wrong.

I did tick the Enable control using ASCII commands box in HS3. I also created a new user for home assistant with Admin + Local user rights. Is that the correct user rights? Is there something else I'm missing? Thanks!

Logger: libhomeseer.listener
Source: /usr/local/lib/python3.8/site-packages/libhomeseer/listener.py:82
First occurred: 12:00:55 PM (10 occurrences)
Last logged: 12:00:55 PM

Failed to login to HomeSeer ASCII at 192.168.1.99:11000: error, no user or bad pass

I have multiple fibaro motion sensors and battery and motion is working just fine. But the temp and lux sensors are not visible in HA. How can I fix this?:)

Is there possible to send status of a HA device with this command? I get an error when trying to send a number.

"Failed to call service homeseer/control_device_by_value. required key not provided @ data['value']"

UNIT_PERCENTAGE was changed to PERCENTAGE in 0.115. Any entities displaying % in Custom Component/Integrations will now error.

Trying to get the HomeSeer logo to appear in the Supervisor add-ons...
I removed my old setup which was initially manual and then overlaid by HACS.
Removed the homeseer: entry I had in configuration.yaml.
Re-added the repository to HACS and added the integration in HACS and I see the new folder in custom_components.
Restarted HA but I can no longer see the integration when I try to add via HA Supervisor.

I can see this in the logs:

2021-03-02 22:16:16 WARNING (SyncWorker_18) [homeassistant.components.waze_travel_time.sensor] Error on retrieving data: empty response
2021-03-02 22:16:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for homeseer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-03-02 22:16:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

After following the directions, the homeseer integration does not show up in configuration ->integrations ->add integration

I can edit the HS Device Type String if need be.

I've moved my Vision door lock from HA back to HS since ozw cannot properly handle the logging records. Somehow it's current record is always one record behind the actual current record. Max stored records on the lock is 50 but since it last hit 50, the new current record is invalid record. I excluded it from ozw, added it to HS and the log record is okay now. No idea what ozw is doing!!!

Anyway, I had a sensor in HA from which I parsed the segments and converted the lock's UTC time to local time. It would be nice to have that back again!

#   Door Locks
      frontdoor_lock_log_date:
        friendly_name: "Frontdoor Lock Log"
        value_template: '{{ states.sensor.front_door_lock_logging.attributes["TimeStamp"] | timestamp_custom("%d/%m/%y %H:%M:%S") }}'
      
      frontdoor_lock_log_message:
        friendly_name: "Frontdoor Lock Log"
        value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[1].split(":")[1].strip() }}'

      frontdoor_lock_log_user:
        friendly_name: "Frontdoor Lock Log"
        value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[2].split(":")[1].strip() }}'

      frontdoor_lock_log_code:
        friendly_name: "Frontdoor Lock Log"
        value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[3].split(":")[1].strip() }}'

Hi

This is a great plugin when it works.
But it has a problem.
Suddenly it just stop working,
It happens mostly when i remove a device in Homeseer or make som other reconfiguration on Home Assistant.
If i restart Home Assistant everything works again.

A change in a home controlling system is not unusual.
So this is a problem.
I can not trust this plugin.

Could this be solved ?
If you need some logs or something just tell me what you need.
I really want this to work.

I have an issue with my binary switches (simple on off switches, no dimmer) in that I'm able to turn them off in Home Assistant, but the option to turn them on never populates. I turn the switch off and it doesn't change to the ability to turn it on. It tracks the status correctly in identifying on (but have to do manually) and off but can't actually turn on.

I have a virtual device that has four states, each with an assigned attribute/value pair in HS. (Motion, no motion, away, other)

However, within the integration, it is represented strictly as on/off both as a toggle device and on the timeline. The attributes of the entity show both the value (1) and the attribute title (e.g. Away).

Is there a way to exclude all devices at once in recorder?
as i have 1000+ devices log growing everyday with 120mb.

just want to know if this is possible.

regards

Add support for device type string "Z-Wave Watts" as a proper energy sensor.

I have 3 Schlage Z-Wave locks (all same model) which the homeseer integration successfully created in Home assistant as:

lock.door_lock
lock.door_lock_2
lock.door_lock_3

The third lock works fine and I can lock/unlock from Home Assistant, and the status updates correctly in the UI and appropriate messages appear in the Homeseer log. The other two (lock.door_lock and lock.door_lock2) do not update status, nor do they appear to contact homeseer when their lock/unlock button is pressed in the UI. The lock history also does not update when the lock status is changed in homeseer.

When I click the "Lock" toggle in the home assistant UI, I get the following in the Home Assistant log:

2020-11-11 13:55:00 ERROR (MainThread) [pyhs3.const] HomeSeer HTTP Request error: Invalid variable type: value should be str or int, got None of type <class 'NoneType'> 2020-11-11 13:55:13 ERROR (MainThread) [pyhs3.const] HomeSeer HTTP Request error: Invalid variable type: value should be str or int, got None of type <class 'NoneType'>

There are no messages in the Homeseer log.

I’m new to HA and slowly migrating devices around the house into HA and have a lot of Insteon equipment. I was very happy to be able to get the HomeSeer Custom Integration for Home Assistant working for the most part. One issue I have is with 2 Insteon Hidden Door Sensors where I am missing the Root/Parent reference device (REF# 904 in the image below). The Integration was able to pull in all the other child devices though but as you can see, the one I really need is the open/close status of the Root device.

Pulling the logs it looks like this is purposely not created.

2021-07-25 10:45:08 DEBUG (MainThread) [custom_components.homeseer.homeseer] Device ref 904 is a root device, not creating an entity for this device

Is there a way I can manually create an Entity for this Device in HA or that you can update the integration to accommodate this need?

When you turn off a dimmer and turn on it again in home assistant it goes to on (full power) instead of the dimmed level.

Is there something I can do to solve this issue?
The dim level is known see below

{ "ref":74, "name":"Eetkamertafel", "location":"Woonkamer", "location2":"Beneden", "value":39.0, "status":"39%", "device_type_string":"Z-Wave Switch Multilevel", "last_change":"\/Date(1608838259046+0100)\/", "relationship":4, "hide_from_view":false, "associated_devices":[ 73 ], "device_type":{ "Device_API":4, "Device_API_Description":"Plug-In API", "Device_Type":0, "Device_Type_Description":"Plug-In Type 0", "Device_SubType":38, "Device_SubType_Description":"" }, "device_type_values":null, "UserNote":"", "UserAccess":"Any", "status_image":"/images/HomeSeer/status/dim-40.gif", "voice_command":"", "misc":4352, "interface_name":"Z-Wave" },

Hi,

I did notice there is a little thing what would be nice to be implemented.

I have some tuya devices that only have a dim slider.
Now when imported into home assistant it shows up as a status device.

I did see in the docs it needs on/off and dim to show up as a light..

Sadly the thermostat/heater devices have a bug in homeassistant tuya integration, that's why I want to use it trough this integration.

I am not able to install the integration under the "Configurations - Integrations" menu on HA. I get the following (possibly related) errors in the log:
2021-02-28 19:45:12 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-02-28 19:45:13 WARNING (MainThread) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.

Any suggestions you have would be greatly appreciated.

Im running HS4, I get following error inn HA:

2020-09-15 19:42:42 ERROR (MainThread) [homeassistant.setup] Error during setup of component homeseer
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 191, in _async_setup_component
result = await task
File "/config/custom_components/homeseer/init.py", line 82, in async_setup
await homeseer.api.initialize()
File "/usr/local/lib/python3.8/site-packages/pyhs3/hometroller.py", line 56, in initialize
await self._get_devices()
File "/usr/local/lib/python3.8/site-packages/pyhs3/hometroller.py", line 95, in _get_devices
all_devices = result["Devices"]
KeyError: 'Devices'

Any idea if this is relatied to me running HS4 or is it something else im doing wrong?

I started getting this error message repeatedly.

Entity cover.node_66_z_wave_left_garage_door (<class 'custom_components.homeseer.cover.HomeSeerGarageDoor'>) implements device_state_attributes. Please report it to the custom component author.

It looks like "device_state_attributes" got deprecated in 12.1 and it should be renamed to "extra_state_attributes"

I have a couple of these in my house: https://shop.homeseer.com/products/z-wave-fan-control-switch

When bridging them from HS to HA, I see them show up as lights with a dimmer, instead of fans with specific levels.

Happy to provide any information that would be helpful.

Hey, this is a great idea. I am personally moving all my zwave devices to use Homeseer for more stability. Thank you for making this integration!

I have 1 request, add it to HACS https://hacs.xyz/docs/publish/start

This would make upgrading a bit easier to track and get notifications when things are ready. Looks like you have been doing a lot of work, so this would be helpful!

Is it possible to get the special button presses from the HomeSeer dimmer switches such as the HS-WD200?
Would like to be able to run an automation if I double tap the off button, etc...

Following the instructions in the README I get:

• Component error: homeseer - Integration 'homeseer' not found.
  when running ha core check prior to restarting.
  Log entry:
  2021-02-20 17:55:00 ERROR (MainThread) [homeassistant.components.hassio] Component error: homeseer - Integration 'homeseer' not found.

Any suggestions? My entry in configuration.yaml is below:

Integration of Homeseer with Home Assistant (README: https://github.com/marthoc/homeseer/blob/main/README.md)

homeseer:
host: 192.168.1.12
namespace: homeseer
http_port: 80
ascii_port: 11000
username: REDACTED
password: REDACTED
name_template: '{{ device.name }}'
allow_events: True
forced_covers: [ 10, 20, 30 ]

I used File Editor to pull the code from github.

I'm using the integration HA/HS, and working very well. Thank you for the great job.
But I have some questions:
When I finished the integration config some devices was imported not the way I would like, some sensor as generic, some lights as switches, sensor without sensor type (light, humid, etc).
I read all the posts and I understood that I can adjust it using the correct " device type (string)"? The question is that the relation between what I have to put in that field for receive, for example, a humid sensor, or a presence sensor? Is there some table of relation?

Another thing that I can do is disable automatic import and add just the device that I need, configuring in yaml file. It is possible? There some documentation?

Thanks for any help

Followed install process and got the following. Please advise. Thanks

SOLVED - Booted HA RPi4 and HS4 Hometroller. Systems connected as designed. Devices and entities in HS4 appeared in HA. Thanks for as great integration!

@AndreBremer and @kmitch95120 have both opened PR's which address the way entities are named in this component and propose different changes to the config parameters that control naming.

I would appreciate if we could all agree on a solution before I delve into looking at your specific changes.

The real issue (custom naming of entities) could be resolved here if we could provide entities with a unique ID - they could then take advantage of the entity registry and the ability to rename the entity and change its entity id from within Home Assistant. The problem is that HS3 doesn't expose any uniquely identifying info for a device (e.g. a UUID or serial #) over the API. We could use e.g. the device ref of the device as the unique id, though this is not truly unique. We could also use e.g. a hash of the device ref and name of the device (or other characteristics) which ups the uniqueness.

Thoughts?

• Update the documentation with an example event
• Update the documentation with an example automation triggered by the example event

So I installed this as a way to merge the gap between Home Assistant and HomeSeer. I only use HomeSeer for the lack of insteon product supportly current in Home Assistant. My End all goal is to get everything in HomeAssistant some how and I believe better insteon support is years away from where it is in Home Seer with Marks plugin.

Anyway I added your integration to HA and configured it to only pull in my Insteon Devices from HomeSeer. It worked and pulled them in but i am finding some issue

First is Garage Doors. Insteon uses a I/O sensor/relay device with a wired magnetic sensor and a on/off relay for telling it to open and closed. This device added in but instead of having the input sensor and output relay it is getting 2 entity for the output relay.

The Input sensor which is not and entity is what tell HomeSeer the door is opened closed.

Next issue i noticed is my Insteon KPL which are wall switched which can have 6 or 8 buttons to confuigure. Newer version of the PKL will allow you to detach the load from the switch buttons so you can't control the load from the switch. I am using that option but it appears when the intigration added the PKL it didn't add an entitiy for the first button instead it created the device as button a so i have no way to control it.

This is only first round of testing on a dev HA. Want to get this right before i add to prod but this plugin is my key to being able to use the HA system as the main controler to use with its great UI and Cards.

I have noticed that HomeSeer integrated devices are sometimes marked as unavailable. I presume this occurs after I restart HomeSeer without restart Home Assistant.

Does this integration, or HA itself, not attempt to reconnect if the TCP session between Home Assistant to HomeSeer is broken for one reason or another?

Hi,

I've recently purchased a new Zwave Door Sensor, but instead of using the usual settings, it uses 22/23 for On/Off. its set as Device Type of 'Z-wave Notification', I did manage to fudge it using 'Zwave Temperature', but obviously that is not ideal.

Would it be possible to have a Notification, device type which reports back the value as is ? Looking forward to the Electric meter values being passed through.

I've left the entity name template at its default setting of "{{ device.location2 }} {{ device.location }} {{ device.name }}" and it works for most HS devices but I've got a couple of devices that look like they are coming in as "{{ device.location2 }} {{ device.location }} {{ device.featurename }}". They have the Feature name instead of Device name. This isn't a huge problem, I can rename them, but I can't see why this is happening. The device names are unique but the feature names aren't.

David

Hi, I have several homeseer button devices that show up as sensors. I cannot get them to activate or do anything in home assistant. They simply display status, but i cannot control them. For example, I have an HAI Omni Pro II Controller, that has a driver for homeseer but not for home assistant. The omni pro II has buttons, lighting scenes, and various other things, that show up in homeseer correctly, but show up as a sensor when i try and use your homeassistant/homeseer bridgeing software. Is there anything that can be done about this? There are several other devices I use in homeseer, that work fine in homeseer, but just show status in homeassistant. Here are some screenshots.

Neo Electronics NAS-WR01ZE Power Plug
Similar to the door lock, it has features that report kWh, Watts, Volts and Amps.
Device Type Strings for the features is Z-Wave Electric Meter.
The Power Management Notification feature is Z-Wave Notification.

Integration of thermostat (If you get bored:) )
I have a Heatit thermostat I would like to integrate whit Home Assistant.
https://www.thermo-floor.no/media/multicase/documents/_tfasdokumentasjon/heatit%20controls/heatit%20z-trm3/manual_heatit_z-trm3_fw%204.0%20ver2020-b_eng.pdf

Temperature is ok. I have added the JSON output of the different devices underneath:

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":819,"name":"Thermostat - Heating Setpoint 1","location":"Stue","location2":"1. eta","value":24.0,"status":"24 C","device_type_string":"Z-Wave Heating Setpoint","last_change":"/Date(1607956368164+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":16,"Device_API_Description":"Thermostat API","Device_Type":6,"Device_Type_Description":"Thermostat Setpoint","Device_SubType":1,"Device_SubType_Description":"Heating 1"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/Thermometer-80.png","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":820,"name":"Thermostat - Mode 1","location":"Stue","location2":"1. eta","value":1.0,"status":"Heat","device_type_string":"Z-Wave Mode","last_change":"/Date(1607942922084+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":16,"Device_API_Description":"Thermostat API","Device_Type":3,"Device_Type_Description":"Thermostat Mode Setting","Device_SubType":0,"Device_SubType_Description":"Mode"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/Heat.png","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":821,"name":"Thermostat - Operating State 1","location":"Stue","location2":"1. eta","value":1.0,"status":"Heating","device_type_string":"Z-Wave Operating State","last_change":"/Date(1608195410454+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":16,"Device_API_Description":"Thermostat API","Device_Type":1,"Device_Type_Description":"Thermostat Operating State","Device_SubType":0,"Device_SubType_Description":"Operating State"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/heating.png","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":825,"name":"Thermostat - kW Hours 1","location":"Stue","location2":"1. eta","value":49.7,"status":"49.700 kW Hours","device_type_string":"Z-Wave Electric Meter","last_change":"/Date(1608195172408+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":256,"Device_API_Description":"Energy API","Device_Type":4,"Device_Type_Description":"KWH","Device_SubType":50,"Device_SubType_Description":""},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/electricity.gif","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":826,"name":"Thermostat - Watts 1","location":"Stue","location2":"1. eta","value":0.2,"status":"0.200 Watts","device_type_string":"Z-Wave Electric Meter","last_change":"/Date(1608195476509+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":256,"Device_API_Description":"Energy API","Device_Type":1,"Device_Type_Description":"Watts","Device_SubType":50,"Device_SubType_Description":""},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/electricity.gif","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

{"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":false,"Devices":[{"ref":827,"name":"Thermostat - Volts 1","location":"Stue","location2":"1. eta","value":238.8,"status":"238.800 Volts","device_type_string":"Z-Wave Electric Meter","last_change":"/Date(1608195471557+0100)/","relationship":4,"hide_from_view":false,"associated_devices":[818],"device_type":{"Device_API":256,"Device_API_Description":"Energy API","Device_Type":3,"Device_Type_Description":"Volts","Device_SubType":50,"Device_SubType_Description":""},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/electricity.gif","voice_command":"","misc":4352,"interface_name":"Z-Wave"}]}

Trying to setup HS4 for the first time but it always get an error connecting to ASCII

Failed to connect to HomeSeer ASCII connection at 192.168.1.5:11000, aborting entry setup.
9:23:41 AM – (ERROR) HomeSeer (custom integration) - message first occurred at 7:35:53 AM and shows up 3 times
Error opening connection to HomeSeer ASCII at 192.168.1.5:11000: [Errno 110] Connect call failed ('192.168.1.5', 11000)
9:23:16 AM – (ERROR) /usr/local/lib/python3.9/site-packages/libhomeseer/listener.py - message first occurred at 7:35:28 AM and shows up 5 times

I get the following error in HA, and not all events are showing:

Will this work with HS4?

Do you have plans to integrate with the new websocket?

Thanks!

You may already be thinking about this but I'll post in case you're not...

Would it be possible for the integration to import the HS Root device into HA as a device that then has the other related entities associated with it?

Hello,

Using this integration gives me some trouble.

In Homeseer I have some sensors that are realy good integrated in HA. Values are quick and correct visible.

But I do have a couple of switches that are not correctly send to HA. They show up as 'cover', and can only be used to 'close' the cover, what in my case means set out the light connected to the switch. Setting on does not work.
This is the case both for wall-switches as for build-inn switches.
In Homeseer I have two zwave controllers: an Aeotec Z-Wave Plus Z-Stick Gen5 and a homeseer z-net.
The switches on the z-net do show up right in HA, the switches on the aeotec stick are wrong.

Is there a way to get those things right in HA?

For example: see screenshots:

See alandtse/alexa_media_player#1281 (comment)
and https://github.com/dermotduffy/hass-motioneye/blob/main/custom_components/motioneye/init.py#L380-L389

I just updated my homeseer to the latest version 4.2.7.0 and also updated my Inteon plug in to the new HS4 version. and I am noticing this now i can't controll. I think this is caused by the new Insteon HS4 plugin as my homeseer nest plugin seems to be reporting values to HomeAssistant. If i revert back it works fine. i will try reverting back and then updated the homeseer and still see if the HS3 version plugin causes the same issue to narrow down which is causing this.

2022-01-27 15:22:38 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: {"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":true,"Devices":[{"ref":107,"name":"Plant Light","location":"Office","location2":"Basement","value":0.0,"status":"Off","device_type_string":"Dual-Band On/Off Module","last_change":"/Date(1643162400545-0500)/","relationship":4,"hide_from_view":false,"associated_devices":[199],"device_type":{"Device_API":513,"Device_API_Description":"Undefined API=513","Device_Type":0,"Device_Type_Description":"Undefined API 513, Type 0, SubType 0","Device_SubType":0,"Device_SubType_Description":"Dual-Band On/Off Module"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/off.gif","voice_command":"","misc":12544,"interface_name":"Insteon"}]}

2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] Pinging ASCII connection at 172.16.1.10:11000
2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] ASCII message received from 172.16.1.10:11000: b'4.2.7.0\r\n'
2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] Unhandled ASCII message type received from 172.16.1.10:11000: 4.2.7.0

I am seeing this in HA log at startup. Curious what it is complaining about. A timeout of some sort? Integration seems to work fine though...

Logger: libhomeseer.listener
Source: /usr/local/lib/python3.8/site-packages/libhomeseer/listener.py:82
First occurred: 12:43:21 AM (1 occurrences)
Last logged: 12:43:21 AM

Failed to login to HomeSeer ASCII at 192.168.1.103:11000: DC,769,12968148.304839,12968147.504409

Greetings,
While I am not suggesting this is an issue with your integration I need some ideas as to what I might be able to do to fix this.

After setting HS to run as a service, this integration can't access port 11000.

HA is set to allow ASCII and JSON
Pinging HS from HA terminal is good using ping 192.168.1.133:11000

Runs fine when HS is not set as a service. It also works with HS running as a service using NSSM.

HS running on Win10 Pro w latest updates
HAOS running on Pi w latest updates

Thanks

I got this log when upgrading to 2021.8.0 from 2021.7.0. Seems all my other controls and sensors work. I am guessing this has something to do with the new energy monitoring.

Logger: homeassistant.setup
Source: setup.py:311
First occurred: 9:36:04 AM (1 occurrences)
Last logged: 9:36:04 AM

Unable to prepare setup for platform homeseer.sensor: Platform not found (cannot import name 'ELECTRICAL_CURRENT_AMPERE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

I had version 1.0.0 installed and working. When I upgraded to 1.1.0, things stopped working and I'm seeing the following error in the logs.

ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform homeseer.sensor: Platform not found (cannot import name 'ELECTRIC_CURRENT_AMPERE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

Hi,
I have tried to install this custom component without success. I can install it in HACS and it showed up properly in HACS but when I try to search for it in the configuration -> Integration it cannot be found so I cannot set it up. Does anyone know how to fix this?

Hi i wounder if it possible to filter some events I don't need all events?
Ha says it only allowing 150 units?
or it possible to change this?

Is there a way to reconfigure the custom integration after the initial config? Where are the parameters for host, username, etc stored? I'm new to using this CI and am experimenting with the different settings. So far I've have to delete and reinstall each time I've wanted to change something.

Thanks
David

Team,
First of all: great job! In HS I have > 1,000 devices.

• Many of those are already in HA because HA is integrating with the same product as HS does. Example: All Zigbee devices are in HA through the Deconz integration.
• Many devices are not important/irrelevant for HA and therefore should not be imported.

At the end of the day I think that - during the transition period - less than 50 devices would have to be synced. And this number would decrease as I'm replacing KAKU sensors/switches and other technologies with their Zigbee equivalents.

Request: ability to provide a list of device references to import