Thank you Michael.
I can duplicate the issue I had here.
Initially I had configured the MQTT topics top setting to show accepted topics only in the
- General / Inbound (Subscription) Management section - Listen for only accepted topics.
This was for the already configured numeric sensors.
- Associations tab / Include non-plugin HSDevices / Include MQTT Topics
Outbound (Publish) Management - never really touched this section
- by default it shows enumerate HS Devices during startup
Then wanting to add another sensor - didn't change anything above - rather I added it manually via the
Manual - Manual Setup or Edit of Subscription (Inbound) to a MQTT Topic.
No discovery had been done at this point. This is the part I skipped and where it created the "problem" device.
I then checked the accepted box when it showed up in my Associations list.
It did create the device showing a payload numeric value of -1 rather than the actual payload number.
It was this device that I could not change.
I then tried to un accept the device and it removed the variable.
I then changed the settings to discovery mode and it saw the device in question.
I accepted and it still would not let me change it even though it was a different reference number.
This is what I played with mostly yesterday and could never change the device properties.
So what I did (as I had done this once before) I deleted the plugin and associated files.
Installed the plugin from scratch then left it in discovery mode, accepted all of the Node Red Topics (OWFS) and all was well.
I can duplicate the issue I had here.
Initially I had configured the MQTT topics top setting to show accepted topics only in the
- General / Inbound (Subscription) Management section - Listen for only accepted topics.
This was for the already configured numeric sensors.
- Associations tab / Include non-plugin HSDevices / Include MQTT Topics
Outbound (Publish) Management - never really touched this section
- by default it shows enumerate HS Devices during startup
Then wanting to add another sensor - didn't change anything above - rather I added it manually via the
Manual - Manual Setup or Edit of Subscription (Inbound) to a MQTT Topic.
No discovery had been done at this point. This is the part I skipped and where it created the "problem" device.
I then checked the accepted box when it showed up in my Associations list.
It did create the device showing a payload numeric value of -1 rather than the actual payload number.
It was this device that I could not change.
I then tried to un accept the device and it removed the variable.
I then changed the settings to discovery mode and it saw the device in question.
I accepted and it still would not let me change it even though it was a different reference number.
This is what I played with mostly yesterday and could never change the device properties.
So what I did (as I had done this once before) I deleted the plugin and associated files.
Installed the plugin from scratch then left it in discovery mode, accepted all of the Node Red Topics (OWFS) and all was well.
Comment