Advanced Fires 1500 - new config first try #1177
Replies: 9 comments 4 replies
-
Using the log message from #1124, I get a 100% match for advancedfires_1500_fireplace, so your current log must be different. Without seeing the log, I cannot guess which dps need to be made optional. |
Beta Was this translation helpful? Give feedback.
-
Added a diagnostic output from my tuya-local after a further clear out and re-config of my Advanced Fires 1500 and selection of defaults:
|
Beta Was this translation helpful? Give feedback.
-
Thanks, this shows the temperature, brightness and a few others are missing, probably because the device is currently off. |
Beta Was this translation helpful? Give feedback.
-
So I removed the integration, made sure the fire is on then restarted the config. Again I got the same two options of an rgbww_lightbulb or simple_switch . I chose the former as default and took the default name. Only the one entity is created as a fancy light, nothing else. New/latest diags:
|
Beta Was this translation helpful? Give feedback.
-
And by 'on' I only mean powered for lights. The heater remains off. |
Beta Was this translation helpful? Give feedback.
-
Just a general thought - do I need to do anything in Tuya IoT to enable a particular instruction set? Currently I have it on a specific DP Instruction called 'Multicolor Series'. I don't have it using the standard instruction set as that looked wrong and too basic. I'm fairly new to all this as you can probably tell. |
Beta Was this translation helpful? Give feedback.
-
Here is my Tuya IoT Device Basic information for the device named 'Advanced Fires 1500', in case this has any relevance to the lack of config match: |
Beta Was this translation helpful? Give feedback.
-
So I've not got any further with this Advanced Fires 1500 device, it still will not appear on my config entry choices. Are there further things I can try? |
Beta Was this translation helpful? Give feedback.
-
OK and massive thanks - something must have changed as a reinstallation of the latest integration main code has now matched my device. Will play and post back how things go. |
Beta Was this translation helpful? Give feedback.
-
I requested a new 'Advanced Fires 1500' config for an electric fireplace with a primary climate/heater and a bunch of led lights used for virtual flame/effects.
I got a notification that the new tuya-local release today contains that config, so wanted to give it a try. Downloaded the new zip and unpacked the files to my HA custom components tuya-local directory, overwriting the existing files where necessary.
When I started a new config with id, local key, IP address etc. I thought the ID would be used to match to a device config directly?
Instead I get offered just a generic switch or 'rgbww_lightbulb' only:
I re-read the documentation to see if I was just being a dumb ass, but can't see any obvious user errors. Any views on this from the community before I start bugging the author?
Beta Was this translation helpful? Give feedback.
All reactions