core
core copied to clipboard
Neptun Smart shows up in Tuya as (unsupported) and has no entities
The problem
Hello,
I have added my leakage protection system to the Smart Life app where it works as expected. It automatically appeared in Tuya Integration as a device, but with the text (not supported) in the name. There are also no objects created for the Neptun Smart.
Is this a bug or am I doing something wrong?
Thanks and all the best
What version of Home Assistant Core has the issue?
core-2023.1.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Tuya
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya
Diagnostics information
tuya-5fe4c1d21bb39517a1af3f210008e10d-Neptun Smart-1a785500de82ab68a1528c832bf1b679.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of tuya
can trigger bot actions by commenting:
-
@home-assistant close
Closes the issue. -
@home-assistant rename Awesome new title
Change the title of the issue. -
@home-assistant reopen
Reopen the issue. -
@home-assistant unassign tuya
Removes the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
tuya documentation tuya source (message by IssueLinks)
I can see the same issue after updating to Core 2023.1.4
2023.1.7 the problem is still there
confirm
а кто знает, может это надо нептунов самих пинать, апи какоенить может изменилось и это им исправлять надо?
если вдруг кому будет полезно, то есть интеграция sst_cloud, через нее все подключилось, на гитхабе: SST Cloud Integration вроде все работает
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.