Going to open this as a new issues, a previous issues similar to this has been closed but that solution doesnt apply here.

Node Red isnt showing in the UI configurations.

Followed the instructions initially.
Running HA 0.110.2
Then tried Installing via Hacs

translations shows in my custom_components/nodered. (other posts solution)

Any advice would be much appreciated.

How do I remove/delete/destroy an entity that I add this way? I tried deleting it from flow (I didn't really think that would work and it didn't).

Hi, I run HASS on a Raspberry Pi 4. I'm running the latest versions of HASS & Node Red. When I drag and drop the "entity" node onto the canvas and open it, I see "custom integration needs to be installed in Home Assistant for this node to function correctly” error" in red.

I've followed your installation instructions, created the config/custom components/nodered folder, put the zip files inside it, restarted the HASS server, when I go to HASS integrations and click the orange + symbol - I still can't see "In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Node-RED"

Nothing appears when searching for it as a new integration.

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log

Add your logs here.

Version of the custom_component

v0.1.0

Configuration

nodered:

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log

Add your logs here.

Output on Connect

Version of the custom_component

v0.4.4, Node-Red V7.2.6

Configuration

Add your logs here.

Describe the bug

The "Event: State" node of a custom component switch always send a payload on connect even if the "Output on Connect" option is unchecked.

Debug log

Add your logs here.

I've pretty much fresh installed hass.io on a rPi3b. Enable an SSH server, log into the box and do a git clone of this repo and cp the custom_components folder into the /config folder where the configuration.yaml file is.

Restart HA, not showing up in Add integration list. Rebooted. Only thing I see is in the /config/home-assistant.log is:

`config $ cat home-assistant.log 
2020-01-02 23:39:33 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.`

Not sure what else to try here, I've gone into the custom_components folder under /config and compared, all files and the .translations subfolder exist in there and have the same permissions as the rest of the items in /config

nodered $ ls -la
total 56
drwxr-xr-x    3 root     root          4096 Jan  2 23:37 .
drwxr-xr-x    3 root     root          4096 Jan  2 23:37 ..
drwxr-xr-x    2 root     root          4096 Jan  2 23:37 .translations
-rw-r--r--    1 root     root          7126 Jan  2 23:37 __init__.py
-rw-r--r--    1 root     root          2050 Jan  2 23:37 binary_sensor.py
-rw-r--r--    1 root     root           949 Jan  2 23:37 config_flow.py
-rw-r--r--    1 root     root          1094 Jan  2 23:37 const.py
-rw-r--r--    1 root     root          3366 Jan  2 23:37 discovery.py
-rw-r--r--    1 root     root           280 Jan  2 23:37 manifest.json
-rw-r--r--    1 root     root          1154 Jan  2 23:37 sensor.py
-rw-r--r--    1 root     root          3312 Jan  2 23:37 switch.py
-rw-r--r--    1 root     root          4333 Jan  2 23:37 websocket.py

Edit: Apparently the solution is "Wait Longer". After about an hour of playing around, it just showed up when I went to look for some reason.

on HA version 0.109 getting the flowing error
nodered: the '.translations' directory has been moved, the new name is 'translations', starting with Home Assistant 0.111 your translations will no longer load if you do not move/rename this

Almost exactly how webhooks work but with services as well.

My use case for this is pretty simple. I want to pass data from button click events in esphome via homeassistant.service Action

The idea is to have an esphome automation on the button double click event that will call a nodered service in home assistant, and that would in turn trigger the corresponding node in nodered.

After installing the component via HAC I have no integration available to add for Node-RED in Configurations -> Integrations
Followed the instructions with restart and check that the files are in place in custom_components

Running HA 0.115.3 with Node-RED add-on 7.2.1

No error messages in the logs except that Node-RED is complaining about the missing integration:
27 Sep 19:42:33 - [error] [ha-entity:propulsion.SB.exhaustTemperature] Node-RED custom integration needs to be installed in Home Assistant for this node to function correctly.

Any idea what wrong?

Is your feature request related to a problem? Please describe.

Get this custom stuff into the core, and remove the need for users to install this custom component.

Describe the solution you'd like

See above

Describe alternatives you've considered

Deprecate the Home Assistant Node-RED add-on to get rid of this brain damage I've accumulated over time on users not able to figure this all out.

Additional context

No.

I already have the NodeRED integration installed, and I'm looking at a node called "entity" which points to needing this custom component installed. I have this custom component installed from HACS, but I keep getting errors in NodeRED stating that

"Node-RED custom integration needs to be installed in Home Assistant for this node to function correctly."

The instructions regarding installing this point to manipulating the core NodeRED integration while also stating that it needs to be installed via HACS.

???

Is your feature request related to a problem? Please describe.
Right now the sensor is working flawlessly, however I feel like the addition of being able to change the mdi icon based on inputting a valid msg.icon would make this far superior to the native template sensor in Home Assistant

Describe the solution you'd like
Either declaring an icon the same way you currently define the state or allowing {{msg.icon}} in the 'Config' section to parse that message.

Describe alternatives you've considered
Currently I am having to resort to using the template sensor within Home Assistant.

Version of the custom_component

0.4.1

Configuration

2021-04-08 00:59:30 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'nodered'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'nodered'

Describe the bug

manifest file needs updating for this integration to continue working with Home Assistant.

Describe the bug

I recently updated Home Assistant to the modern version 2020.12.2 and unfortunately Node-Red companion integration stopped working, so my custom NodeRed entity went unavailable. Previous working version was 0.113.something

Versions of the custom_component

hass-node-red custom_component: latest master (739619e)
home assistant core: 2020.12.2

Debug log

I tried this logging config, no nodered/node-red occurrences appeared in logs :(

logger:
  default: info
  logs:
    custom_components.nodered: debug

Version of the custom_component

Current master branch.

Configuration

Add your logs here.

Describe the bug

I was interested in what this integration did. README wasn't very descriptive so browsing through the code and it's doing I/O inside the event loop. This should be done inside the executor worker thread.

Change async def -> def and then run `result = await hass.async_add_executor_job(check_files)

Debug log

Add your logs here.

I'm using the Node-RED webhooks to integrate HASS with DialogFlow/Google Assistant. I'd love a way to customize the Webhook Response to send DialogFlow additional information (it currently gets a generic 200 with no information, I believe).

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log

Add your logs here.

Is your feature request related to a problem? Please describe.
Lights are not that easy to customize in HA.
Especially programming custom solutions for like remote controlled LED strips (that aren't Wifi) would be a lot easier in Node-RED compared to the solutions there are in HA for this. (not to mention all the restarts to test the "code")

Describe the solution you'd like
Would it be possible to make an entity a "light" instead of the binary_sensor, sensor or switch ?

Describe alternatives you've considered
Right now I have a hacked solution for the color wheel made in HA's configuration.yaml. I don't really have a solution (yet) for setting brightness (just plus and minus buttons on a remote). Customizing is usually a lot easier in Node-RED in my experience...

v0.4.4

Configuration

HASS OS v4.12
Homeassistant 0.114.4
Node-Red v7.1.0
hass-node-red v0.4.4

Describe the bug

Entity nodes error with "Node-RED custom integration needs to be installed in Home Assistant for this node to function correctly."

All package files appear to exist in custom_components/nodered
Node-Red was installed via Supervisor / Addon Store
hass-node-red was installed after the fact

Steps taken:

• Reinstalled hass-node-red from HACS
• Restarted homeassistant
• Restarted Node-red
• Rebooted the box
• All steps were followed on installation page for hass-node-red
• No new entities are created or visible in Developer tab

I was unclear at first what installing this added over using -- alone. I found the release announcement with pictures and detailed descriptions. (And a very useful tip!) I wanted to suggest copying that into the project's README.md as well.

Thanks for this very useful project!

Version of the custom_component

Configuration

I use last version and did following steps:

1. Setup module and have instruction that it is necessary to use Integration
2. Setup integration
3. Open port 1880 on router

It all. I saw many video instructions, but can't find button open web, start and other.
How can I start it?

Add your logs here.

## Describe the bug
A clear and concise description of what the bug is.


## Debug log

<!-- To enable debug logs check this https://www.home-assistant.io/components/logger/ -->

```text

Add your logs here.

Version of the custom_component

Using v0.4.3

Configuration

Add your logs here.

Describe the bug

I had this installed via HACS, working well for months. One automation I had exposed ti HA became unavailable, so I began looking at the others I had exposed. When I open a node I can briefly see the boxes where I had named the switch and gave it an icon - then it disappears. I took a video of this behavior and can send that upon request if it helps.

Below you can see a card with all the exposed switches from NR - the grayed out lines are ones I have checked - once the node has been opened, the switch becomes unavailable in HA.

I ran the debug, logs below - and it says it creates switches for the ones I have not opened in NR.

Debug log

-------------------------------------------------------------------
nodered
Version: 0.4.3
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/zachowj/hass-node-red/issues
-------------------------------------------------------------------

2020-05-27 11:39:04 DEBUG (MainThread) [custom_components.nodered.discovery] Discovery message: {'type': 'nodered/discovery', 'server_id': 'b1cff34f.02b12', 'node_id': 'eb7e62ef.27845', 'component': 'switch', 'state': True, 'config': {'name': 'Kitchen Automation', 'icon': 'mdi:pistol'}, 'id': 10}
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.discovery] Creating switch b1cff34f.02b12 eb7e62ef.27845
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.websocket] Webhook created: uXa5dS7S8L6Rub5..
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.websocket] Webhook created: Pp98yiWaUmQRj74..
2020-05-27 11:39:05 DEBUG (MainThread) [custom_components.nodered.discovery] Discovery message: {'type': 'nodered/discovery', 'server_id': 'b1cff34f.02b12', 'node_id': '71e0ead5.d69c64', 'component': 'switch', 'state': True, 'config': {'name': 'Bedroom Automation', 'icon': 'mdi:pistol'}, 'id': 13}
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.discovery] Creating switch b1cff34f.02b12 71e0ead5.d69c64
2020-05-27 11:39:05 DEBUG (MainThread) [custom_components.nodered.discovery] Discovery message: {'type': 'nodered/discovery', 'server_id': 'b1cff34f.02b12', 'node_id': 'ea620998.df9958', 'component': 'switch', 'state': True, 'config': {'name': 'Master Bath Automation', 'icon': 'mdi:pistol'}, 'id': 14}
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.discovery] Creating switch b1cff34f.02b12 ea620998.df9958
2020-05-27 11:39:05 DEBUG (MainThread) [custom_components.nodered.discovery] Discovery message: {'type': 'nodered/discovery', 'server_id': 'b1cff34f.02b12', 'node_id': '50e4bfcc.e6629', 'component': 'switch', 'state': True, 'config': {'name': 'Bath Fan Automation', 'icon': 'mdi:pistol'}, 'id': 15}
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.discovery] Creating switch b1cff34f.02b12 50e4bfcc.e6629
2020-05-27 11:39:05 DEBUG (MainThread) [custom_components.nodered.discovery] Discovery message: {'type': 'nodered/discovery', 'server_id': 'b1cff34f.02b12', 'node_id': '9b927271.33e65', 'component': 'switch', 'state': True, 'config': {'name': 'Closet Automation', 'icon': 'mdi:pistol'}, 'id': 16}
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.discovery] Creating switch b1cff34f.02b12 9b927271.33e65
2020-05-27 11:39:05 INFO (MainThread) [custom_components.nodered.websocket] Webhook created: yPMF3vJy6QBwaoW..

Is your feature request related to a problem? Please describe.
If you want to use the state node in a subflow, it would be very handy to work with environment variables. However, I'm unable to work with environment variables in the entity_id node.

Describe the solution you'd like
Allow environment variables in the entity_ID of the nodes, this would add great flexibility!

Is your feature request related to a problem? Please describe.
Want to be able to create an AirQuality entity from data collected in NodeRed. Currently the entity object in node red only exposes Sensor, Binary Sensor, and Switch

Describe the solution you'd like
I think what needs to be done is update this library to support AirQuality but I am not 100% sure on that.

Describe alternatives you've considered
Tried to figure out some other way to create the AirQuality entity from either node-red or home assistant, but can't figure a way.

Describe the bug

I'm using a state node (switch), and expose this to Home Assistant in order to create an identity in HA. This works well. However, whenever I deploy an update in Node red, the entity state is always set to true, regardless of it's previous state. The same behaviour can be seen when restarting the home assistant container.

What should happen?

When deploying a flow or when or restarting HA, the entity state should not be changed, it should remain as it was previously set.

Hi

First of all thank you for you work and nice add-on

HA version Home Assistant: 0.114.4
Node_Red version: 7.1.0
Node Red Intregration version: 0.4.4

Describe the bug

The output points in Node red of the switch won't show any data when i add a Debug node to it.
When flipping the switch in HA the event-all and state change does show the switch being flipped.

If you look at the switch image attached it looks like some stuff is missing.

so i have a working situation especially handy concerning Lovelace :)

Thank you for your work

Release v0.3.0 notes that:

New service added nodered.trigger to trigger an exposed node.

After upgrading and restarting, I'm looking in the Developer Tools->Services and do not see nodered.trigger service available. I can confirm that I do see a services.yaml file in my $config/custom_components/nodered directory; however the service details are not registered/exposed to Home Assistant.

I can also confirm that the component is being loaded successfully:

2020-02-12 19:19:51 INFO (MainThread) [homeassistant.setup] Setting up nodered
2020-02-12 19:19:51 INFO (MainThread) [homeassistant.setup] Setup of domain nodered took 0.0 seconds.
2020-02-12 19:19:51 INFO (MainThread) [custom_components.nodered] 
-------------------------------------------------------------------
nodered
Version: 0.3.0
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/zachowj/hass-node-red/issues
-------------------------------------------------------------------

When searching for this integration, appears an empty line:

I've put the contents in the folder as described in the instructions:

when i select it showed loading icon during some time, but then only this:

And i don't have the integration in the list as installed.

this is what appeared me in the logs only:
2020-03-15 15:37:14 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

versions:

Version of the custom_component

6.1.4 (I think is the latest version)

Configuration

I'm not too sure what to add here, the problem is not related with nothing that I can detect.

Describe the bug

Since the update to Home Assistant 0.108.0 the CPU has gone higher and the memory of the Home Assistant AND Node RED addon grows constantly. I have verified this with a docker stats command.

If I stop the Node RED docker, the memory of Home Assistant seems to be stable.

Here is a graph of the memory/CPU usage since installed Home Assistant 0.108.0. I have restarted the system several times:

Is not sure 100% that Node Red is the culprit of that, so I open this issue to see if others have installed this new version of Home Assistant to see if they have the same problem and can we locate where the problem is.

Debug log

I'm not too sure what to add here, maybe a log of the system starting and the first 5 minutes of execution? I have it, but maybe is too big. Must I filter it by something?

Version of the custom_component

v0.4.1

Describe the bug

Randomly the integration between Node-red and home assistant will die and all the nodes appear as disconnected.

Debug log

5 Mar 12:01:41 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:46 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:52 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:57 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:02 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:07 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:12 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:17 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:22 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:28 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:33 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log

Add your logs here.

Version of the custom_component

Latest version

Configuration

None needed

Describe the bug

The entity node created a duplicate entity (same entity_id with _2 appended to it). I went to delete both entities to make a one, but the delete button was greyed out. To fix this, I suggest that you remove the disabled attribute from the delete button's HTML. I do not know how the entity was duplicated, so I can't offer much help there, but this has happened to me a handful of times over the past few months.

Reproduce the bug

Create a sensor in Node-RED with the entity node. Go to Configuration > Integrations > Node-RED entities and select the entity. Try to delete the entity. It should be greyed out. The entity can be deleted by removing the "disabled" attribute in the HTML and then clicking the delete button.

Debug log

None needed.

I think your integration fills a gap between Hassio and Node Red. Much appreciated.
But I could need som documentation/ explanation how to actually use it. With a few examples

Hi all,

I just installed NodeRED throw HACS, restart server and clear my browser cache but NodeRED is not displayed in the HA main menu.

It seems to be loaded because I have this line in the HA logs:

2021-04-14 18:39:48 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nodered 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.

NodeRED plugin: 0.4.5
HA version 2021.1.5

Can someone help me to solve this issue ?

Best regards,

Version of the custom_component

Latest

Describe the question

Is it possible to use a variable for the name of the entity, e.g. {{msg.payload.name}}?

I'm trying to create multiple sensors based on a JSON payload. The JSON is like this:

{
	"data": [{id: 123, name: Alpha}, {id: 456, name: Beta}]
}

I want a sensor for each item in the array, so have used a split node to send multiple messages.

For some reason it does not seem to accept a varaiable name.

Any advice?

After upgrading HA v0.111 beta (b2 when creating this issue), the switch feature no longer loads. It throws the following error on the logs:

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

Hi,

I'm having issues with the nodered custom integration for Home assistant.
When i try to add the integrations no text is displayed for the node red integrations:

When "configured" it look like this in the integrations list :

And in node-red, I've a error message whn i try to use the sensor component:

I've restarted many time and reinstalled many time and nothing change.

I'm using hass.io ( docker containers )

Regards,
Gilles aka Ekiel

HA Version: .114.0
Node Red: Installed via SuperVisor Add-on Store Version 7.0.0
Installed Node-Red Integration via Hacs , restarted
Version of the custom component (via const.py) VERSION = "0.4.4"

I am unable to add the Node-Red integration, and nothing related to Node-red is in the logs
I have tried removing the custom component of Node-Red from Hacs and reinstalling it, but there is no difference, even after numerous restarts.

The files in custom_components/nodered match the repo. The translations folder exists as well.

Thank you

Would it be possible to expand on the Entity Node Types from the current Switch, Sensor and Binary Sensor to also include the other supported entity types?

For example, I would use Light, Climate and Alarm Control Panel.

Sorry, if this is on a roadmap somewhere.

Cheers
David

Version of the custom_component:

v0.4.1

Describe the bug

I have some binary_sensors in my flows that generate the following warning message upon every deploy.

Node-RED custom integration needs to be installed in Home Assistant for this node to function correctly.

They all work fine, but this warning clutters the debug window.

See screenshot
Within the screenshot 2 sensor nodes are visible. The warning is printed by one of them but not the other. There is also a warning from another sensor node that is off screen.

Version of the custom_component

Node red version Installed: v0.4.3.

Note sure what other information you need in terms of config etc.. Hence did not add any.

Describe the bug

Trying to capture event data from a mobile and using the events:all node.
The mobile_app_notification_action event captured via Node Red does not have all the information which is returned.

I see the following when I use developer tools on HA

{
    "event_type": "mobile_app_notification_action",
    "data": {
        "action_2_title": "Snooze 5 mins",
        "action_3_title": "Remind me at Home",
        "sticky": "true",
        "title": "Low Battery",
        "message": "Charge your phone",
        "action_1_title": "Dismiss",
        "action_1_key": "DISMISS",
        "action_2_key": "SNOOZE",
        "action_3_key": "REMIND_HOME",
        "action": "SNOOZE"
    },
    "origin": "REMOTE",
    "time_fired": "2020-05-20T06:56:47.688083+00:00",
    "context": {
        "id": "I2345",
        "parent_id": null,
        "user_id": "1234"
   }
}

and below is all that is seen on the events:all node which is the out put of a debug node and on the node-red add on log section

20 May 20:12:26 - [info] [debug:d932decb.3b42c] 
{
  event_type: 'mobile_app_notification_action',
  entity_id: undefined,
  event: {
    action_2_title: 'Snooze 5 mins',
    action_3_title: 'Remind me at Home',
    sticky: 'true',
    title: 'Low Battery',
    message: 'Charge your phone',
    action_1_title: 'Dismiss',
    action_1_key: 'DISMISS',
    action_2_key: 'SNOOZE',
    action_3_key: 'REMIND_HOME',
    action: 'SNOOZE'
  }
}

as you can see it is missing a portion of the data which provides user information.

Debug log

There is no log other information on the hassio.log file when this event is captured when i setup logging at Info level.

I follow your guide, createn new folder nodered (subfolder of custom_components), cope there all files and restart Hass.io. But when I go to Configuration -> Integrations -> + there isnt option nodered.

Im using Hass.io and Node-red v.6.0.0

Version of the custom_component

v0.4.4

Describe the bug

Entity Switch does not get updated when passing in state data. Under HA v0.111. As shown:

Hello,

First let me thank zachowj (and any other contributer that may have helped) for this great work. This is really integrating node-red in HA.

This is a feature request that fits my needs, I assume that may benefit other people too, but honestly I don't understand the complexity of this request and its feasibility (cost vs effort), and I understand if you devs decide against this feature.

I use Node-Red with HA for many things. One of the things is to monitor the connectivity/availability of some devices IoT devices that are important in my system.
I want to expose to HA a switch that would activate/deactivate multiple switchs so that I could deactivate the entire monitoring, because sometimes it is useful.

Example 1 - monitor important devices:

Example 2 - monitor air quality in the house

What I have implemented is the input_bolean to allow this goal, but it would be much easier and cleaner to make that virtual switch available in Node-Red.

Thanks!

thanks for your work

Would it be possible to include the function to generate a virtual switch?
This feature would be very great. Currently I'm doing it with virtual switch in HASS

Version of the custom_component

Using latest version from github

Configuration

Add your logs here.

Configuration:

homeassistant:
    customize: !include customize.yaml
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
# Example configuration.yaml entry
device_tracker: # Set consider_home to 1m to check / debug home presence
  - platform: bluetooth_le_tracker
  - platform: bluetooth_tracker
    request_rssi: true

customize.yaml:

device_tracker.oneplus_3t:
  friendly_name: Massi's OnePlus 3T
device_tracker.mi_smart_band_4:
  friendly_name: Massi's Mi Smart Band 4
light.80100865807d3a769f3b:
  supported_features: 63

Home Assistant v 0.116.4
arch | armv7l
-- | --
chassis |  
dev | false
docker | true
docker_version | 19.03.13
hassio | true
host_os | Raspbian GNU/Linux 10 (buster)
installation_type | Home Assistant Supervised
os_name | Linux
os_version | 5.4.51-v7l+
python_version | 3.8.5
supervisor | 2020.10.0
timezone | Europe/Berlin
version | 0.116.4
virtualenv | false

Describe the bug

A clear and concise description of what the bug is.
Description:
I am using the Home Assistant Supervised Version (the one shipping with IOTStack). I followed the instructions in the readme file, creating the folders and downloading the files as instructed. This is the contents of the directory (filepath as seen from the host machine, mapping to the right /config folder within the homeassistant container)

/usr/share/hassio/homeassistant/custom_components/nodered $ ls -la
total 64
drwxr-xr-x 3 root root 4096 Oct 29 02:28 .
drwxr-xr-x 3 root root 4096 Oct 29 02:19 ..
-rw-r--r-- 1 root root 2072 Oct 29 02:28 binary_sensor.py
-rw-r--r-- 1 root root  983 Oct 29 02:28 config_flow.py
-rw-r--r-- 1 root root 1377 Oct 29 02:28 const.py
-rw-r--r-- 1 root root 3382 Oct 29 02:28 discovery.py
-rw-r--r-- 1 root root 7501 Oct 29 02:28 __init__.py
-rw-r--r-- 1 root root  328 Oct 29 02:28 manifest.json
-rw-r--r-- 1 root root 1172 Oct 29 02:28 sensor.py
-rw-r--r-- 1 root root  753 Oct 29 02:28 services.yaml
-rw-r--r-- 1 root root 4964 Oct 29 02:28 switch.py
drwxr-xr-x 2 root root 4096 Oct 29 02:28 translations
-rw-r--r-- 1 root root 4401 Oct 29 02:28 websocket.py

After restarting HA, when trying to add the integration, the integration is not present in the list.

Debug log

Debug Logs:

Error sending through socket 18
3:32:22 AM – /usr/local/lib/python3.8/site-packages/zeroconf/__init__.py (WARNING)
You are using a custom integration for nodered 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.
3:31:09 AM – loader.py (WARNING)
Error setting up platform legacy
3:31:09 AM – Device tracker (ERROR)
No Bluetooth LE devices to track!
3:31:08 AM – bluetooth_le_tracker (WARNING)

Hi,

Currently using the custom component we can create a switch in Hass but I was wondering if there was an option to create it stateless (separate ON/OFF buttons)

Describe alternatives you've considered
Maybe something with template switches in hass but I'm still unsure if its possible this way.

Edit: As a workaround, its possible to customize the entity using assumed_state configuration, so I found the solution.

thanks!

Version of the custom_component

v0.4.4

Describe the bug

I have installed the node-red add-on (currently v7.1.1) in supervisor long time ago, only today I found out this custom_component and wanted to use the "Expose to Home Assistant" function, I then used HACS to install it (v0.4.4). However after installing and restarting HA the "Expose to Home Assistant" is still not showing up in the event node.

Does it need extra configuration to make it work? Or is it because I didn't follow the custom_component first - add-on second installation order? How can I fix this?

Is your feature request related to a problem? Please describe.
I made several switches in Node-RED exposed to HA to control some RF plug sockets and some RF wall switches.
Since these switches can't return a state to HA, I'd like to be able to just push OFF or ON several times in the UI.

Describe the solution you'd like
It would be nice to have some extra attributes to set to the switch made.
I'm requesting the "assumed_state" setting here, but maybe it would be possible to just add all the settings ?

Describe alternatives you've considered
I can of course just make the switches in HA configuration.yaml but I really like the fact that new "things" added with Node-RED are just editable without restarting all the time...