It was fine with 13.3. After updating to 13.4 the problems returned. The Matter service started having problems again. At the first blackout, I find all my devices offline on Google home. Once again I have to disconnect the matter, reconnect it and reconfigure all the devices on Google home. This situation is really bad.
I solved it by restarting the ihost. I think I understand that when starting after the blackout, as the wifi network is not yet active, the ihost Matter service remains lame. Can this be resolved with post-boot attempts? A retry would be enough.
Whatâs the exact problem?
The node-red add-on and the whtsApp are not run or maintain by us.
Maybe try update the node-red image?
Sorry for causing trouble to youďźmay you make a feedback and upload your sys log on ihost?
the whatsapp function in node red worked well until I did the latest update V1.13.4 for the ihost. After that I no longer receive any notifications. The problem is not with node red, I have the latest update for that. The problem started after installing version V1.13.4. Version V1.13.4 is not progress, but regression
Iâve had similar issues after power cut/failure. I found rebooting my router solved the issue. My ihost needed no action. The ihost booted fine after the power failure, the router did not. A controlled reboot of the router allowed it to restart correctly and the ihost was ready and waiting once it had finished.
I hope I can help. I took use node-red with WhatsApp nodes for notifications but had no issues with it after updating. Although I did have some hardware anomalies that the Devs helped me fix.
What version or node-red are you using?
What WhatsApp pallete in node-red, and version is that pallete?
Are you using the CallMeBot API?
Iâll see if you are using something different to me.
Please send us your system log and node-red log.
Weâll pinpoint whatâs wrong.
I noticed that many times the problems caused by NODE-RED are caused by the inability to resolve domains, NS. If I do a simple ping node, it does not respond to domains like google.com but responds to ips (8.8.8.8). I think that IHost uses an internal DSN and it does not work properly. After several restarts it works. I mention that all the other devices in the LAN do not have NS resolution problems, it is strictly a problem of IHost. We can not set a DNS server manualyâŚ
It doesnât work that way. Your conclusions are misguided. Firstly because internal DNS names cannot be used to connect to external IP addresses of the VM. A Docker container virtualises only the application layer, and runs on top of the host operating system. Therefore, it is not a VM instance.
I donât know how it works but it doesnât work. I also know that it does not use the DNS declared by DHCP, I also know that when IHost is not working, it does not respond to IHost.local but only to ip, and it does not query any domain either. I know it happens often, I know I have to restart 10 times for it to work. I also know that a year has passed and basic functionalities have not been fixed. Probably DNS is declared a server from China that works when it wants! When Node Red does not work, the eWelink Smart Home container doesât work too, devices become offlineâŚetcâŚetc⌠And here Iâm talking about LAN only, not opening ZigBee subjectâŚ
And once again, suddenly, Google home no longer receives status updates via ihost matter. Can anyone suggest me an alternative firmware for ihost? Iâm tired of resetting everything every 10 days. I have completely lost faith in sonoff. I would just like my home automation to actually work but with this ihost itâs clear that I canât have it.
Again today. Suddenly Google home routines no longer work. Why? Because the ihost matter stops communicating the status of the devices. Rebooting ihost does not solve the problem. After a few reboots it suddenly decides to start working again. It cannot be considered a reliable system/device. Not at all. Iâll rename It âiHostWhenIWantâ
Hi liberaccio,
Sorry for the inconvenience. When you have a moment, could you kindly submit the logs via the iHost WebUI? This would be incredibly helpful for our development team as they can then inspect if thereâs any issue in our Matter component.
If possible, could you also provide a specific device ID? You can send it directly to me in a message. It would be greatly appreciated.
1 Like
V1.13.7 (2024.03.27)
New Features:
- Matter Bridge now supports SONOFF TRV.
- eWeLink add-on now supports SONOFF Smart Stackable Power Meter.
Optimizations:
- Optimized the detection duration of SNZB-06P, which can be set to a minimum of 15 seconds.
- Further optimized and improved iHost performance.
Bug Fixes:
- Fixed the issue where SONOFF TRV smart schedules failed to revert to defaults after device reset.
- Resolved the offline issue with MINIR4.
- Resolved an issue where the status of multiple SONOFF TRVs could not be saved as scene triggers.
1 Like
After the update, the scene with the snzb-06p sensor does not work.
Removing the sensor from the scene and adding it back fixed the problem.
hi, weâve just done some test from 1.13.4 to 1.13.7, SNZB-06P works in scenes.
whatâs your previous version? is it 1.13.4?
can you please submit your system logs via the Feedback?
and please let me know the device id of 06P.
updates I made from version 1.13.4 to 1.13.7. When I have access to ihost, I will s flend the logs.
I send
feedback 204966
thank you, please let me know the device id of 06P