New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] - Moes Thermostat - TS0601 #2755
Comments
I have the same device and managed to make it working using this quirk: however this device has a number of issues not dependent on Home Assistant or the ZigBee protocol itself, see here |
@glcos Thank you. Have gotten this model as well [gotten it with the 11.11 sale, at a steep discount], with this the 3 most important features are now working for me One question: Do you know if its possible to FULLY deactivate the build in programming/scedule I have a Avatto one as well, of which this is possible. Having it only be In Manual modus. https://www.aliexpress.com/item/1005002960679997.html? |
@darknessblade I'm not sure I'm getting your question right, anyway I use the MOES one only in manual mode, and let Home Assistant to do the schedule and advanced programming such as temperature setting based on occupancy. |
@glcos What I mean is: That you deactivate the Schedule modus completely, so its always in Manual modus. and the mode-change button essentially doesn't do anything. It should be possible trough the advanced menu "screen off+ hold mode+clock" |
@glcos Contacted the seller for the advanced menu instructions, and It does not look like its possible to disable the build in scedule Now I only needs to find out why HASS thinks I want to heat my room to a temperature hotter than the sun |
See following log [Due large file size and randomness in the spikes, I cut the section of the most recent spike with roughly 3 temp/set checks before the spike] |
Thanks for all the time and research guys, I really appreciate it 😄 I don't think I put it anywhere in the original post so I edited to reflect what I now understand to be the specific model identifier: _TZE204_aoclfnxz |
@DJ-Specter Do you have the same issue with those Solar-flare temperature spikes? |
I certainly do! This request came off the back of my HA Community post: https://community.home-assistant.io/t/popular-moes-thermostat-not-showing-entities-after-zha-pairing/641041/19?u=dj-specter |
This also seems like a good opportunity to flag another post that much to my distress hasn't had any traction, but which I'm pretty sure must be related: |
@DJ-Specter @darknessblade in my installation I don't see these spikes in temperature. |
@glcos I use the "Sonoff Zigbee 3.0 plus type E" with ZHA. Currently have changed the build in scedule to have everything set at 00:00 and 15C. The weirdest part is that I have not touched or interacted with the Climate card/integration or panel. yet it still has spikes |
Does anyone know how long these kind of device support requests take to be actioned? I'm wondering now about just using the smelly Smart Life app to unlock the full content of these and some TRVs I got, but I really don't want to. |
@darknessblade I received a new Avatto thermostat and tested, now I think I understand what you ment for disabling scheduling mode. I could not find a way to completely disable scheduling or advanced programming mode and put it into manual. |
Not sure waht causes that blank screen. Also a small update regarding My moes thermostat after updating the zigbee coordinator, it still gives the same spikes as I had before. One benefit is that the thermostat does not instantly turn ON when it gets such a spike, since it turns on roughly 10 seconds after a temp-change trigger |
Do the spikes only happen when the mode is switched from heat to off, or vice versa? Or are they when the temperature is changed, maybe? It's hard for me to see from the graphs, but I feel like it's possible to test. I'm also convinced this is the thing that's causing my thermostat to gradually decrease the temperature it's set to, per the HA community ticket I linked above... |
@DJ-Specter the spikes happen when the device is ON Display/heat=ON |
So is this a manufacturer problem then? How can we move forward to get it fixed? |
@DJ-Specter This way the "bug" still is present, but the log data is more readable, as the spikes are cut off at 50C instead of UNCAPPED. which results in rare spikes of 1.3BILLION degrees Celsius. My reason for 50C, is because nobody would use a set temp above 30C ""under normal use"". [Unless people use it for a Infared sauna, trough the floor sensor with the electric heating panel]. As I am not well versed in coding, I am not sure if its possible to do this with the custom quirks. I have contacted the manufacturer/seller to see if I can get the Xcell files/custom cluster information. [will update when I get a response] |
@DJ-Specter tried contacting the manufacturer/seller, for the tuya cluster information, but they do not want to give this information. Would it be possible to hardlock the max reported set-temp to 50C, in the custom quirk? where it ignores anything above said value |
That's very annoying, damn. Nice one for getting in contact with them!
I strongly endorse your suggestion but have no idea how to make it happen
I'm afraid 😅
Hopefully it can be factored into the official ZHA quirk when this ticket
gets actioned?
Or some enterprising dev can swoop in to the rescue with an amendment to
the custom quirks listed above, or something fresh if that's more
constructive?
…On Sat, 20 Jan 2024, 07:47 darknessblade, ***@***.***> wrote:
@DJ-Specter <https://github.com/DJ-Specter> tried contacting the
manufacturer/seller, for the tuya cluster information, but they do not want
to give this information.
Would it be possible to hardlock the max reported set-temp to 50C, in the
custom quirk? where it ignores anything above said value
—
Reply to this email directly, view it on GitHub
<#2755 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNDXYDE2F24C4GMJGILEKTYPNR6PAVCNFSM6AAAAAA7N6L636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBRG44TKNZRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
True, luckily the thermostat has a roughly 10 second delay before activating the relay. so the 1MS "false positive" update isn't the biggest issue in terms of function, its only annoying for logging purposes, as it KILLS the graph. In my opinion they should HARD-limit all thermostats recording/messages to a default limit. It is indeed a shame that MOES doesn't want to share the Tuya cluster info. Last dev/shop {AVATTO}, I contacted for a different panel, did share it without issue. [though in my case they did promise it being functional with homeassistant under ZHA], so that may have played a factor. |
Fixed quirk at repo: All target room temp spikes over 50 degrees are not reported to HA. |
Whoa, out of nowhere, a new hero swoops in! Amazing, thank you so much dude! I've just added it and will keep an eye on my temps over the next week and report back. |
added it to my HASS, It looks to be working slightly better than the one I used before, Instead of spikes I now get dips to 0-4C. in 7 hours I got 3 dips Will report back in 72 hours if I get massive spikes or dips again. |
Those spikes are seen in your previous log, so device send it, unfortunately.
|
Can verify I am only getting DIPS that drop the set_temp to 0-8C Still slightly annoying, but still better than spikes of 100MIL+, especially for logging data From the logs: {Isolated the section of the DIP} |
You know that you have a broken device. There's no cure for that.
Did you upgrade the firmware of the dongle or are you on stock version? |
I upgraded the firmware from the stock firmware, I am running "Firmware: 7.3.1.0 build 176" In what sense would the device be broken? I have roughly 90 zigbee devices in my network. Of which 12 are switches with Neutral "functioning as repeaters". "Wifi_analyzer does not show any overlapping Wifi networks in the range of the zigbee channel" |
ZHA is in reader mode. It just hears what is sent to HA. You can't even blame repeater or etc. because those commands are different: 15, 0 and 15 degrees back.
|
AAH OK, I can try connecting it to TUYA [have a Zigbee hub, I only use for updates] Have checked it with my zigbee hub and it still gives the same issues the TUYA-IOT platform shows this in the logs. Have also contacted aliexpress/the store for a solution, "since its a CHOICE store" its was dealt with by aliexpress, currently awaiting results/their verdict from the "higher support team" |
Problem description
Hi,
I'm submitting this request following the conversation on this ticket:
https://community.home-assistant.io/t/popular-moes-thermostat-not-showing-entities-after-zha-pairing/641041/1
I bought a Moes thermostat (gas boiler + zigbee version), that pairs with Zigbee but doesn't show any proper entities.
I have a friend with what I thought was an identical model but it seems there are lots of subvariants of this one. Either way, it should definitely work.
I have also done all the troubleshooting outlined in this, including removing and re-pairing several times: https://community.home-assistant.io/t/guide-for-zigbee-interference-avoidance-and-network-range-coverage-optimization/515752
I'm not sure what other info is required here, but please don't hesitate to ask :)
EDIT: After learning a lot about quirks since I posted this, I'm adding the actual model number to the post for searchability as I can't see it anywhere - _TZE204_aoclfnxz
Thank you very very much in advance for any help!
Solution description
As far as I understand, something to do with quirks is required for this to work properly with Zigbee Home Assistant, and the device needs to be opted into ZHA. I think that's all that's necessary?
Screenshots/Video
Screenshots/Video
Device signature
Device signature
Diagnostic information
Diagnostic information
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: