when using the Action node in ‘Node-red’
I select the action ‘number.set_value’
but then it’s not possible to select an entity…
(this used to work)
when I select something else (like ‘input_number.set_value’ then it is possible to select an entity… but since this is a device i can not change it from ‘number’ to ‘input_number’… is this a bug? or what do i need to do?
I have never heard of a domain just named number.
What device is that from?
Actions in Home Assistant are provided by integrations. Integrations add entities, and may also at the same time provide various Actions that can be applied to these (and only these) entities.
Home Assistant comes, out of the box, with a number of Building Block Integrations. These do not relate to any real devices or entities, but provide basic services that other integrations can use.
The Number Integration is one such Building Block integration. As such, you can’t use it directly, since it does not relate to any real entities. If there are no entities that use this Action, it is not possible to select any entities in the Action node.
Other integrations, such as the input_number Helper, will create an input_number entity, and will use the Number Building Block integration to support it. The input_number integration will provide actions for the entities it creates, such as set_value, increment, and decrement.
It is, however, possible for Integrations to create Actions called ‘number.set_value’ if they do not follow the rules. This is probably overloading or miss-using the Number building block integration by adding an exposed action that the integration should not have done. As it happens, my TP-link integration does just that
Where integrations do not follow the rules, sooner or later the situation will be corrected and the ‘feature’ you were relying on evaporates. My guess is, you should not be able to use number.set_value, and if you can/did then this is an erroneous situation.
.
number.set_value is a valid service call provided by home assistant core. Integrations have the ability to breakout numerical attributes to their own number entities. Wled provides number entities for brightness and effect speed of segments. This is not a misuse, it’s an intended feature.
@WallyR this is from the device ‘smartEVSE’
but also the tesla integration as other (wled) integrations have this.
I know in previous version of HomeAssistant / Nodered it was working (version where you did need to fill in the entity id manual, and not by a dropdown menu)
I have an device, with an entity: number.smartevse_override_current (in the dashboard I can change this value by the ‘slider’)
But now I want to automate this using node-red
as you can see it is possible to select ‘number.set_value’
but then it is not possible to enter/select an entity_id.
I don’t know now how I can make it work in Node-Red…
I also think this is an intended feature, but a bug inside node-red? Where can i report this?
You probably need to update the home assistant nodes. In the right side menu choose manage palette and look for the ha nodes. I have the ability to choose a target.
can you check on what version you are?
I used to be able to also choose a target. But since the update i did last it is not possible anymore.
also, the ones that worked before the update, are still working (even so when opening, you don’t see any target, as long you don’t modify them, they keep working.)
it’s adding a new one that gives problems.
0.74.2 is the version I am using as well. Have you tried rebooting the entire system not just ha? In the shutdown popup there should be a drop down that gives you the option to reboot the host. Try clearing the browsers cache as well.
Another thing if you are not using it already, the direct access link. haip:1880 If prompted for a user and password use your ha login credentials.
I asked because it might also be the integration that have changed and knowning the specific integration might get others with that integration to help, like to try it out in Node Red.
I do not have that integration, so I am unable to help further, since Mikefilla already mentioned updating the NodeRed palettes. 
rebooting the complete system solved it (i allready tried restarting HomeAssistant and the nodered addon) (over 600 days since last reboot… thankfully everything went well 
)
