OK I’ve added more debug message to find out what it could be.
Here more debug message :
2019-09-02 19:59:17 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.sinope_light_bea_s_room is taking over 10 seconds
2019-09-02 19:59:18 DEBUG (SyncWorker_14) [custom_components.sinope] in request for 132f0100 : Unknown error (b’fc’).
2019-09-02 19:59:18 ERROR (MainThread) [homeassistant.helpers.entity] Update for light.sinope_light_bea_s_room fails
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 261, in async_update_ha_state
await self.async_device_update()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 441, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/sinope/light.py”, line 96, in update
device_data = self._client.get_light_device_data(self._id)
File “/config/custom_components/sinope/init.py”, line 535, in get_light_device_data
intensity = get_intensity(bytearray(send_request(self, data_read_request(data_read_command,device_id,data_light_intensity))).hex())
File “/config/custom_components/sinope/init.py”, line 290, in get_intensity
return int(float.fromhex(tc2))
ValueError: invalid hexadecimal floating-point string
Hi my kitchen sink juste drop off from under the qwartz counter and was full of water. Water Found His way through the Floor and floud all m’y network devices.
Until tomorrow Nights no internet and m’y pi is dead.
Il need to know if hassbian work on rpi 4
error b’fc’ is device not responding
Ok I’m back.
I’ve added more debug detail and Sinopé is just starting to answer some of my questions.
Need to setup a new hassbian HA but still have access to Hass.io HA
Update:
Sinopé have done many fix in there api and everything look good now for HA neviweb.
In HA sinope-GT125, I’ve added lots of error message debug for thermostat . For many reasons a thermostat may return invalid temperature value that correspond to error message. So I’ve added all possible invalid values with the corresponding error message that will appear in the log. I’ll issue a pull request soon but you can test it with the new branch «error-message» if you want.
Claude,
I’ve got a recurring problem with the gt125 integration. After a restart, all is well and working properly. After a couple of hours (between 4 and 8), all the request update timed out !!! The only way to get out of this, is to restart HA.
So, when the problem occurs, I’m no longer able to use my Sinope devices through HA but the Neviweb app works normally.
The problem is definitely cause by HA since the official app is working.
Also, like I post earlier, I have two devices which HA is constantly reporting a “not responding” error. But, again, those two devices works well with the app.
Here is an exemple of the time out error :
2019-09-08 17:26:18 ERROR (MainThread) [homeassistant.helpers.entity] Update for light.sinope_light_kitchen fails
Traceback (most recent call last):
File “/config/custom_components/sinope/init.py”, line 535, in get_light_device_data
intensity = get_intensity(bytearray(send_request(self, data_read_request(data_read_command,device_id,data_light_intensity))).hex())
File “/config/custom_components/sinope/init.py”, line 411, in send_request
sock.connect(server_address)
TimeoutError: [Errno 110] Operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 261, in async_update_ha_state
await self.async_device_update()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 441, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/sinope/light.py”, line 96, in update
device_data = self._client.get_light_device_data(self._id)
File “/config/custom_components/sinope/init.py”, line 538, in get_light_device_data
raise PySinopeError(“Cannot get light data”)
custom_components.sinope.PySinopeError: Cannot get light data
Let me know if you need more log.
Look like your gt125 IP adress has changed. Do you have a dhcp reservation for your GT125 or fixed IP?
dhcp reservation
Check if you have another device with a fix IP that is the same as the GT125. Also when it start bugging could you try to ping your GT125 ?
In my setup I have one pi that run hassbian HA with both neviweb and sinope gt125 and another pi that run Hass.io HA with both neviweb and sinope gt125. I don’t have the error message you mentioned above. I only get from time to time that one device is not responding in the neviweb custom_component. My GT125 is probably over loaded at that time. Each of my pi is polling my 35 devices every 2 minutes via gt125 and every 5 minutes via neviwed component. If I stop one pi, everything is back to normal.
I have the issue right now and I can ping the GT125 successfully from the hassio terminal. So it doesn’t seem a network issue.
Any other idea ?
Do you have the crc8.py file installed in your custom_components/sinope folder ?
Yep, the file is there
You have a network problem, it could be related to your proxy settings or DNS setting.
Look like HA try to connect, sock.connect(server_address), but it take longer than one minutes.
in your terminal type the following command:
/sbin/ifconfig
/sbin/route
and see if the IP adress and route are ok
Both Hassio and the Sinope Gateway are on the same managed switch. Like I said yesterday, the Neviweb app is working properly and the problem goes immediately away if I restart HA.
It’s a HA bug since 0.93 that pop up from time to time. Which HA version are you running ?
On Hass.io I’m on 0.98.4 and will upgrade to 0.98.5
On Hassbian I’m on 0.98.4 and upgrade to 0.98.5 failed
I’ll try to open a socket with different timeout value. It’s reported to fix that bug
For neviweb you don’t talk to the GT125 directly. For sinope you open a socket directly with the GT125
There is a timeout error waiting to that socket to open.
In your post for eth0 above, you have 11 errors in your RX packets. That could be the problem
RX errors mean that your NIC is receiving malformed frames from the transmitting switchport.
Frame errors mean CRC failures on receipt of a frame. The root cause of this could be a bad cable, or a bad interface on either the machine or the switch. Try replacing the cable, then moving to another port on the switch.
I just upgraded to 0.98.5 and I also reboot the pi to reset the RX/TX counter.
If the problem comes back, I will take another snapshot of the counter.
Thanks for your help
It didn’t take long
2019-09-11 00:20:19 ERROR (MainThread) [homeassistant.helpers.entity] Update for light.sinope_light_hallway_half_basement fails
Traceback (most recent call last):
File “/config/custom_components/sinope/init.py”, line 553, in get_light_device_data
intensity = get_intensity(bytearray(send_request(self, data_read_request(data_read_command,device_id,data_light_intensity))).hex())
File “/config/custom_components/sinope/init.py”, line 429, in send_request
sock.connect(server_address)
TimeoutError: [Errno 110] Operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 261, in async_update_ha_state
await self.async_device_update()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 441, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/sinope/light.py”, line 96, in update
device_data = self._client.get_light_device_data(self._id)
File “/config/custom_components/sinope/init.py”, line 556, in get_light_device_data
raise PySinopeError(“Cannot get light data”)
custom_components.sinope.PySinopeError: Cannot get light data
I already have 22 “Operation Timed Out” and no RX errors
I’m going to bed, it’s too late