Autor Thema: MAX! Cul: Send Queue missing ack from ...  (Gelesen 1822 mal)

Offline kennybl

  • Jr. Member
  • **
  • Beiträge: 52
MAX! Cul: Send Queue missing ack from ...
« am: 28 November 2020, 21:32:10 »
Hello,

I have installed FHEM and connected everything via a Max Cube and then changed everything to a CUL and everything seemed to work.
After a few weeks i see a lot of "Send Queue missing ack from ..." messages in the log.

Also it sometimes takes a lot of time before temperatures are being synct from or to a thermostat.
What can the problem be?

Thank you


This is the last part of the log:

2020.11.28 06:59:16 3: cm, Send Queue missing ack from MAX_1be048 for TimeInformation, removing from queue
2020.11.28 12:59:16 3: cm, Send Queue missing ack from MAX_1bdd5d for TimeInformation, removing from queue
2020.11.28 14:59:16 3: cm, Send Queue missing ack from MAX_1bdb83 for TimeInformation, removing from queue
2020.11.28 15:43:21 3: CM_Parse, unhandled message WakeUp from MAX_1bccc6 to MAX_1bdb83, groupid : 0 , payload : 03 - ignoring !
2020.11.28 15:43:32 3: CM_Parse, unhandled message WakeUp from MAX_1bccc6 to MAX_1bdd5d, groupid : 0 , payload : 03 - ignoring !
2020.11.28 15:44:07 3: CM_Parse, unhandled message WakeUp from MAX_1bccc6 to MAX_1bdb83, groupid : 0 , payload : 03 - ignoring !
2020.11.28 18:59:16 3: cm, Send Queue missing ack from MAX_1be048 for TimeInformation, removing from queue
2020.11.28 20:14:43 3: cm, Send Queue missing ack from MAX_1bdb83 for SetTemperature, removing from queue
2020.11.28 20:15:16 3: cm, Send Queue missing ack from MAX_1bdd5d for SetTemperature, removing from queue
2020.11.28 20:15:27 2: cm, CUL not enough credit! credit10ms is 92, but we need 110. Waiting 18 seconds. Currently 1 messages are waiting to be sent
2020.11.28 20:15:53 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 2 messages are waiting to be sent
2020.11.28 20:17:42 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 2 messages are waiting to be sent
2020.11.28 20:19:32 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 2 messages are waiting to be sent
2020.11.28 20:21:18 3: cm, Send Queue missing ack from MAX_1bdb83 for SetTemperature, removing from queue
2020.11.28 20:21:18 2: cm, CUL not enough credit! credit10ms is 5, but we need 110. Waiting 105 seconds. Currently 1 messages are waiting to be sent
2020.11.28 20:23:11 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 1 messages are waiting to be sent
2020.11.28 20:25:00 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 1 messages are waiting to be sent
2020.11.28 20:26:49 2: cm, CUL not enough credit! credit10ms is 7, but we need 110. Waiting 103 seconds. Currently 1 messages are waiting to be sent
2020.11.28 20:28:36 3: cm, Send Queue missing ack from MAX_1bdd5d for SetTemperature, removing from queue



Edit: Not all of the thermostats do this, could it be that some of the thermostats are out of range? If so, can i increase the range?
« Letzte Änderung: 29 November 2020, 10:16:27 von kennybl »

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 15567
  • "Developer"?!? Meistens doch eher "User"
Antw:Send Queue missing ack from ...
« Antwort #1 am: 29 November 2020, 07:18:07 »
Could you pls change the thread title to better point to MAX! or move the entire thread to the MAX! forum section?
Then Wzut most likely will answer. Perhaps he will recommend to switch to the beta versions oft the module set as a first step.
Server: HP-T620@Debian 10, aktuelles FHEM + ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Offline Wzut

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4533
Antw:Send Queue missing ack from ...
« Antwort #2 am: 29 November 2020, 08:43:49 »
Not all of the thermostats do this, could it be that some of the thermostats are out of range? If so, can i increase the range?
You have good devices and bad devices ?
Maybe the bad devices are too far away from your CUL.
The new CUL(USB) is not on the same position in your house as the old CUBE(LAN) ?

Please have a look at the RSSI values of  each of your MAX devices , to get a quick overview you can define a readingsGroup :
define rg_rssi readingsGroup <name>,<rssi>,<time> TYPE=MAX:av_.*
attr rg_rssi mapping %DEVICE
attr rg_rssi room MAX
attr rg_rssi sortColumn 2
attr rg_rssi valueStyle style="text-align:right"
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

Offline kennybl

  • Jr. Member
  • **
  • Beiträge: 52
Antw:Send Queue missing ack from ...
« Antwort #3 am: 29 November 2020, 10:18:54 »
Could you pls change the thread title to better point to MAX! or move the entire thread to the MAX! forum section?
Then Wzut most likely will answer. Perhaps he will recommend to switch to the beta versions oft the module set as a first step.

Thank you for the tip, i just updated that.



You have good devices and bad devices ?
Maybe the bad devices are too far away from your CUL.
The new CUL(USB) is not on the same position in your house as the old CUBE(LAN) ?

Please have a look at the RSSI values of  each of your MAX devices , to get a quick overview you can define a readingsGroup :
define rg_rssi readingsGroup <name>,<rssi>,<time> TYPE=MAX:av_.*
attr rg_rssi mapping %DEVICE
attr rg_rssi room MAX
attr rg_rssi sortColumn 2
attr rg_rssi valueStyle style="text-align:right"

I see the one that is not changin has an RSSI value of -81.5, all the others are between -75 / -79, and 2 of them are between -60 and -65.

What is a decent RSSI value? If i know that value i can try to reposition the cul and see if i that changes the results



Also, i installed a new thermostat, it shows up in FHEM perfectly but i can't change the temperature again.

This is what the log shows:
2020.11.29 11:56:10 3: cm, Send Queue missing ack from MAX_127d1b for PairPong, removing from queue
2020.11.29 11:58:50 2: cm, CUL not enough credit! credit10ms is 56, but we need 110. Waiting 54 seconds. Currently 1 messages are waiting to be sent
2020.11.29 11:59:52 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 1 messages are waiting to be sent
2020.11.29 12:01:41 2: cm, CUL not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 1 messages are waiting to be sent

The newly added device shows this STATE: 20.0&deg;C (rf error)

I also don't understand how the credits work. In het second log row it says we have 56 but we need 110. The next row shows we have 8 but still needs 110, why did we lose 48 credits without anything being done? (still 1 message needs to be send). After almost 2 minutes again we still need 110 and still have 8, i can't exactly understand how it works.

Also i need 110 credits to just change the temperature from 1 thermostat? Because that was all i tried to do

After waiting i tried to change temperature again and get this again:

2020.11.29 12:03:28 3: cm, Send Queue missing ack from MAX_127d1b for SetTemperature, removing from queue
« Letzte Änderung: 29 November 2020, 13:07:00 von kennybl »

Offline Wzut

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4533
Antw:Send Queue missing ack from ...
« Antwort #4 am: 29 November 2020, 17:16:43 »
Also, i installed a new thermostat, it shows up in FHEM perfectly but i can't change the temperature again.
and the reason is :
2020.11.29 11:56:10 3: cm, Send Queue missing ack from MAX_127d1b for PairPong, removing from queuethis device is not paired with cm and you cant set anything on a unpaired device !
if you try that it will cost you a lot of your valuable credits
Is it a brand new device or a already used one ? If it is not new maybe it is already paired with its old master -> factory reset

Zitat
The next row shows we have 8 but still needs 110, why did we lose 48 credits without anything being done
if you make a verbose 5 log you will see that there was more than nothing

what is the answer of this question :
The new CUL(USB) is not on the same position in your house as the old CUBE(LAN) ?




Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

Offline kennybl

  • Jr. Member
  • **
  • Beiträge: 52
Antw:MAX! Cul: Send Queue missing ack from ...
« Antwort #5 am: 29 November 2020, 17:42:28 »
I factory reset the thermostat and i can get the "new" (secondhand) thermostat working now.

The CUL is not on the same place but on the top floor. I moved it to a lower floor to test now and i think that makes the RSSI of the thermostats better:

(index):198 MAX_1bdb83 > -70.5
(index):198 MAX_1bdd5d > -72
(index):198 MAX_1bccc6 > -57.5
(index):198 MAX_1bdd75 > -74.5
(index):198 MAX_1be7d4 > -76
(index):198 MAX_1bd434 > -53
(index):198 MAX_1bccc1 > -62.5
(index):198 MAX_1be048 > -75
(index):198 MAX_127d1b > -71.5

Can i get a better RSSI with a 868mhz transmitter like this:
https://nl.aliexpress.com/item/33059343309.html?spm=a2g0o.productlist.0.0.4c517b1cFlR0Op&algo_pvid=1b462424-2f07-43b6-92b7-9ab96c44fbf2&algo_expid=1b462424-2f07-43b6-92b7-9ab96c44fbf2-46&btsid=2100bddd16066680832195775ea3c7&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_


I now have this:
https://nl.aliexpress.com/item/32924239954.html?spm=a2g0o.detail.1000060.1.2db47f5brljZi2&gps-id=pcDetailBottomMoreThisSeller&scm=1007.13339.169870.0&scm_id=1007.13339.169870.0&scm-url=1007.13339.169870.0&pvid=df19dc62-f607-4f31-9d66-ae877796fc1b&_t=gps-id:pcDetailBottomMoreThisSeller,scm-url:1007.13339.169870.0,pvid:df19dc62-f607-4f31-9d66-ae877796fc1b,tpp_buckets:668%230%23131923%230_668%23808%234094%23134_668%23888%233325%2314_668%232846%238116%23959_668%232717%237559%2353_668%231000022185%231000066059%230_668%233468%2315609%23224

Offline Wzut

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4533
Antw:MAX! Cul: Send Queue missing ack from ...
« Antwort #6 am: 29 November 2020, 18:57:37 »
your RSSI values are looking much better !
if your problem come back or if you install other devices on new places : CUL_MAX can handele more than one CUL.
e.g. CUL1 with USB  and CUL2 with LAN/WLAN
in my house are running two LAN connected old CUBEs with the CUL firmware and I have good RSSI values from the cellar up to the roof

About your CC1101 modules : i am not a hardware specialist, but in the last time some user reported that they have problems with the exact frequency of the radio part.
your first link points to a 433 MHz Module !!! MAX is running on 868 MHz
« Letzte Änderung: 29 November 2020, 19:00:02 von Wzut »
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

Offline kennybl

  • Jr. Member
  • **
  • Beiträge: 52
Antw:MAX! Cul: Send Queue missing ack from ...
« Antwort #7 am: 29 November 2020, 19:31:09 »
I'm sorry, i just posted a quick link from aliexpress, i know they are running on 868mhz.

I have a cube which i am not using, would it be better to reflash it as a cul (?) and connect it together with the nanoCul?
Or create another nanoCul and put it somewhere downstairs? (usb or lan)

Offline Wzut

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4533
Antw:MAX! Cul: Send Queue missing ack from ...
« Antwort #8 am: 30 November 2020, 17:05:38 »
The CUBE has a good CC1101 module and with the firmware from Telekatz its easy to change, costs no money and can be connected to LAN or USB.

If you start with a second CUL please remember that you must change some attributs on CUL, CULMAX and your MAX devices.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

Offline kennybl

  • Jr. Member
  • **
  • Beiträge: 52
Antw:MAX! Cul: Send Queue missing ack from ...
« Antwort #9 am: 02 Dezember 2020, 20:10:33 »
Thank you